[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1884) ClientTransaction alters wire format

Justin Bertram (JIRA) jira-events at lists.jboss.org
Wed Jul 6 16:54:24 EDT 2011


     [ https://issues.jboss.org/browse/JBMESSAGING-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated JBMESSAGING-1884:
----------------------------------------

    Fix Version/s: 1.4.0.SP3.CP14
                   1.4.8.SP2


> 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.0.SP3.CP11, 1.4.0.SP3.CP12, 1.4.0.SP3.CP13, 1.4.6.GA.SP1, 1.4.7.GA, 1.4.8.GA, 1.4.8.SP1
>            Reporter: Kevin Conner
>            Assignee: Justin Bertram
>             Fix For: 1.4.0.SP3.CP14, 1.4.8.SP2
>
>         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
> Clients communicating with one of these versions of JBoss Messaging using libraries from any version aside from these will have problems performing transactions (i.e. network communication will hang because each side will be expecting different data).
> 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

        


More information about the jboss-jira mailing list