Re: [Wrapper-user] SERVICE_CONTROL_INTERROGATE - last message before wrapper dies

[Leif M. <le...@ta...>]

Krishna Kottamasu wrote:

> Thanks for your prompt response.   Upgrading this customer to 
> 3.1.1/3.1.2 could take some time.  I can try setting 
> wrapper.debug=false in the config. file and see how it goes.  From 
> your message, this is what I understood:

Ok, I assumed you had enabled debug output when you started encountering 
problems.
Is there a reason why you have debug output enabled by default?  Debug 
output builds
up pretty large log files in a hurry.  It looks like you have it limited 
to 10, 10MB files
though so you should be Ok as far as disk-space.

> If more than one thread in our application tries to write something to 
> the standard out (which the wrapper traps and outputs to the wrapper's 
> log file) at the same time, that could be crashing the wrapper 
> process.  Is my understanding correct?

I want to reclarify this.   It is only a problem with multithreading in 
the C code of the
Wrapper.exe process.   There is NOT a problem when console log output coming
from the Java program itself.   Logging from multi threaded Java apps is 
perfectly
safe.

If the User presss CTRL-C,  second thread from the OS is called into the 
Wrapper
process.   If my debug log output from this second thread attempts to 
log at the same
instant as a log message from the Wrapper's main event loop then there 
was a chance
of memory corruption.   With debug output disabled, this would pretty 
much never
happen.

> I've also answered your questions right underneath them in the 
> original message.

Thanks,
Leif