tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: svn commit: r702160 - /tomcat/connectors/trunk/jk/native/common/jk_shm.c
Date Wed, 08 Oct 2008 06:04:53 GMT schrieb:
> Author: mturk
> Date: Mon Oct  6 07:28:20 2008
> New Revision: 702160
> URL:
> Log:
> Implement global shared memory lock for IIS. With IIS 6+ we don't have a single process
any more

I was talking to someone having exactly a shared memory corruption
problem for IIS 6 with application pools (multiple processes) yesterday.
So this is great.

The same holds true for the log file. Could we use the same construction
for the log file locking, or would that be bad? The user involved has
corrupt log lines every now and then, although log level is only info,
so they don't have a huge log volume. So I expect the multiple processes
currupt lines when incidentally logging in parallel.

Is there an easy way to distinguish the application pools (like a name
in the registry or so)? We could then add the application pool name to
the log lines. Of course we already have the pid there, but users can't
easily find out which pid belongs to which application pool.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message