Klaus Bertram wrote: > > Michael wrote: > >Vadim Gritsenko wrote: > >> > >> >It does also not help to call this xsp ones with small data amount > >> >and the second time with large data amount (giving the amount as request value). > >> > > >> >I know the process ID (Linux) of the thread which stops the system. > >> >Is there any way to know if this thread is the garbage collection thread? > >> > > >> > >> Delay in small XSP can be explained as gc, but system hang-up... I > >> doubt. StoreJanitor monitors memory state and logs everything to the log > >> file - do you see any suspicious activity there? if not, it is not gc issue. > >> > > > >Nothing suspicious in the logfile: > >DEBUG (2002-08-29) 16:23.49:350 [core.store.janitor] (Unknown-URI) >Unknown-thread/StoreJanitorImpl: JVM total Memory: 49377280 > >DEBUG (2002-08-29) 16:23.49:351 [core.store.janitor] (Unknown-URI) >Unknown-thread/StoreJanitorImpl: JVM free Memory: 12260168 > >DEBUG (2002-08-29) 16:23.49:351 [core.store.janitor] (Unknown-URI) >Unknown-thread/StoreJanitorImpl: Memory is low = false > > > > > >Michael > > Is your jdk is sun 1.3 ? > they had with this problems by large memory and thread's Stand of jan 02
No, I have Sun 1.4.0_01 As I encountered this problem I got the latest available jdk. Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
