[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1608) MessagingXAResourceRecovery doesn't reconnect remote Messaging instance after remote instance restart

[Takayoshi Kimura (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464595#action_12464595 ] 

Takayoshi Kimura commented on JBMESSAGING-1608:
-----------------------------------------------

Yes  as I mentioned in the comment, I've tested this with EAP 4.3.0.GA_CP04 which includes Messaging 1.4.0.SP3_CP07, latest CP release. Getting same result.

> MessagingXAResourceRecovery doesn't reconnect remote Messaging instance after remote instance restart
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1608
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1608
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.SP3_CP03
>            Reporter: Takayoshi Kimura
>            Assignee: Howard Gao
>         Attachments: JBMESSAGING-1608.zip
>
>
> There are 2 JBoss instances, a JMS client and a server. The client instance defines a RemoteJMSProvider and uses JMS XA resource adapter to connect to the server.
> MessagingXAResourceRecovery is configured on the client instance and it works fine as long as the server instance keeps running. Once the server instance restarted, the MessagingXAResourceRecovery doesn't get working anymore and repeats the following WARN in every recovery:
> > 2009-04-27 15:45:42,479 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException, XAException.XAER_RMFAIL
> Looking at the Messaging code, the MessagingXAResourceWrapper only recreate connection when XA_RETRY is returned. When the remote instance restarts it gets XAER_RMFAIL and reuses dead connection every time.
> If there is no specific reason on this behavior we might want to recreate connection with any XAException.
> How to reproduce:
> * Define RemoteJMSProvider in deploy/remote-jms-ds.xml on the client instance
> * Configure MessagingXAResourceRecovery in conf/jbossjta-properties.xml on the client instance
> * (No config is needed on the server instance)
> * Boot the client and server instances
> * Check the recovery works on the client
> * Stop the server
> * Check the recovery WARNs on the client
> * Start the server
> * You'll see the recovery is not recovered
> I've attached a zip file which contains configurations and logs. Tested with EAP 4.3.0.GA_CP02 (and confirmed it's still reproducible with CP04).
> - deploy/remote-jms-ds.xml
> - conf/jbossjta-properties.xml
> - log/server.log
> - log/server.log.debug
> - debug.patch (for generate server.log.debug. It seems the MessagingXAResourceWrapper/ResourceManager swallow the root cause exception)
> Note that the remote-jms-ds.xml doesn't have resource adpter definition because it's not needed for testing recovery.

-- 
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