Carsten Ziegeler wrote:
>
> Vadim Gritsenko wrote:
> >
> > MRUStore synchronization is on my list. In current version I do not
> > expect issues except some exceptions, but I will change it to be
> > properly synchronized.
> >
> Hmm, all hanging threads log the following lines from the hold()
> method:
> if (getLogger().isDebugEnabled()) {
> getLogger().debug("Holding object in memory:");
> getLogger().debug(" key: " + key);
> getLogger().debug(" value: " + value);
> }
> And then nothing is logged. The next message in the log would
> be the release of the xml serializer but this never shows up,
> so I guess this is a synchronization problem in the MRUStore.
>
We currently have the problem that Cocoon (or Tomcat) hangs after some
period of activity. We tested this with several versions of
tomcat, ranging from 3.2.4, 3.3, 3.3rc1 to 4.0.3) and jdks (1.3.1 sun,
1.3.1 blackdown, 1.4 sun) and windows/linux.
All with the same result: tomcat does not respond at some time.
It seems that no OutOfMemory occurs.
When we put Cocoon to debug logging the last lines for each thread
are the above mentioned. And tomcat uses more and more threads as more
are comming in.
The stress test we currently do is to start each minute 27 requests
parallel.
Each request does some heavy operation which has a duration between 10 and
40
seconds!
I now synchronized all methods of the MRUStore and now all threads
inside Cocoon are processed (which means they left the service() method of
the servlet), but tomcat hangs and does not respond. Hm, so it seems we
have more than one problem here.
Anyone else experiencing problems like this?
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
