Resource Manager Unavailable

[Rachana Reddy]

Hi,

When the transaction takes more than 2 mins .I get the following error message. I have Oracle thin Driver.
with 2 emulate turn on ( which is same as XA Driver).

Please Help

start() failed on resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl':
XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource
'weblogic.jdbc.wrapper.JTSXAResourceImpl' is unavailable
at
weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:1019)
at
weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:572)
at
weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1068)
at
weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1001)
at
weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:203)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:207)
at weblogic.jdbc.jts.Driver.connect(Driver.java:154)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:298)
at
com.ml.mlim.lps.util.LPSConnection.makeConnection(LPSConnection.java:103)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManagerBean.makeConnection(PCCListManagerBean.java:1051)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManagerBean.getPartnerList(PCCListManagerBean.java:2633)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManager_7ylrjm_EOImpl.getPartnerList(PCCListManager_7ylrjm_EOImpl.java:2638)
at
com.ml.mlim.lps.session.listmanager.pcc.PCCListManager_7ylrjm_EOImpl_WLSkel.invoke(Unknown Source)
at

[Rachana Reddy]

Hi,
Update to the earlier question, Workaround was posted in one of the saying:
I cannot go with first solution, more than 2 mins is to the application and the second setting of
<Domain>
...
<JTA
MaxXACallMillis="240000"
/>
...
</Domain>

is a global parameter, which will effect other application which are hosted on the server.

Please help.
Thanks in advance
WORKAROUND:
To avoid this issue, find a process that holds a transaction so long, then optimize the process not to hold the transaction more than 2 minutes. Because the application should not have such a long living transaction in general. If you think this long living transaction is applicable for your application, you have an option to change the maximum allowed duration for XA calls to resources. The option is MaxXACallMillis in JTA element of the config.xml file. You can configure the duration by adding the option to the config.xml file directly.
For example:
<Domain>
...
<JTA
MaxXACallMillis="240000"
/>
...