We had an issue involving all java methods timing out from diff applications. It did not get resolved even after repeated JMS restarts (about 5 or 6 times). Then, we accessed the JBoss JMX console to take a thread dump. What we found was that most of the threads were blocked as below and the total thread count was going up from time to time. From the stack below, we could sense that there was something wrong with the BOF cache. So, we removed it and restarted the JMS. It worked this time around and the thread count became stable at about 78. Now, we want to know "why exactly" all the JBoss threads were stuck up at com.documentum.fc.client.impl.bof.compoundclass.CompoundClassMgr.getImpClass(CompoundClassMgr.java:63) ? What possible reasons there could be for CompoundClassMgr.getImpClass to remain blocked? We want to know this so we could avoid such occurrences in future
Thread: http-0.0.0.0-24080-3 : priority:5, demon:true, threadId:102, threadState:BLOCKED, lockName:java.lang.Object@677646
com.documentum.fc.client.impl.bof.compoundclass.CompoundClassMgr.getImpClass(CompoundClassMgr.java:63)
com.documentum.fc.client.impl.objectmanager.AbstractPersistentObjectFactory.getCompoundClassEntry(AbstractPersistentObjectFactory.java:39)
com.documentum.fc.client.impl.objectmanager.PObjectFactoryWithAspects.makeObject(PObjectFactoryWithAspects.java:48)
com.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObjectFromServer(PersistentObjectManager.java:356)
com.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObject(PersistentObjectManager.java:311)
com.documentum.fc.client.impl.session.Session.getObject(Session.java:834)
com.documentum.fc.client.impl.session.Session.getServerConfig(Session.java:648)
com.documentum.fc.client.impl.session.TicketCustodian.areMultiUseTicketsSupported(TicketCustodian.java:114)
com.documentum.fc.client.impl.session.TicketCustodian.learnTicketType(TicketCustodian.java:108)
com.documentum.fc.client.impl.session.TicketCustodian.refreshTicket(TicketCustodian.java:74)
com.documentum.fc.client.impl.session.TicketCustodian.refreshTicketIfNecessary(TicketCustodian.java:62)
com.documentum.fc.client.impl.session.ManagedLoginInfo.markLoginInfoSuccessfullyUsed(ManagedLoginInfo.java:78)
com.documentum.fc.client.impl.session.LoginInfoManager.markLoginInfoSuccessfullyUsed(LoginInfoManager.java:99)
com.documentum.fc.client.impl.session.SessionManager.getSessionFromFactory(SessionManager.java:105)
com.documentum.fc.client.impl.session.SessionManager.newSession(SessionManager.java:64)
com.documentum.fc.client.impl.session.SessionManager.getSession(SessionManager.java:168)
com.documentum.fc.client.DfClient$ClientImpl.newSession(DfClient.java:331)
com.ibm.lifesci.score.ral.dctm.methodserver.DctmCdXmlUtil.getSession(DctmCdXmlUtil.java:60)
com.ibm.lifesci.score.ral.dctm.methodserver.DctmCdXmlProcess.executeServerMethod(DctmCdXmlProcess.java:115)
com.ibm.lifesci.score.ral.dctm.methodserver.DctmCdXmlMethod.execute(DctmCdXmlMethod.java:128)
com.documentum.mthdservlet.DmMethodRunner.runIt(Unknown Source)
com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)
com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)
com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)
ENVIRONMENT INFORMATION
------------------------------------
<<Product Information>>
Product: Content Server
Version: 6.5 SP3
