javax.ejb.EJBException:
Unable to complete container-managed transaction.
Anyone of you faced this kind of exceptions or errors in your projects? We have faced some typical and strange issue in the project that I am currently working on. Noone of us aware of this issue earlier. We struggled a lot to found root cause for this exception.We didn't find any application specific errors in logs as well.
We restarted the Glassfish server - no use. Issue was not solved.
We restarted Oracle Database server - Issue was disappeared.
Root cause:
One of our coleagues said that she had see this kind of exception sometime back and she struggled a lot to fix this issue the whole day. But she didn't find solution and went home. When she came next day and run the application the issue was disappeared and later she didn't care about the issue since the uergent project release.
We recollected the recent changes that we have made in application and database. We have introduced some new classes required for new products and data model changes to add new tables and new columns to the existing tables for the new products in the application that we going to support for. The lady who faced this issue earlier recollected that there was a data model change when she faced the same issue earlier.
By analyzing the above incidents we concluded that whenever we make data model changes this issue is appearing and when we restart the Oracle database server the issue is disappearing. Actually any database server should not behave like that. We have notified this weired behavior or bug of Oracle server to the vendor.
So friends if you face this kind of exception with Orcale database, just restart the database server, your problem will get resolved.
at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:5147)
at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4901)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
21T16:28:33.064+0200|WARNING|glassfish3.1.2|javax.enterprise.system.core.transaction.com.sun.jts.jtsxa|_ThreadID=111;_ThreadName=Thread-2;|JTS5067:
Unexpected error occurred in commit
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1135)
at oracle.jdbc.xa.client.OracleXAResource.commit(OracleXAResource.java:565)
at com.sun.gjc.spi.XAResourceImpl.commit(XAResourceImpl.java:84)
at com.sun.jts.jtsxa.OTSResourceImpl.commit_one_phase(OTSResourceImpl.java:174)
at
com.sun.jts.CosTransactions.RegisteredResources.commitOnePhase(RegisteredResources.java:1565)
javax.enterprise.system.core.transaction.com.sun.jts.CosTransactions|_ThreadID=111;_ThreadName=Thread-2;|JTS5031:
Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0
completed: Maybe] on Resource [commit one phase] operation.|#]
javax.enterprise.resource.resourceadapter.com.sun.enterprise.resource.allocator|_ThreadID=111;_ThreadName=Thread-2;|RAR7093
: Error while cleaning up ManagedConnection
javax.resource.ResourceException:
Closed Connection: OraclePooledConnection.getConnection() - SQLException
Ocurred:Invalid or Stale Connection found in the Connection Cache
at
com.sun.gjc.spi.ManagedConnection.getActualConnection(ManagedConnection.java:725)
javax.transaction.xa.XAException:
javax.resource.spi.LocalTransactionException: No more data to read from socket
at
com.sun.enterprise.resource.ConnectorXAResource.handleResourceException(ConnectorXAResource.java:115)
at com.sun.enterprise.resource.ConnectorXAResource.commit(ConnectorXAResource.java:126)
at
com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:501)
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
We restarted the Glassfish server - no use. Issue was not solved.
We restarted Oracle Database server - Issue was disappeared.
Root cause:
One of our coleagues said that she had see this kind of exception sometime back and she struggled a lot to fix this issue the whole day. But she didn't find solution and went home. When she came next day and run the application the issue was disappeared and later she didn't care about the issue since the uergent project release.
We recollected the recent changes that we have made in application and database. We have introduced some new classes required for new products and data model changes to add new tables and new columns to the existing tables for the new products in the application that we going to support for. The lady who faced this issue earlier recollected that there was a data model change when she faced the same issue earlier.
By analyzing the above incidents we concluded that whenever we make data model changes this issue is appearing and when we restart the Oracle database server the issue is disappearing. Actually any database server should not behave like that. We have notified this weired behavior or bug of Oracle server to the vendor.
So friends if you face this kind of exception with Orcale database, just restart the database server, your problem will get resolved.
Comments
Post a Comment