[JBoss JIRA] Created: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
5:51 p.m.
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
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Jonathan Halliday
Priority: Blocker
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
12:50 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]
Mark Little updated JBTM-279:
-----------------------------
Fix Version/s: 4.2.3.SP6
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
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Jonathan Halliday
Priority: Blocker
Fix For: 4.2.3.SP6
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
1:52 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]
Jonathan Halliday updated JBTM-279:
-----------------------------------
Fix Version/s: 4.2.3.SP7
(was: 4.2.3.SP6)
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
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Jonathan Halliday
Priority: Blocker
Fix For: 4.2.3.SP7
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
7:56 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=comments#action_12396648 ]
Adrian Brock commented on JBTM-279:
-----------------------------------
It's all in the JBossAS server project except the JMSProviderXAResourceRecovery.java
class
on the linked task which depends upon the new TM classes and obviously needs to go in its
configuration.
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
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Jonathan Halliday
Priority: Blocker
Fix For: 4.2.3.SP7
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
4:07 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]
Jonathan Halliday updated JBTM-279:
-----------------------------------
Component/s: Recovery
Fix Version/s: 4.2.3.SP8
(was: 4.2.3.SP7)
Assignee: Michael Musgrove (was: Jonathan Halliday)
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
4:43 p.m.
New subject: [JBoss JIRA] Work started: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]
Work on JBTM-279 started by Michael Musgrove.
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
11:59 a.m.
New subject: [JBoss JIRA] Resolved: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ 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
12:01 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]
Michael Musgrove closed JBTM-279.
---------------------------------
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
Attachments: xatest.tar.bz2
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
12:01 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.
[ http://jira.jboss.com/jira/browse/JBTM-279?page=all ]
Michael Musgrove updated JBTM-279:
----------------------------------
Attachment: xatest.tar.bz2
The attachment contains the files I used to test recovery including the various conf files
required to enable the JBossMQ XA recovery feature.
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
Attachments: xatest.tar.bz2
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
6115
days inactive
6362
days old
jbossts-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Adrian Brock (JIRA) -
Jonathan Halliday (JIRA)
-
Mark Little (JIRA)
-
Michael Musgrove (JIRA)