Re: Is it safe to use log4cxx in multi-threaded environement?

Yes, all worker thread are created as thread.

 

I implemented the worker class in a separate compilable unit and instantiated it by wrapping it in a proc via the Windows CreateThread api.  I did that because i want tighter control of the thread instead of subclass it from the CWinThread.

 

Anyway, I was thinking wither to pass the LoggerPtr instance in to the worker thread class duringing instantiation or simply use the "extern" to reference the logger instance.

 

So based on your response, I can simply use log4cxx simple logging api by the main thread and all worker threads without having to implement a slightly more sophisticated socket listener apprroach.

 

yml

Curt Arnold <carnold@xxxxxxxxxx> wrote:

On Dec 6, 2004, at 12:38 PM, Jeff Lynn wrote:

> So by not requesting another instance of logger, do you mean I should
> use global variable in the main thread dnd and "extern" in worker
> threads?
>

Are you sure you meant threads? Sounds like you might be intended to
talk about child processes which is a totally different animal to which
the previous discussion does not apply.

Threads are independent code paths in the same application. You can
access all the variables that any other thread in the application can
access (however bad things can happen if you aren't careful).
Variables aren't "extern" for a thread, they are "extern" for a
compilation unit.

---

Do you Yahoo!?
 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.