Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / Virtual Machine / June 2003

Tip: Looking for answers? Try searching our database.

JVM freeze

Thread view: 
Mark van Leeuwen - 30 Jun 2003 05:17 GMT
Hi all,

We are occasionally getting a JVM freeze. It appears to happen when
both the application and the box it is running on are suddenly put
under load.

We are running JDK 1.3.1.08 on Solaris 8 with latest patches.

Truss output for the JVM process suggests that every thread has gone
to sleep:

poll(0xEC081448, 0, 2147483647) (sleeping...)
signotifywait()                 (sleeping...)
lwp_sema_wait(0xECC81E30)       (sleeping...)
lwp_cond_wait(0xEC181FA8, 0xFF385558, 0x00000000) (sleeping...)
lwp_sema_wait(0xEDF81E30)       (sleeping...)
lwp_mutex_lock(0xFF385908)      (sleeping...)
lwp_sema_wait(0xECD81E30)       (sleeping...)
accept(18, 0xED781624, 0xED781634, 1) (sleeping...)
lwp_sema_wait(0xED481E30)       (sleeping...)
poll(0xED0814D0, 0, 300000)     (sleeping...)
lwp_sema_wait(0xED181E30)       (sleeping...)
lwp_sema_wait(0xECF81E30)       (sleeping...)
poll(0xECE814C0, 0, 300000)     (sleeping...)
lwp_sema_wait(0xEA181E30)       (sleeping...)
lwp_sema_wait(0xECB81E30)       (sleeping...)
lwp_sema_wait(0xED581E30)       (sleeping...)
lwp_sema_wait(0xEC481E30)       (sleeping...)
read(31, 0xEC380E20, 1)         (sleeping...)
lwp_mutex_lock(0xFF385908)      (sleeping...)
read(33, 0xEC280E20, 1)         (sleeping...)
lwp_cond_wait(0xFF385548, 0xFF385558, 0xFF37EDB0) (sleeping...)
door_return(0x00000000, 0, 0x00000000, 0) (sleeping...)

Any help would be appreciated.

Thanks
Mark
Bill Scott - 30 Jun 2003 20:19 GMT
If the problem is in the Java application (rather than the JVM itself)
you should try to track down what Java was doing.  A Stack Trace
helps.  You can get one by sending a kill -3 to the process.  Note
that they changed the output a bit sometime back (I forget how 1.3
works) so you may have to experiment.  You can experiment on a
non-broken Java app so next time things freeze you'll know what to do.

-Bill


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.