[jboss-jira] [JBoss JIRA] Commented: (JBAS-7442) Disable MessagingXAResourceRecovery in clustering tests

[Richard Achmatowicz (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12494373#action_12494373 ] 

Richard Achmatowicz commented on JBAS-7442:
-------------------------------------------

There may be more versions to which this issue applies...

> Disable MessagingXAResourceRecovery in clustering tests
> -------------------------------------------------------
>
>                 Key: JBAS-7442
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7442
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-Branch_4_2
>         Environment: AS configurations which use JBoss Messaging
>            Reporter: Richard Achmatowicz
>            Assignee: Shelly McGowan
>            Priority: Minor
>             Fix For: JBossAS-Branch_4_2
>
>
> When running the clustering tests for AS configurations which use JBoss Messaging, the following exception is seem in the logs:
> 16:21:39,410 ERROR [MessagingXAResourceWrapper] ********************************Failed to connect to server
> javax.naming.NameNotFoundException: DefaultJMSProvider not bound
> 	at org.jnp.server.NamingServer.getBinding(NamingServer.java:581)
> 	at org.jnp.server.NamingServer.getBinding(NamingServer.java:589)
> 	at org.jnp.server.NamingServer.getObject(NamingServer.java:595)
> 	at org.jnp.server.NamingServer.lookup(NamingServer.java:342)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:694)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:654)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:351)
> 	at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.getConnectionFactory(MessagingXAResourceWrapper.java:381)
> 	at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.connect(MessagingXAResourceWrapper.java:338)
> 	at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.getDelegate(MessagingXAResourceWrapper.java:260)
> 	at org.jboss.jms.server.recovery.MessagingXAResourceWrapper.recover(MessagingXAResourceWrapper.java:108)
> 	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecovery(XARecoveryModule.java:774)
> 	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:688)
> 	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:179)
> 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWork(PeriodicRecovery.java:237)
> 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:163)
> This exception is raised by the JBoss Transactions Recovery Manager which periodically checks with JBoss Mesdsaging to see if it requires any recovery services. But JBoss Messaging is not deployed in these configurations, and so the exception is raised.
> MessagingXARResourceecovery is configured by default in 'all' and it would appear that it needs to be disabled when creating the clustering configurations which do not involve messaging. This can be done by removing/commenting out the entry:
> <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.jboss.jms.server.recovery.MessagingXAResourceRecovery;java:/DefaultJMSProvider"/>
> in the file conf/jbossjta-proeprties.xml.
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira