You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by "Goli, Sri Sairam (Sairam)" <go...@lucent.com> on 2004/04/16 16:08:04 UTC

JVM hang while loading xml into dom

Hi,
 
We have an application which loads its configuration from an xml file. 
It uses a dedicated xml thread which reloads the conffiguration.
Sometimes that xml thread is hanging in DOMParser.parse() . 
We have log4j messages just before and after the parse(), the last message
that is
logged just before the hang was from the xml thread.  And from the log it
looks 
like all other threads are also hanging (no log messages from the other
threads, 
generally we see periodic log messages form these threads)
 
This happened twice once on windows 2003 and once on solaris, we couldn't
reproduce it again. Both times it happened when we are trying to reload the
xml configuration.
 
On windows (after  hanging for almost an hour), when we try to get the stack
dump,
all threads  started working normally. No exceptions were thrown and the
first message that is 
logged in the log was from the xml  thread ( the message right after the
parse())
 
But on solaris when this happens it stopped responding to kill -3.  ^C also
didn't work.
we have to kill the jvm using kill -9.
 
We are using jvm 1.4.2_03 in server mode and xerces 2.5.0.
 
Is anybody seen this problem? Is it possible to hang the whole JVM by some
application bug
or is it problem with JVM itself?
 
Thanks
goli

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org