[jbossts-issues] [JBoss JIRA] Resolved: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.

Michael Musgrove (JIRA) jira-events at lists.jboss.org
Fri May 2 05:59:18 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]

Michael Musgrove resolved JBTM-279.

    Resolution: Done

I have added the new JMS recovery provider to the ats integration module (the attached zipped tar file contains the tests I used to validate the fix). To enable the feature add the following property to the jta section of the jbossjta-properties.xml file:

<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="com.arjuna.ats.internal.jbossatx.jta.JMSProviderXAResourceRecovery;java:/DefaultJMSProvider"/>

The recovery code requires a minor fix to the JBossMQ implementation (I've raised JIRA JBAS-5502 to track this).

The attachment contains the config files I used to enable recovery. If you use a JBossMQ PersistenceManager with an Hsql Db then make you disable the  write_delay property to ensure that data is immediately flushed out to  disk. I used a MySQL Db (the relevant SQL is in the file mysql-jdbc2-service.xml (if you use this make sure you remove the default config ie hsqldb-jdbc2-service.xml).

The recovery code does not work with non-durable topic subscriptions (I will raise a JIRA against JBoss Messaging to get it tested on the latest JMS implementation).

> Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
> ------------------------------------------------------------------------------------
>                 Key: JBTM-279
>                 URL: http://jira.jboss.com/jira/browse/JBTM-279
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JTA Implementation, Recovery
>    Affects Versions: 4.2.3.SP5
>            Reporter: Mark Little
>         Assigned To: Michael Musgrove
>            Priority: Blocker
>             Fix For: 4.2.3.SP8
> Adrian did some work on providing a ResourceRecovery implementation and RecoveryModule for JBossMQ (for Glencore). I had assumed that support would make sure it was shipped in subsequent releases of AS (since recovery is pretty important), but that doesn't seem to be the case. If they are not going to do it, then we need to because MQ is effectively frozen (at least that's what Adrian thought).

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


More information about the jbossts-issues mailing list