[jboss-jira] [JBoss JIRA] (WFLY-1710) HornetQ fail-back results in XA recovery warnings

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924327#comment-12924327 ] 

RH Bugzilla Integration commented on WFLY-1710:
-----------------------------------------------

Miroslav Novak <mnovak at redhat.com> made a comment on [bug 1031464|https://bugzilla.redhat.com/show_bug.cgi?id=1031464]

Setting flags for EAP 6.2 so it can be tracked for next releases of EAP 6. It seems that it's to late for getting changes to current release.

This is dedicated topology with shared store. Problem is that HQ RA is configured on backup server (with in-vm connector) where actually nothing except HQ backup should be hosted.
We should prepare example configuration for HQ backup for EAP 6 with just necessary and supported services similarly as we have for EAP 5.
                
> HornetQ fail-back results in XA recovery warnings
> -------------------------------------------------
>
>                 Key: WFLY-1710
>                 URL: https://issues.jboss.org/browse/WFLY-1710
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS
>    Affects Versions: 8.0.0.Alpha2
>            Reporter: Justin Bertram
>            Assignee: Jeff Mesnil
>             Fix For: 8.0.0.Alpha4
>
>         Attachments: server.log
>
>
> I pulled the WildFly source as of today and used that for my testing.
> I configured 2 instances of WildFly for HornetQ live-backup functionality.  I started both and after a few minutes I killed the live server.  The backup became active as expected with no problems.  Then after a few more minutes I restarted the live server.  At this point fail-back occurred so that the backup again became passive.  However, I began to see WARN messages like this on the backup every 2 minutes or so:
> {noformat}
> 10:33:45,054 WARN  [org.hornetq.jms.server] (Periodic Recovery) HQ122015: Can not connect to XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=246bb54d-eef6-11e2-a532-65f5ccbce265, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null] on auto-generated resource recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.]
> 	at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:852) [hornetq-core-client-2.3.1.Final.jar:]
> 	at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connect(HornetQXAResourceWrapper.java:378) [hornetq-jms-server-2.3.1.Final.jar:]
> 	at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.getDelegate(HornetQXAResourceWrapper.java:287) [hornetq-jms-server-2.3.1.Final.jar:]
> 	at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.recover(HornetQXAResourceWrapper.java:75) [hornetq-jms-server-2.3.1.Final.jar:]
> 	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:534) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> 	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:168) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira