[
https://issues.jboss.org/browse/JBMESSAGING-1884?page=com.atlassian.jira....
]
Justin Bertram updated JBMESSAGING-1884:
----------------------------------------
Description:
JBMESSAGING-1786 changed the format of ClientTransaction to include a recovery flag,
unfortunately this breaks the wire protocol with older clients.
The versions containing the problematic changes from JBMESSAGING-1786 are
- 1.4.0 SP3 CP11, CP12, CP13
- 1.4.6 GA SP1
- 1.4.7 GA
- 1.4.8 GA
- 1.4.8 SP1
Attached to this issue is a diff, made against the current Branch_1_4, which addresses the
issue.
Older clients should still be able to talk to the newer server but will not be able to
take advantage of the fix for JBMESSAGING-1786.
was:
JBMESSAGING-1786 changed the format of ClientTransaction to include a recovery flag,
unfortunately this breaks the wire protocol with older clients.
The versions containing this problem are
- 1.4.0 SP3 CP11, CP12, CP13
- 1.4.6 GA SP1
- 1.4.7 GA
- 1.4.8 GA
- 1.4.8 SP1
Attached to this issue is a diff, made against the current Branch_1_4, which addresses the
issue.
Older clients should still be able to talk to the newer server but will not be able to
take advantage of the fix for JBMESSAGING-1786.
ClientTransaction alters wire format
------------------------------------
Key: JBMESSAGING-1884
URL:
https://issues.jboss.org/browse/JBMESSAGING-1884
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.8.SP1
Reporter: Kevin Conner
Assignee: Justin Bertram
Attachments: transaction.diffs
JBMESSAGING-1786 changed the format of ClientTransaction to include a recovery flag,
unfortunately this breaks the wire protocol with older clients.
The versions containing the problematic changes from JBMESSAGING-1786 are
- 1.4.0 SP3 CP11, CP12, CP13
- 1.4.6 GA SP1
- 1.4.7 GA
- 1.4.8 GA
- 1.4.8 SP1
Attached to this issue is a diff, made against the current Branch_1_4, which addresses
the issue.
Older clients should still be able to talk to the newer server but will not be able to
take advantage of the fix for JBMESSAGING-1786.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira