Error:
Caused by: javax.ejb.EJBException: Unexpected exception in com.retek.rib.app.getnext.impl.GetNextPublisherEjb.getNextAndPublishMessages:
com.retek.rib.binding.exception.PublishException: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'rib-rms-managed-datasource_RIBDomain': XAER_RMFAIL : Resource manager is unavailable
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:790)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1247)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1180)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:285)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:561)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:488)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1673)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1577)
at weblogic.jdbc.jta.DataSource.getConnectionInternal(DataSource.java:478)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:462)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:512)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:498)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:491)
at com.retek.rib.app.getnext.impl.GetNextPublisherEjb.getConnection(GetNextPublisherEjb.java:161)
Causes:
The issue is due to datasources connection are crashed when tx timeout or deadlock is occurred.
Solution:
After applying this patch the above issue is getting resolve.
Caused by: javax.ejb.EJBException: Unexpected exception in com.retek.rib.app.getnext.impl.GetNextPublisherEjb.getNextAndPublishMessages:
com.retek.rib.binding.exception.PublishException: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'rib-rms-managed-datasource_RIBDomain': XAER_RMFAIL : Resource manager is unavailable
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:790)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1247)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1180)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:285)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:561)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:488)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1673)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1577)
at weblogic.jdbc.jta.DataSource.getConnectionInternal(DataSource.java:478)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:462)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:512)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:498)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:491)
at com.retek.rib.app.getnext.impl.GetNextPublisherEjb.getConnection(GetNextPublisherEjb.java:161)
Causes:
The issue is due to datasources connection are crashed when tx timeout or deadlock is occurred.
Solution:
After applying this patch the above issue is getting resolve.
superb, this would be very helpful
ReplyDeleteVery good solution
ReplyDeleteWonderful information, thanks for the great solution.
ReplyDeleteGermany VPS Server Hosting
Thanks for the details
ReplyDelete