RE: [JBoss-user] home.findByPrimaryKey HANGS!!!!!!!!!!!!!!!!!!!!!!!!!
Thanks Jason. I will try that. -Saroj -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jason Westra Sent: Friday, September 20, 2002 10:40 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] home.findByPrimaryKey HANGS! Saroj, You could try configuring your settings in ejb-jar.xml to be "Supports" for your entity bean "getters" and finders. This should keep locks from happening as well. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Saroj Kumar Sent: Friday, September 20, 2002 4:35 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] home.findByPrimaryKey HANGS! Hi Dain, The Problem is solved. But, I am not able to pinpoint the reason. I just made a small change in my Oracle-Service.xml To reflect the TX Isolation Level. TRANSACTION_READ_COMMITTED I did this change because of this reason : StackTrace shows that org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock class Is waiting for TX Lock. I checked the ORACLE 9i for any lock but could not find any such lock. QueuedPessimisticEJBLock gave me the idea that may be Jboss is making the ISOLATION LEVEL as SERIALIZABLE and thus trying to get a EXCLUSIVE Lock whereas Oracle is using READ COMMITED Lock and not allowing the container to get the EXCLUSIVE Lock. This led me to add this line as per David Jencks's earlier mail( Thanks a lot David). Once I added this line, it worked fine. Now comes the puzzling behaviour. I removed these lines again from Oracle-service.xml to Make sure that this was the cause of the problem. But, Surprise!!! It was working fine. Still It is working fine without this line in oracle-service.xml. I am not able to understand this behaviour at all. Anyway, it is working fine. Thanks, Saroj -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dain Sundstrom Sent: Thursday, September 19, 2002 10:59 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] home.findByPrimaryKey HANGS! Have you done a thread dump when it hangs? Where is it waiting. My guess is you database is locked somehow. -dain Saroj Kumar wrote: > Hi! > Ive been struggling with this for quite some time.I have some Jsps > deployed in > Tomcat 4.04 which then call EJB components hosted on Jboss 3.0.1. > I have session and entity beans(CMP2.0) deployed on Jboss. > > My session beans calls a java class which in turn tries to do a > home.findByPrimaryKey on > an entity and hangs.When I do the same using a standalone java client > it works..but not > through the Jsps hosted on Tomcat. > > Also setEntityContext is called and ejbActivate and EJBLoad are not > called. > It just hangs and then times out after some time with the following > stack trace > > > > 22:29:03,839 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//13, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,104 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//17, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,224 ERROR [BeanLock] Thread[Thread-20,5,RMI Runtime]Saw rolled > back tx=TransactionImpl:XidImpl [FormatId=257, Global > Id=mdpcad110773//17, BranchQual=] waiting for txLock > 22:29:07,264 ERROR [LogInterceptor] TransactionRolledbackLocalException, > causedBy: > java.lang.RuntimeException: Transaction marked for rollback, possibly a > timeout > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedPess > imisticEJBLock.java:325) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(QueuedPes > simisticEJBLock.java:189) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.schedule(QueuedPessi > misticEJBLock.java:140) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor > .java:103) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInt > erceptor.java:69) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > ptor.java:107) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > CMT.java:178) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) > at > org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav > a:130) > at > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) > at > org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) > at > org.jboss.ejb.plugins.local.Ba
RE: [JBoss-user] home.findByPrimaryKey HANGS!!!!!!!!!!!!!!!!!!!!!!!!!
Saroj, You could try configuring your settings in ejb-jar.xml to be "Supports" for your entity bean "getters" and finders. This should keep locks from happening as well. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Saroj Kumar Sent: Friday, September 20, 2002 4:35 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] home.findByPrimaryKey HANGS! Hi Dain, The Problem is solved. But, I am not able to pinpoint the reason. I just made a small change in my Oracle-Service.xml To reflect the TX Isolation Level. TRANSACTION_READ_COMMITTED I did this change because of this reason : StackTrace shows that org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock class Is waiting for TX Lock. I checked the ORACLE 9i for any lock but could not find any such lock. QueuedPessimisticEJBLock gave me the idea that may be Jboss is making the ISOLATION LEVEL as SERIALIZABLE and thus trying to get a EXCLUSIVE Lock whereas Oracle is using READ COMMITED Lock and not allowing the container to get the EXCLUSIVE Lock. This led me to add this line as per David Jencks's earlier mail( Thanks a lot David). Once I added this line, it worked fine. Now comes the puzzling behaviour. I removed these lines again from Oracle-service.xml to Make sure that this was the cause of the problem. But, Surprise!!! It was working fine. Still It is working fine without this line in oracle-service.xml. I am not able to understand this behaviour at all. Anyway, it is working fine. Thanks, Saroj -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dain Sundstrom Sent: Thursday, September 19, 2002 10:59 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] home.findByPrimaryKey HANGS! Have you done a thread dump when it hangs? Where is it waiting. My guess is you database is locked somehow. -dain Saroj Kumar wrote: > Hi! > Ive been struggling with this for quite some time.I have some Jsps > deployed in > Tomcat 4.04 which then call EJB components hosted on Jboss 3.0.1. > I have session and entity beans(CMP2.0) deployed on Jboss. > > My session beans calls a java class which in turn tries to do a > home.findByPrimaryKey on > an entity and hangs.When I do the same using a standalone java client > it works..but not > through the Jsps hosted on Tomcat. > > Also setEntityContext is called and ejbActivate and EJBLoad are not > called. > It just hangs and then times out after some time with the following > stack trace > > > > 22:29:03,839 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//13, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,104 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//17, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,224 ERROR [BeanLock] Thread[Thread-20,5,RMI Runtime]Saw rolled > back tx=TransactionImpl:XidImpl [FormatId=257, Global > Id=mdpcad110773//17, BranchQual=] waiting for txLock > 22:29:07,264 ERROR [LogInterceptor] TransactionRolledbackLocalException, > causedBy: > java.lang.RuntimeException: Transaction marked for rollback, possibly a > timeout > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedPess > imisticEJBLock.java:325) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(QueuedPes > simisticEJBLock.java:189) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.schedule(QueuedPessi > misticEJBLock.java:140) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor > .java:103) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInt > erceptor.java:69) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > ptor.java:107) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > CMT.java:178) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) > at > org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav > a:130) > at > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) > at > org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) > at > org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.invoke(BaseLocalCo > ntainerInvoker.java:301) > at > org.jboss.ejb.plugins.local.EntityProxy.invoke(EntityProxy.java:38) > at $Proxy232.getCreatedBy(Unknown Source) > at > com.cadmus.rpm.domain.session.ModelFactory.ModelFactoryGenBean.getArticl > e(Unknown S
RE: [JBoss-user] home.findByPrimaryKey HANGS!!!!!!!!!!!!!!!!!!!!!!!!!
Hi Dain, The Problem is solved. But, I am not able to pinpoint the reason. I just made a small change in my Oracle-Service.xml To reflect the TX Isolation Level. TRANSACTION_READ_COMMITTED I did this change because of this reason : StackTrace shows that org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock class Is waiting for TX Lock. I checked the ORACLE 9i for any lock but could not find any such lock. QueuedPessimisticEJBLock gave me the idea that may be Jboss is making the ISOLATION LEVEL as SERIALIZABLE and thus trying to get a EXCLUSIVE Lock whereas Oracle is using READ COMMITED Lock and not allowing the container to get the EXCLUSIVE Lock. This led me to add this line as per David Jencks's earlier mail( Thanks a lot David). Once I added this line, it worked fine. Now comes the puzzling behaviour. I removed these lines again from Oracle-service.xml to Make sure that this was the cause of the problem. But, Surprise!!! It was working fine. Still It is working fine without this line in oracle-service.xml. I am not able to understand this behaviour at all. Anyway, it is working fine. Thanks, Saroj -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dain Sundstrom Sent: Thursday, September 19, 2002 10:59 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] home.findByPrimaryKey HANGS! Have you done a thread dump when it hangs? Where is it waiting. My guess is you database is locked somehow. -dain Saroj Kumar wrote: > Hi! > Ive been struggling with this for quite some time.I have some Jsps > deployed in > Tomcat 4.04 which then call EJB components hosted on Jboss 3.0.1. > I have session and entity beans(CMP2.0) deployed on Jboss. > > My session beans calls a java class which in turn tries to do a > home.findByPrimaryKey on > an entity and hangs.When I do the same using a standalone java client > it works..but not > through the Jsps hosted on Tomcat. > > Also setEntityContext is called and ejbActivate and EJBLoad are not > called. > It just hangs and then times out after some time with the following > stack trace > > > > 22:29:03,839 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//13, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,104 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//17, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,224 ERROR [BeanLock] Thread[Thread-20,5,RMI Runtime]Saw rolled > back tx=TransactionImpl:XidImpl [FormatId=257, Global > Id=mdpcad110773//17, BranchQual=] waiting for txLock > 22:29:07,264 ERROR [LogInterceptor] TransactionRolledbackLocalException, > causedBy: > java.lang.RuntimeException: Transaction marked for rollback, possibly a > timeout > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedPess > imisticEJBLock.java:325) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(QueuedPes > simisticEJBLock.java:189) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.schedule(QueuedPessi > misticEJBLock.java:140) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor > .java:103) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInt > erceptor.java:69) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > ptor.java:107) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > CMT.java:178) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) > at > org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav > a:130) > at > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) > at > org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) > at > org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.invoke(BaseLocalCo > ntainerInvoker.java:301) > at > org.jboss.ejb.plugins.local.EntityProxy.invoke(EntityProxy.java:38) > at $Proxy232.getCreatedBy(Unknown Source) > at > com.cadmus.rpm.domain.session.ModelFactory.ModelFactoryGenBean.getArticl > e(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at >
Re: [JBoss-user] home.findByPrimaryKey HANGS!!!!!!!!!!!!!!!!!!!!!!!!!
Have you done a thread dump when it hangs? Where is it waiting. My guess is you database is locked somehow. -dain Saroj Kumar wrote: > Hi! > Ive been struggling with this for quite some time.I have some Jsps > deployed in > Tomcat 4.04 which then call EJB components hosted on Jboss 3.0.1. > I have session and entity beans(CMP2.0) deployed on Jboss. > > My session beans calls a java class which in turn tries to do a > home.findByPrimaryKey on > an entity and hangs.When I do the same using a standalone java client > it works..but not > through the Jsps hosted on Tomcat. > > Also setEntityContext is called and ejbActivate and EJBLoad are not > called. > It just hangs and then times out after some time with the following > stack trace > > > > 22:29:03,839 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//13, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,104 WARN [TxCapsule] Transaction XidImpl [FormatId=257, > GlobalId=mdpcad110773//17, BranchQual=] timed out. status=S > TATUS_ACTIVE > 22:29:07,224 ERROR [BeanLock] Thread[Thread-20,5,RMI Runtime]Saw rolled > back tx=TransactionImpl:XidImpl [FormatId=257, Global > Id=mdpcad110773//17, BranchQual=] waiting for txLock > 22:29:07,264 ERROR [LogInterceptor] TransactionRolledbackLocalException, > causedBy: > java.lang.RuntimeException: Transaction marked for rollback, possibly a > timeout > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedPess > imisticEJBLock.java:325) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(QueuedPes > simisticEJBLock.java:189) > at > org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.schedule(QueuedPessi > misticEJBLock.java:140) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor > .java:103) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInt > erceptor.java:69) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > ptor.java:107) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > CMT.java:178) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) > at > org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav > a:130) > at > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) > at > org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) > at > org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.invoke(BaseLocalCo > ntainerInvoker.java:301) > at > org.jboss.ejb.plugins.local.EntityProxy.invoke(EntityProxy.java:38) > at $Proxy232.getCreatedBy(Unknown Source) > at > com.cadmus.rpm.domain.session.ModelFactory.ModelFactoryGenBean.getArticl > e(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Stat > elessSessionContainer.java:660) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke( > CachedConnectionInterceptor.java:186) > at > org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Statele > ssSessionInstanceInterceptor.java:77) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > ptor.java:107) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > CMT.java:178) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) > at > org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav > a:130) > at > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) > at > org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer > .java:313) > at org.jboss.ejb.Container.invoke(Container.java:711) > at > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) > at > org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:1 > 02) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav > a:73) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) > at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionI > nterceptor.java:111) > at > org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) > at $Proxy191.getArticle(Unknown Source) > at > com.cadmus.rpm.domain.workflow.actions