Weblogic threads locked

We are noticing performance issue with our production environment. Production environment has a cluster of 6 weblogic instances and the server hangs very often and entire system go down. I have attached thread dump collected from one of the weblogic server. Any idea where is the issue? can you help please.
"ExecuteThread: '19' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x04f92f38 nid=0xb8c runnable [0x0713e000..0x0713fd94]
 at java.lang.Throwable.fillInStackTrace(Native Method)
 - waiting to lock <0x164ec610> (a java.lang.ClassNotFoundException)
 at java.lang.Throwable.<init>(Throwable.java:217)
 at java.lang.Exception.<init>(Exception.java:59)
 at java.lang.ClassNotFoundException.<init>(ClassNotFoundException.java:65)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
 - locked <0x173b3428> (a sun.misc.Launcher$AppClassLoader)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
 - locked <0x173b3428> (a sun.misc.Launcher$AppClassLoader)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
 - locked <0x173c1900> (a weblogic.utils.classloaders.GenericClassLoader)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
 - locked <0x17387ed8> (a weblogic.utils.classloaders.GenericClassLoader)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
 - locked <0x17dc9028> (a weblogic.utils.classloaders.GenericClassLoader)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:282)
 - locked <0x17db3a88> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
 at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
 at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
 - locked <0x17db3a88> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 - locked <0x17db3a88> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:141)
 at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:197)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
 at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:112)
 at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerMethod(BaseDeserializerFactory.java:201)
 at org.apache.axis.encoding.ser.BaseDeserializerFactory.getGetDeserializer(BaseDeserializerFactory.java:289)
 at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:171)
 at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:115)
 at org.apache.axis.encoding.ser.SimpleDeserializerFactory.getDeserializerAs(SimpleDeserializerFactory.java:107)
 at org.apache.axis.encoding.DeserializationContextImpl.getDeserializer(DeserializationContextImpl.java:452)
 at org.apache.axis.encoding.DeserializationContextImpl.getDeserializerForType(DeserializationContextImpl.java:467)
 at org.apache.axis.message.MessageElement.getValueAsType(MessageElement.java:571)
 at com.axeda.sdk.webservices.handlers.LoginHandler.findLogin(LoginHandler.java:153)
 at com.axeda.sdk.webservices.handlers.LoginHandler.handleRequest(LoginHandler.java:99)
 at com.axeda.sdk.webservices.handlers.LoginHandler.invoke(LoginHandler.java:78)
 at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
 at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
 at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
 at org.apache.axis.server.AxisServer.invoke(AxisServer.java:287)
 at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:854)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:339)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Try setting the 'Inactive connection timeout' value on the jdbc data source. Looks like your data source hangs. Also would be a good idea to set the 'test connections on reserve' on with test table sql.

Similar Messages

Thread lock in WL 8.1-on jRockit (queryMbeans)

I have noticed in our thread dumps of Weblogic 8.1 managed servers, the following lock:
"ExecuteThread: '2' for queue: 'weblogic.admin.RMI'" id=186 idx=0x182 tid=5292 prio=5 alive, in native, native_blocked, daemon
at jrockit/vm/Allocator.allocLargeArray(JIZ)Ljava/lang/Object;(Native Method)
at jrockit/vm/Allocator.allocArray(JIZ)Ljava/lang/Object;(Unknown Source)
at java/util/HashMap.resize(I)V(Unknown Source)
at java/util/HashMap.addEntry(ILjava/lang/Object;Ljava/lang/Object;I)V(Unknown Source)
at java/util/HashMap.put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
at java/util/HashSet.add(Ljava/lang/Object;)Z(HashSet.java:192)
at com/sun/management/jmx/RepositorySupport.query(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(RepositorySupport.java:241)
at com/sun/management/jmx/MBeanServerImpl.queryMBeans(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(MBeanServerImpl.java:1042)
^-- Holding lock: weblogic/management/internal/RemoteMBeanServerImpl@0x2000000008e78fc0[fat lock]
at weblogic/management/internal/RemoteMBeanServerImpl.queryMBeans(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(RemoteMBeanServerImpl.java:911)
at com/sun/management/jmx/MBeanServerImpl.queryNames(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(MBeanServerImpl.java:1075)
at weblogic/management/internal/MBeanHomeImpl.mbeanServerQuery(Ljavax/management/ObjectName;Ljavax/management/QueryExp;)Ljava/util/Set;(MBeanHomeImpl.java:487)
at weblogic/management/internal/MBeanHomeImpl.getMBeansByClass(Ljava/lang/Class;Ljava/lang/String;)Ljava/util/Set;(MBeanHomeImpl.java:311)
at weblogic/management/internal/MBeanHomeImpl_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)
at weblogic/rmi/internal/BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:492)
at weblogic/rmi/internal/BasicServerRef$1.run()Ljava/lang/Object;(BasicServerRef.java:435)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)
at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)
at weblogic/rmi/internal/BasicServerRef.handleRequest(Lweblogic/rmi/spi/InboundRequest;)V(BasicServerRef.java:430)
at weblogic/rmi/internal/BasicExecuteRequest.execute(Lweblogic/kernel/ExecuteThread;)V(BasicExecuteRequest.java:35)
at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:183)
at jrockit/vm/RNI.c2java(JJJJ)V(Native Method)
-- end of trace
Then a big number of other threads are blocked by this lock. An example is:
"ExecuteThread: '1' for queue: 'HZOZMsgEjbExecuteThreadQueue'" id=17 idx=0x30 tid=5123 prio=5 alive, in native, blocked, daemon
-- Blocked trying to get lock: weblogic/management/internal/RemoteMBeanServerImpl@0x2000000008e78fc0[fat lock]
at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
at jrockit/vm/Locks.fatLockBlockOrSpin(JLjrockit/vm/ObjectMonitor;II)V(Unknown Source)
at jrockit/vm/Locks.lockFat(Ljava/lang/Object;JLjrockit/vm/ObjectMonitor;Z)Ljava/lang/Object;(Unknown Source)
at jrockit/vm/Locks.monitorEnterSecondStage(Ljava/lang/Object;I)Ljava/lang/Object;(Unknown Source)
at jrockit/vm/Locks.monitorEnter(Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
at com/sun/management/jmx/MBeanServerImpl.internal_addObject(Ljava/lang/Object;Ljavax/management/ObjectName;)V(MBeanServerImpl.java:2379)
at com/sun/management/jmx/MBeanServerImpl.registerMBean(Ljava/lang/Object;Ljavax/management/ObjectName;)Ljavax/management/ObjectInstance;(MBeanServerImpl.java:876)
at weblogic/management/internal/RemoteMBeanServerImpl.private_registerMBean(Ljava/lang/Object;Ljavax/management/ObjectName;)Ljavax/management/ObjectInstance;(RemoteMBeanServerImpl.java:614)
at weblogic/management/internal/RemoteMBeanServerImpl.registerMBean(Ljava/lang/Object;Ljavax/management/ObjectName;)Ljavax/management/ObjectInstance;(RemoteMBeanServerImpl.java:554)
at weblogic/management/runtime/RuntimeMBeanDelegate.register()V(RuntimeMBeanDelegate.java:166)
at weblogic/management/runtime/RuntimeMBeanDelegate.<init>(Ljava/lang/String;Lweblogic/management/runtime/RuntimeMBean;Z)V(RuntimeMBeanDelegate.java:122)
at weblogic/management/runtime/RuntimeMBeanDelegate.<init>(Ljava/lang/String;Lweblogic/management/runtime/RuntimeMBean;)V(RuntimeMBeanDelegate.java:85)
at weblogic/jms/frontend/FEConnection.<init>(Lweblogic/jms/frontend/FEConnectionFactory;Ljava/lang/String;Lweblogic/jms/common/JMSID;Lweblogic/jms/dispatcher/Dispatcher;IIJJJJLjava/lang/String;JZZIIIZZ)V(FEConnection.java:183)
at weblogic/jms/frontend/FEConnectionFactory$1.run()Ljava/lang/Object;(FEConnectionFactory.java:434)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)
at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)
at weblogic/jms/frontend/FEConnectionFactory.connectionCreateInternal(Lweblogic/jms/dispatcher/DispatcherWrapper;Z)Lweblogic/jms/client/JMSConnection;(FEConnectionFactory.java:430)
at weblogic/jms/frontend/FEConnectionFactory.connectionCreate(Lweblogic/jms/dispatcher/DispatcherWrapper;)Lweblogic/jms/client/JMSConnection;(FEConnectionFactory.java:371)
at weblogic/jms/client/JMSConnectionFactory.createConnectionInternal(Ljava/lang/String;Ljava/lang/String;Z)Lweblogic/jms/client/JMSConnection;(JMSConnectionFactory.java:148)
at weblogic/jms/client/JMSConnectionFactory.createQueueConnection()Ljavax/jms/QueueConnection;(JMSConnectionFactory.java:75)
at gr/cosmote/common/util/UtilLib.putObjToQueue(IILjava/io/Serializable;JLgr/cosmote/common/bus/LoginInfo;)V(UtilLib.java:664)
at gr/cosmote/common/util/UtilLib.putObjToQueue(IILjava/io/Serializable;Lgr/cosmote/common/bus/LoginInfo;)V(UtilLib.java:636)
at gr/cosmote/bus/session/HZOZQueueBean.handleMozartCallbackVO(Lgr/cosmote/common/bus/mozartVOs/MozartCallbackVO;)V(HZOZQueueBean.java:418)
at gr/cosmote/bus/session/HZOZQueueBean.onMessage(Ljavax/jms/Message;)V(HZOZQueueBean.java:191)
at weblogic/ejb20/internal/MDListener.execute(Lweblogic/kernel/ExecuteThread;)V(MDListener.java:400)
at weblogic/ejb20/internal/MDListener.transactionalOnMessage(Ljavax/jms/Message;)V(MDListener.java:333)
at weblogic/ejb20/internal/MDListener.onMessage(Ljavax/jms/Message;)V(MDListener.java:298)
at weblogic/jms/client/JMSSession.onMessage(Ljavax/jms/MessageListener;Lweblogic/jms/common/MessageImpl;)V(JMSSession.java:2686)
at weblogic/jms/client/JMSSession.execute(Lweblogic/kernel/ExecuteThread;)V(JMSSession.java:2598)
at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:183)
at jrockit/vm/RNI.c2java(JJJJ)V(Native Method)
-- end of trace
What is this 'weblogic.admin.RMI' queue?
What I understand so far is that the object that appears as locked (RemoteMBeanServerImpl) is used to initiate and instantiate ejb/rmi calls from the managed servers. Does it attempt some sort of connection to the admin? Something else quite interesting that I read somewhere, that when this call (queryMBeans) is performed, the result is handled by a non thread-safe collection object which could (as a result of a weblogic bug) result in an infinite loop.
By the way, our set up is 1 cluster, 4 managed servers in 4 different machines. The admin is installed along with one of the managed. All servers are configured to start/stop/run independently.
Anybody any ideas?

hi,
What is this 'weblogic.admin.RMI' queue has the threads executing the calls from remote managed servers to the Admin Server and from the Admin Server to the managed servers for internal status updates.
There was a bug in wls 8.1 where the call the to the admin server from all the managed server in the cluster used to create a thread lock state.
Contact the Oracle support for the related CR and the patch.
thanks,
Sandeep

Weblogic.ejb20.locks.LockTimedOutException ???

Hi Iam getting a LockTimedOutException while calling a bean method..what could
be the reason and this is permenent..occuring all the time..
Below I have given the stack trace..
what could be the problem??
Thanks
Perianayagam.T
####<Jun 10, 2003 8:59:28 AM EDT> <Info> <EJB> <dssappsrv01> <myServer> <ExecuteThread:
'3' for queue: 'default'> <> <> <010051> <EJB Exception during invocation from
home: com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_HomeImpl@9c1ee threw exception:
weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:EnterpriseUser
with primary key:<user dn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.com"/>
timed-out after waiting 60,000 ms. The transaction or thread requesting the lock
was:Name=[EJB com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for queue:
'default',5,Thread Group for Queue: 'default'],SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).>
weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:EnterpriseUser
with primary key:<user dn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.com"/>
timed-out after waiting 60,000 ms. The transaction or thread requesting the lock
was:Name=[EJB com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for queue:
'default',5,Thread Group for Queue: 'default'],SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).
 at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:528)
 at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
 at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityManager.java:164)
 at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:219)
 at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:198)
 at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
 at weblogic.ejb20.internal.EntityEJBObject.preInvoke(EntityEJBObject.java:89)
 at com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean_svris_EOImpl.getRoles(EnterpriseUserBean_svris_EOImpl.java:333)
 at com.hns.iag.acapulco.ejb.elm.ELMBean.getEnterpriseUserRoles(ELMBean.java:1392)
 at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl.getEnterpriseUserRoles(ELMBean_1h1i_EOImpl.java:2587)
 at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
 at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Hi Perianayagam,
This error is fixed in weblogic 6.1SP4 and 7.0 SP3.
Regards,
Slava Imeshev
"Perianayagam.T" <[email protected]> wrote in message
news:[email protected]...
>
Hi Iam getting a LockTimedOutException while calling a bean method..whatcould
be the reason and this is permenent..occuring all the time..
Below I have given the stack trace..
what could be the problem??
Thanks
Perianayagam.T
####<Jun 10, 2003 8:59:28 AM EDT> <Info> <EJB> <dssappsrv01> <myServer><ExecuteThread:
'3' for queue: 'default'> <> <> <010051> <EJB Exception during invocationfrom
home: com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_HomeImpl@9c1ee threwexception:
weblogic.ejb20.locks.LockTimedOutException: The lock request fromEJB:EnterpriseUser
with primary key:<userdn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.c
om"/>
timed-out after waiting 60,000 ms. The transaction or thread requestingthe lock
was:Name=[EJBcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,n
umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for
queue:> 'default',5,Thread Group for Queue:'default',SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
>
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCo
ordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).>
weblogic.ejb20.locks.LockTimedOutException: The lock request fromEJB:EnterpriseUser
with primary key:<userdn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.c
om"/>
timed-out after waiting 60,000 ms. The transaction or thread requestingthe lock
was:Name=[EJBcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,n
umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for
queue:> 'default',5,Thread Group for Queue:'default',SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
>
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCo
ordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).
atweblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManag
er.java:528)
atweblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258
atweblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityMan
ager.java:164)
atweblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityMa
nager.java:219)
atweblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManag
er.java:198)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
atweblogic.ejb20.internal.EntityEJBObject.preInvoke(EntityEJBObject.java:89)
atcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean_svris_EOImpl.ge
tRoles(EnterpriseUserBean_svris_EOImpl.java:333)
atcom.hns.iag.acapulco.ejb.elm.ELMBean.getEnterpriseUserRoles(ELMBean.java:139
2)
atcom.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl.getEnterpriseUserRoles(ELMB
ean_1h1i_EOImpl.java:2587)
at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Weblogic.ejb20.locks.LockTimedOutException and pb with weblogic-ejb-jar.xml

Hello All,
I get a strange problem when I try to log in to the J2EE application based on EJBs:
weblogic.ejb20.locks.LockTimedOutException
I see that I can add an option to the weblogic-ejb-jar.xml file, and I hope that can help for my previous problem:
<weblogic-enterprise-bean><stateful-session-descriptor>
<allow-concurrent-calls>true</allow-concurrent-calls>
</stateful-session-descriptor></weblogic-enterprise-bean>
But I can not edit the weblogic-ejb-jar.xml file under JBuilder ! the file is probably read-only, but I do not know how to change the property. I can not find this file directly under JBuilder directories.
So I have tried to open the module.jar that contained this file. I have checked: the file is not read-only. I have modified directly manually the weblogic-ejb-jar.xml file, but now I get this error in Jbuilder when I open the weblogic-ejb-jar.xml file:
URL: Transformation requires a XSL StyleSheetThe Node does not have a style sheet associated with itEither add a style sheet using the Add stylesheets button on the toolbar or add a valid XSL Processing instruction to the document directly
In conclusion, what should I do to be able to modify the weblogic-ejb-jar.xml file properly ??

Ok in a way I have solved my problem (even if I am not completely satisfied by the way on how to proceed...). So thanks to message "JBuilder7.0 and Weblogic6.1" on EJB sun forum :
http://forum.java.sun.com/thread.jsp?thread=285735&forum=13&message=1255488
I have tried the following actions (mentionned in the other forum messages):
- To preserve changes to weblogic*.xml, the safest way is to change the ejb-borland.xml.
(I am not sure that I have applied this advice correctly, because I suppose that syntax is not similar in weblogic file or borland file).
And you can MANUALLY update the weblogic file in your JAR archive.
1. Open the EJB JAR file in Winzip and extract the weblogic-ejb-jar.xml file, so that a copy exists in your
project directory.
2. Open this file (in Notepad), add the WebLogic specific information, and then save the file.
3. Now, when you are finished with the build cycle and are ready to deploy, you may open the EJB jar file
and swap in the weblogic-ejb-jar.xml file."
Good Luck.

WLS Container Threads LOCKED

Apologize for this cross-post but I posted in in probably wrong group
Found several WLS Jrockit Threads LOCKED. We are using jrockit81sp2rp1_141_06
System got HUNG
All MUXERS are LOCKED show SocketResetException that seems funny ?
Thanks
Harish
[enablersthreaddump.txt]

Hi,
I'm also facing the same problem, but my server is WLI 8.1 SP2. When we restarted the server for couple of times, it started working fine. but why it is coming? also restarting production server is not a possible solution.
Any one has answers?
Thanks,
Chandra. T

Weblogic thread issue

I am using Weblogic portal server 7.0 SP2
Lately, whenever there is a backend system failure (database or any other system), eventually, all weblogic threads wait for the backend connection and get stuck. I get following message for all threads
ExecuteThread: '28' for queue: 'default' has been busy for "785" seconds working on the request "Http Request: XXXXXX, which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Any idea why such a thing can happen?

You have a contention problem at back end ...

Weblogic Thread hogging at java.io.WinNTFileSystem.getBooleanAttributes at high loads

Hi,
At high loads, we are seeing that one WebLogic thread is active on a windows native call for quite some time.. I can see the following stack statements in thread dumps taken at 10 minutes interval. This has led to slow server performance.
This happens on WebLogic 10.3.2 that is hosted in Windows Server 64 bit 2008 Enterprise Edition SP1.
The JDK used is JRockit jdk1.6.0_20-R28.3.2 (64 Bit)
Also this happens at high user loads only and also irregularly.
Our eclipse link versions are (Implementation-Version: 1.0.1-20080905, Specification-Version: 1.0.1)
Any recommendation or pointer is appreciated.
Now the thread dump details
"[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE
 java.io.WinNTFileSystem.getBooleanAttributes(Native Method)
 java.io.File.isDirectory(File.java:754)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive$1.accept(DirectoryArchive.java:91)
 java.io.File.listFiles(File.java:1134)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:89)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.<init>(DirectoryArchive.java:73)
 org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.<init>(DirectoryArchive.java:55)
 org.eclipse.persistence.internal.jpa.deployment.ArchiveFactoryImpl.createArchive(ArchiveFactoryImpl.java:76)
 org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.findPersistenceArchives(PersistenceUnitProcessor.java:184)
 org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.initialize(JPAInitializer.java:132)
 org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactory(PersistenceProvider.java:104)
 org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactory(PersistenceProvider.java:64)
 javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:78)
 javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:54)
 -- Our internal class calls
 org.jbpm.graph.def.Action.execute(Action.java:123)
 org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:235)
 org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:212)
 org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphElement.java:182)
 org.jbpm.graph.def.GraphElement.fireEvent(GraphElement.java:166)
 org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:120)
 org.jbpm.JbpmContext.newProcessInstance(JbpmContext.java:372)
 -- Our internal class calls
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 java.lang.reflect.Method.invoke(Method.java:597)
 org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:129)
 org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
 javax.faces.component.UICommand.broadcast(UICommand.java:106)
 org.ajax4jsf.framework.ajax.AjaxViewRoot.processEvents(AjaxViewRoot.java:180)
 org.ajax4jsf.framework.ajax.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:158)
 org.ajax4jsf.framework.ajax.AjaxViewRoot.processApplication(AjaxViewRoot.java:346)
 org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
 org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
 -- Our internal class calls
 javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
 weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
 org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 com.anychart.servlet.ResourceFilter.doFilter(ResourceFilter.java:53)
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 -- Our internal class calls
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 -- Our internal class calls
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
 weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
Maybe this thread could help, if it addresses your problem correctly:
Performance issues with class loader on Windows server
Regards,
Mohab

Thread Locking Exception

Hi All,
Many times while working on MDM via MDM API's I received Thread Locking Exception. This Exception is so severe that it leads MDM Data Manager in hanged state and get resolved only by restarting the server. Sometimes I do not get this exception but Data Manager gets hanged, even I am unable to open Console also. Please answer this question.
Thanks ..
Vibha

Hello All,
Still we haven't able to resolve this issue. We already have SR with oracle. So many logs were captured.
Below is the snippet of seedSchedulerdata.log
${work.dir}Entered Validate methodExiting Validate method------------------------------------------------------------
Start seeding task
job name--> Password Expiration Task
schTaskName--> Password Expiration Task
task class name--> com.thortech.xl.schedule.tasks.tcTskPasswordExpiration
task job disable--> 0
task frequency--> DAILY
task maxRetries--> 5
task retryCount--> 0
task paramName--> Email Definition Name
task paramValue--> Password Expired
task paramTpe--> String
Updating Job :Password Expiration Task with keys
java.lang.Exception: Unable to seed scheduler data due to configuration problems. Contact System Administrator
at oracle.iam.scheduler.seed.SeedSchedulerData.startSeeding(SeedSchedulerData.java:770)
at oracle.iam.scheduler.seed.SeedSchedulerData.main(SeedSchedulerData.java:113)
If any of them faced such issue please help.
Thanks
DK

Thread lock

Dear Moderator,
I wanted to know the answers of some questions which were asked to me during interview. So I posted those questions in the Forum on 1st December. But today when I logged in to check the answers, I found the thread locked. Can you please let me know on what basis a thread is locked.
Regards,
D. Mallick
Moved from Test and Playground forum.
Edited by: kishan P on Dec 3, 2010 11:22 PM

I can remember moving one of them which several forum members where complaining about (understandably).
I mean... I can imagine encountering a thread called "questions" even although it is a meaninglessly stupid subject title, but what are we to find usefull in answers ??
Get some fresh air over the weekend. You have some reading to do next week.
Cheers,
Julius

SEVERE: User weblogic soft locked

Hi.,
I am new to Weblogic, How do I get pass this error? while starting up Admin and Managed nodes all servers startup logs showing the same mesg. still I was able to login to weblogic admin console, not sure exactly where it is looking for the password? I tryed to update weblogic password in OID too, but no luck, not sure whether I can put hardcoded password in Database or not. If I had to put encrypted password in OID repository what should i put? boot.properties or defaultauthenticator.ldift? Pl. Help me to bypass this issue.

Thanks Faisal for quick response, Here is what I noticed while starting up weblogic server components on different nodes.
Admin Node startup Log
INFO: populated user attributes from db
Jan 4, 2011 1:31:11 PM oracle.iam.platform.utils.portability.OIMPlatformFactory getInstance()
INFO: Found Weblogic Application Server Platform. returning OIMWebLogicPlatform
Jan 4, 2011 1:31:11 PM oracle.iam.platform.auth.impl.DBStore incrementLoginAttempts
INFO: Increased failed login attempts for user weblogic
Jan 4, 2011 1:31:11 PM oracle.iam.platform.auth.impl.Authenticator authenticateWithPassword
SEVERE: Authentication of user weblogic failed because of invalid password
<Jan 4, 2011 1:31:27 PM CST> <Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be available via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to false.>
<Jan 4, 2011 1:31:41 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jan 4, 2011 1:31:41 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jan 4, 2011 1:32:11 PM CST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
OID Startup log
Jan 4, 2011 1:38:27 PM oracle.iam.platform.auth.impl.DBStore initializeDataSource
INFO: Pool data source initialized successfully
Jan 4, 2011 1:38:29 PM oracle.iam.platform.auth.impl.DBStore populateUserFromResultSet
INFO: populated user attributes from db
Jan 4, 2011 1:38:29 PM oracle.iam.platform.utils.portability.OIMPlatformFactory getInstance()
INFO: Found Weblogic Application Server Platform. returning OIMWebLogicPlatform
Jan 4, 2011 1:38:29 PM oracle.iam.platform.auth.impl.DBStore incrementLoginAttempts
INFO: Increased failed login attempts for user weblogic
Jan 4, 2011 1:38:29 PM oracle.iam.platform.auth.impl.Authenticator authenticateWithPassword
SEVERE: Authentication of user weblogic failed because of invalid password
Jan 4, 2011 1:38:30 PM oracle.iam.platform.auth.impl.DBStore populateUserFromResultSet
INFO: populated user attributes from db
Jan 4, 2011 1:38:30 PM oracle.iam.platform.auth.impl.DBStore incrementLoginAttemptsAndLockUser
SEVERE: User weblogic locked at 2011-01-04
Jan 4, 2011 1:38:30 PM oracle.iam.platform.auth.impl.Authenticator authenticateWithPassword
SEVERE: Authentication of user weblogic failed because of invalid password
<Jan 4, 2011 1:38:31 PM CST> <Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be available via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to false.>
<Jan 4, 2011 1:38:35 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jan 4, 2011 1:38:35 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
OAM1 Startup Log
INFO: Authentication module initialized
<Jan 4, 2011 1:48:10 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
Jan 4, 2011 1:48:10 PM oracle.iam.platform.auth.impl.DBStore initializeDataSource
INFO: Pool data source initialized successfully
Jan 4, 2011 1:48:13 PM oracle.iam.platform.auth.impl.DBStore populateUserFromResultSet
INFO: populated user attributes from db
Jan 4, 2011 1:48:13 PM oracle.iam.platform.auth.impl.Authenticator getUserFromIDStore
SEVERE: User weblogic soft locked
<Jan 4, 2011 1:48:14 PM CST> <Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be available via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to false.>
<Jan 4, 2011 1:48:18 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
OAM2 startup log
INFO: Authentication module initialized
<Jan 4, 2011 1:50:58 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
Jan 4, 2011 1:50:59 PM oracle.iam.platform.auth.impl.DBStore initializeDataSource
INFO: Pool data source initialized successfully
Jan 4, 2011 1:51:01 PM oracle.iam.platform.auth.impl.DBStore populateUserFromResultSet
INFO: populated user attributes from db
Jan 4, 2011 1:51:01 PM oracle.iam.platform.auth.impl.Authenticator getUserFromIDStore
SEVERE: User weblogic soft locked
<Jan 4, 2011 1:51:03 PM CST> <Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

Threads/Locks within EJBs

I'm trying to get a good handle on the reason there are restrictions on threading/locking
semantics used from within application code dealing with EJBs. I think the idea
is the application code shouldn't do anything to interfere with the locking of
the ejbs done from within the container at various stages in their lifecycle.
So, I shouldn't subject the bean implemenation class to any explicit synch. But
what about spawning threads from within my EJBs? In 3rd party classes used by
my EJBs?
Any clear explanation is gratefully appreciated.
Max

Max
See section 24.1.2 "Programming restrictions" in the ejb20 final release specification.
Thanks
Jim
Max wrote:
I'm trying to get a good handle on the reason there are restrictions on threading/locking
semantics used from within application code dealing with EJBs. I think the idea
is the application code shouldn't do anything to interfere with the locking of
the ejbs done from within the container at various stages in their lifecycle.
So, I shouldn't subject the bean implemenation class to any explicit synch. But
what about spawning threads from within my EJBs? In 3rd party classes used by
my EJBs?
Any clear explanation is gratefully appreciated.
Max[Reply.vcf]

Weblogic threads getting stuck at setAutoCommit

Hi,
We are using Weblogic 10.3.4 in our production environment with Oracle 11g backend.
Yesterday two of the transactions timed-out as the threads running these transactions blocked at the setAutoCommit method. Upon checking the de-compiled classes in ojdbc.jar, the threads seem to try obtaining a lock to execute the synchronized method doSetAutoCommit in T4CConnection class.
There were no other transactions running at the time the thread dump was taken. What could be be reason for two threads to block at the same method while no other thread seems to hold the lock?
Please find the stack traces from the thread dump below. Both the threads were running the same application transaction (perhaps 2 users initiated the transaction or the same user tried the transaction twice).
"[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock oracle.jdbc.driver.T4CConnection@ee159e BLOCKED
     oracle.jdbc.driver.PhysicalConnection.setAutoCommit(PhysicalConnection.java:3735)
     oracle.jdbc.OracleConnectionWrapper.setAutoCommit(OracleConnectionWrapper.java:130)
     weblogic.jdbc.wrapper.XAConnection.setAutoCommit(XAConnection.java:833)
     weblogic.jdbc.wrapper.JTAConnection.recoverAutoCommitState(JTAConnection.java:237)
     weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:222)
     weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:74)
     weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:65)
     weblogic.jdbc.wrapper.Statement.checkStatement(Statement.java:315)
     weblogic.jdbc.wrapper.Statement.doClose(Statement.java:411)
     weblogic.jdbc.wrapper.Statement.close(Statement.java:398)
"[STUCK] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock oracle.jdbc.driver.T4CConnection@1d67b41 BLOCKED
     oracle.jdbc.driver.PhysicalConnection.setAutoCommit(PhysicalConnection.java:3735)
     oracle.jdbc.OracleConnectionWrapper.setAutoCommit(OracleConnectionWrapper.java:130)
     weblogic.jdbc.wrapper.XAConnection.setAutoCommit(XAConnection.java:833)
     weblogic.jdbc.wrapper.JTAConnection.recoverAutoCommitState(JTAConnection.java:237)
     weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:222)
     weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:74)
     weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:65)
     weblogic.jdbc.wrapper.Statement.checkStatement(Statement.java:315)
     weblogic.jdbc.wrapper.Statement.doClose(Statement.java:411)
     weblogic.jdbc.wrapper.Statement.close(Statement.java:398)

I'd like to see the full stacktraces. It is an error to have two application threads operating on the
same JDBC connection or any of it's subobjects, or operating on behalf of the same global
transaction.

Weblogic Threads Deadlock

We are experiencing a problem with web services communicating within a weblogic managed server configured with 15 threads. When we have 2 web services in the managed server (named A and B), after flooding A with 20 or more simultaneous requests, we begin to get socket timeouts on the inbound side of A. The throughput goes to zero and the number of queued requests continues to climb.
This does not happen if we flood the inbound side of B. It happily handles over 100 requests.
Are there restrictions on running multiple web services within weblogic managed servers?

Hi,
There is no restriction on the number of services that may run on a managed server. Can you tell the WL version you are using? Is the service using SSL? WL 8.1.5 (or 8.1.6, I am not sure) fixes an SSL bug that causes something similar to what you are experiencing.
Regards,
LG

Type 2 jdbc driver cause weblogic thread dump

we have weblogic 5.1(sp6) running on redhat linux 7.1
we install oracle client (8.1.7.0.0) and jdbc12(classes12.zip).
the connection pool use type 2 driver
oracle.jdbc.driver.OracleDriver
the jdk is 1.3.1 b24 (we have try -native -server -hotspot)
sometime weblogic crash , the error output is:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x51dc0310
Function name=kpufGetRcvInfo
Library=/usr/local/oracle/product/8.1.7/lib/libclntsh.so.8.0
Current Java thread:
at oracle.jdbc.oci8.OCIDBAccess.close_query(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.closeQuery(OCIDBAccess.java:541)
at oracle.jdbc.driver.OracleResultSetImpl.internal_close(OracleResultSet
Impl.java:627)
at oracle.jdbc.driver.OracleResultSetImpl.close(OracleResultSetImpl.java
:118)
at weblogic.jdbcbase.pool.ResultSet.close(ResultSet.java:166)
at weblogic.jdbc20.rmi.internal.ResultSetImpl.close(ResultSetImpl.java:5
1)
at weblogic.jdbc20.rmi.SerialResultSet.close(SerialResultSet.java:54)
for some reason , we can't change to type 4 driver .
any advice is very thanks

Hi Owen,
You may have to get the latest patchset from oracle for your OCI client
libraries. You should talk to Oracle support about this problem as the core
dump is due to Oracle's driver.
sree
"Owen He" <[email protected]> wrote in message
news:3cf5940c$[email protected]..
>
we have weblogic 5.1(sp6) running on redhat linux 7.1
we install oracle client (8.1.7.0.0) and jdbc12(classes12.zip).
the connection pool use type 2 driver
oracle.jdbc.driver.OracleDriver
the jdk is 1.3.1 b24 (we have try -native -server -hotspot)
sometime weblogic crash , the error output is:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x51dc0310
Function name=kpufGetRcvInfo
Library=/usr/local/oracle/product/8.1.7/lib/libclntsh.so.8.0
Current Java thread:
at oracle.jdbc.oci8.OCIDBAccess.close_query(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.closeQuery(OCIDBAccess.java:541)
atoracle.jdbc.driver.OracleResultSetImpl.internal_close(OracleResultSet
Impl.java:627)
atoracle.jdbc.driver.OracleResultSetImpl.close(OracleResultSetImpl.java
:118)
at weblogic.jdbcbase.pool.ResultSet.close(ResultSet.java:166)
atweblogic.jdbc20.rmi.internal.ResultSetImpl.close(ResultSetImpl.java:5
1)
atweblogic.jdbc20.rmi.SerialResultSet.close(SerialResultSet.java:54)
>
>
for some reason , we can't change to type 4 driver .
any advice is very thanks

Weblogic Thread Management

Hello Buddies,
We are facing performance problem in our J2EE application. For our application, Native Thread Management is enabled(EnableNativeIO=true).
But, while starting the weblogic server(managed server), we are getting the following message.
####<Oct 16, 2008 12:40:25 PM BST> <Warning> <Socket>
<wrohstsco10> <gc3-wrohstsco10>
<ListenThread.Default> <<WLS Kernel>> <>
<BEA-000402> <There are: 9 active sockets, but the maximum
number of socket reader threads allowed by the configuration is: 8. You
may want to alter your configuration.>
Can any one suggest on this?
Regards
Senthil Nathan M

you know that Native IO is enabled if you see "Native IO Enabled" in the server log at startup. This means that it founds the native IO shared libraries at startup.
You've probably already seen this, but this is from the WebLogic docs, at <http://e-docs.bea.com/wls/docs100/messages/Socket.html>
BEA-000402
Warning: There are: numSockets active sockets, but the maximum number of socket reader threads allowed by the configuration is: getMaxSocketReaders. You may want to alter your configuration.
Description
A non-native IO is being used, and the number of
socket reader threads is less than the number of active sockets.
Performance may degrade significantly. It is recommended that you
change the socket reader settings to improve the performance.
Cause
When non-native IO is used, IO is performed in a
blocking manner. Therefore, if the number of socket reader threads is
less than the number of active sockets, performance may degrade
significantly.
Action
Increase ThreadPoolPercentSocketReaders and/or
ThreadPoolSize, and/or decrease SocketReaderTimeoutMinMillis and/or
SocketReaderTimeoutMaxMillis.
This would imply what you understand. If you are seeing "Native IO Enabled" in your server log, but you are getting that warning, then I would first simply follow the advice in the message description that applies if you are using non-native IO. After experimenting with that (whether it works or not), I would file a support case asking first why you're getting that warning if you have native IO enabled, and whether following this advice for non-native IO should resolve your problem.

Weblogic threads locked

Similar Messages

Maybe you are looking for