[jira] [Updated] (ARTEMIS-1546) Messages sent with snapshot won't be read from 1.x consumers

2017-12-21 Thread clebert suconic (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

clebert suconic updated ARTEMIS-1546:
-
Affects Version/s: 2.0.0
   2.1.0
   2.2.0
   2.3.0
   2.4.0

> Messages sent with snapshot won't be read from 1.x consumers
> 
>
> Key: ARTEMIS-1546
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1546
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> Sending JMS message with core master, receiving with 1.4 will cause issues.
> Any other combination is fine!
> The issue is that 1.x had an extra integer at the end of the body with the 
> size of the body.
> Basically there is on at the beginning  and one at the end of the body
> {size} ... bytes... {size + Initial Head}
> that integer was lost during the AMQP / Core refactoring... 
> The fix here is to recast the message with the integer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1546) Messages sent with snapshot won't be read from 1.x consumers

2017-12-14 Thread clebert suconic (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

clebert suconic updated ARTEMIS-1546:
-
Description: 
Sending JMS message with core master, receiving with 1.4 will cause issues.

Any other combination is fine!


The issue is that 1.x had an extra integer at the end of the body with the size 
of the body.

Basically there is on at the beginning  and one at the end of the body

{size} ... bytes... {size + Initial Head}


that integer was lost during the AMQP / Core refactoring... 

The fix here is to recast the message with the integer.

  was:
Sending JMS message with core master, receiving with 1.4 will cause issues.

Any other combination is fine!


> Messages sent with snapshot won't be read from 1.x consumers
> 
>
> Key: ARTEMIS-1546
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1546
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> Sending JMS message with core master, receiving with 1.4 will cause issues.
> Any other combination is fine!
> The issue is that 1.x had an extra integer at the end of the body with the 
> size of the body.
> Basically there is on at the beginning  and one at the end of the body
> {size} ... bytes... {size + Initial Head}
> that integer was lost during the AMQP / Core refactoring... 
> The fix here is to recast the message with the integer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARTEMIS-1546) Messages sent with snapshot won't be read from 1.x consumers

2017-12-14 Thread clebert suconic (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

clebert suconic updated ARTEMIS-1546:
-
Summary: Messages sent with snapshot won't be read from 1.x consumers  
(was: Compatibility issues between Artemis 1.4 and 2.0)

> Messages sent with snapshot won't be read from 1.x consumers
> 
>
> Key: ARTEMIS-1546
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1546
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: clebert suconic
> Fix For: 2.5.0
>
>
> Sending JMS message with core master, receiving with 1.4 will cause issues.
> Any other combination is fine!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)