[jboss-jira] [JBoss JIRA] (JBJCA-737) XAResourceRecoveryImpl does not consider the possibility that wrapXAResource may be null
Stuart Douglas (JIRA)
jira-events at lists.jboss.org
Mon Jan 30 22:39:48 EST 2012
[ https://issues.jboss.org/browse/JBJCA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart Douglas updated JBJCA-737:
---------------------------------
Affects Version/s: 1.0.7.Final
> XAResourceRecoveryImpl does not consider the possibility that wrapXAResource may be null
> ----------------------------------------------------------------------------------------
>
> Key: JBJCA-737
> URL: https://issues.jboss.org/browse/JBJCA-737
> Project: IronJacamar
> Issue Type: Bug
> Affects Versions: 1.0.7.Final
> Reporter: Stuart Douglas
> Assignee: Jesper Pedersen
>
> This results in a potential problem when deploying XML datasources in AS7 without an xa-pool:
> 14:17:30,697 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.NullPointerException
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:187)
> at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:52) [jbossjts-integration-4.16.1.Final.jar:]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:462) [jbossjts-4.16.1.Final.jar:]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:385) [jbossjts-4.16.1.Final.jar:]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:166) [jbossjts-4.16.1.Final.jar:]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-4.16.1.Final.jar:]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-4.16.1.Final.jar:]
> I am just going to work around this in AS7 for now, but I think this should still be fixed in IJ.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list