• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

IllegalMonitorStateException: JVMLK003: current thread not owner

 
Ranch Hand
Posts: 207
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
1.Using MVC Architecture
2.TESTED AT JRUN WORKING FINE
3.TESTED AT WEBSPHERE GETTING ERROR
java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
4.Not using any threads in my program.
Do anybody have idea about why this error occurring frequently?
This is quite urgent.please do mail me as fast as possible.
Moderators,please look into this matter...
java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The immediate cause is of course an attempt to do a wait, notify or notifyAll on an object when the Thread does not own a lock on the object. (See java.lang.Object)
Seems to me the first question is - does your code have any uses of wait or notify methods?
Bill
 
thomas davis
Ranch Hand
Posts: 207
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I already have mentioned that I am not using threads in my application. And I also specified that my application ran into above said error when it migrated to IBM WebSphere Application Server.I would like to know whether this error occur only in WebSphere Server or some other servers also. Does anybody have idea about this bug?
 
thomas davis
Ranch Hand
Posts: 207
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner .

1)d:\WebSphere\AppServer\installedApps\globalrfx.ear\globalrfx.war\WEB- INF\classes\com\sharedapps\internetworkingrfs\servlets\
Servlet: CommonInfoController.java
Bean : RequesterDB.java
Method : getPrevRequests()
The Following error has come in UT RFX : Common Info Controller - Case P:com.sharedapps.common.dbconnection.DBException: Problem in getPrevRequests method of RequesterDBcom.sharedapps.common.dbconnection.DBException: com.sharedapps.common.dbconnection.DBException: com.sharedapps.common.dbconnection.DBException: java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
2) D:\WebSphere\AppServer\installedApps\globalrfx.ear\globalrfx.war\WEB-INF\classes\com\sharedapps\globalrfx\servlets\
Servlet: ModifyController.java
Bean : SearchDB.java
Method : getRegionLst()
The Following error has come in UT RFX : ModifyController - Case 0:javax.servlet.ServletException: Problem in getRegionLst method of SearchDBjava.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
3) D:\WebSphere\AppServer\installedApps\globalrfx.ear\globalrfx.war\WEB-INF\classes\com\sharedapps\globalrfx\servlets\
Servlet: ServiceController.java
Bean : RequesterDB.java
Method : getPrevRequests()
The Following error has come in UT RFX : ServiceController - Case 200:com.sharedapps.common.dbconnection.DBException: Problem in getPrevRequests method of RequesterDBcom.sharedapps.common.dbconnection.DBException: com.sharedapps.common.dbconnection.DBException: com.sharedapps.common.dbconnection.DBException: java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
4) D:\WebSphere\AppServer\installedApps\globalrfx.ear\globalrfx.war\WEB-INF\classes\com\sharedapps\globalrfx\servlets\
Servlet: LoginController.java
Bean : RequesterDB.java
Method : getRequesterDetails()
The Following error has come in UT RFX : Login Controller - Case 0:com.sharedapps.common.dbconnection.DBException: Problem in getRequesterDetails method of RequesterDBcom.sharedapps.common.dbconnection.DBException: com.sharedapps.common.dbconnection.DBException: com.sharedapps.common.dbconnection.DBException: java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner

5) D:\WebSphere\AppServer\installedApps\globalrfx.ear\globalrfx.war\WEB-INF\classes\com\sharedapps\globalrfx\servlets\
Servlet: ServiceController.java
Bean : -
Method : -
The Following error has come in UT RFX : ServiceController - Case 102:java.lang.IllegalMonitorStateException: JVMLK003: current thread not owner
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic