Hi Rob, Right now, we are trying all the options suggested by you, thanks a ton for the same :) As you might have come to know, that we have little knowledge of the JAM VM; we are JAVA experts and we are using the JAM VM as a jre only, so we have little knowledge of its insides. Basically, What we need to know is that, when our JAMVM hangs, then what can we provide in this forum (or file as bug), which can help the jamvm experts to diagnose the problem and come to the solution? Should we provide the Thread State by running the kill -3 <pid> command or Is there is any thing else, which can help you to diagnose the problem better? Please guide us further, Thanks & Regards, - Rajesh Robert Lougher wrote: > > P.S. JamVM has several tracing options, most of which need to be > enabled at configuration time. Do ./configure --help to find out > which ones are available. Then enable using --enable-traceX, e.g: > > ./configure --enable-tracethread --enable-tracealloc > > Rob. > > 2009/7/15 Robert Lougher <rob.lougher@xxxxxxxxx>: >> Hi, >> >> Quick reply: >> >> 1) You can get a dump of all the threads and their stack traces by >> sending SIGQUIT to the jamvm process (find the process ID via ps or >> top), e.g. >> >> kill -3 <process ID> >> >> JamVM will dump the thread state and continue. >> >> If you launched JamVM from a terminal you can also do Ctrl-\ in the >> terminal, which will send SIGQUIT. >> >> 2) Attach gdb to jamvm and inspect the threads, e.g.: >> >> gdb jamvm <process ID> >> >> list all threads with: >> >> info threads >> >> then, for each interesting thread: >> >> thread <thread no> >> bt >> >> 3) Run JamVM with strace >> >> This will dump information about every system call being executed. >> However, if it takes two hours to hang this will probably be far too >> much information. >> >> Rob. >> >> 2009/7/15 ragoel <ragoel@xxxxxxxxxxxxxxxxxxx>: >>> >>> Problem: JAM VM hangs after running for ~2 hours. There is no response >>> from >>> jetty (running on jamvm) at this time. >>> >>> The environment is: >>> - the jam vm version is JamVM 1.5.3 >>> - GNU Classpath version is 0.98 >>> - the GNU Classpath is build by disabling the following things as they >>> are >>> not required by us: >>> . /configure --disable-gtk-peer --disable-plugin --disable-gconf-peer >>> --enable-tools >>> - we are running jetty 6.1.8 using the jam vm. >>> - we are connecting to the jetty (which is running on jamvm), through >>> the >>> browser (IE7) on port 8080, but there is no response from the server. >>> - Our code runs fine when it is running jetty on sun jre 1.5. So it is >>> certain that the problem is with the jamvm >>> - the linux platform is: debian >>> - After some analysis, it seems that there is some bug in the socket >>> library >>> of GNU Classpath due to which it stops responding after running for >>> sometime. >>> >>> Queries: Basically we are not able to do anything when the JAMVM hangs, >>> so >>> could someone please tell me about how to debug the jamvm when it hangs >>> i.e. >>> - Is there any hook so that we can attach something to it, >>> - Can we debug it remotely, >>> - How to enable logging in it? >>> - Any tool which can aid us in analyzing this problem further? >>> >>> We are stuck on this; please provide your valuable >>> suggestions/resolutions >>> for the same? >>> -- >>> View this message in context: >>> http://www.nabble.com/JAM-VM-hangs-after-running-for-%7E2-hours.-tp24494239p24494239.html >>> Sent from the Gnu - Classpath - General mailing list archive at >>> Nabble.com. >>> >>> >>> >> > > > -- View this message in context: http://www.nabble.com/JAM-VM-hangs-after-running-for-%7E2-hours.-tp24494239p24510469.html Sent from the Gnu - Classpath - General mailing list archive at Nabble.com.
