[jira] [Updated] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-6142: Attachment: amq-6142.diff amq-6142.diff - file attach. Show the problem with message.copy that seems to be the root cause cc [~cshannon] > ActiveMQBytesMessage decompress throws DataFormatException incorrect header > check > - > > Key: AMQ-6142 > URL: https://issues.apache.org/jira/browse/AMQ-6142 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.10.2, 5.12.1, 5.11.3, 5.13.0 >Reporter: Claudio Tagliola >Assignee: Christopher L. Shannon > Fix For: 5.13.1, 5.14.0 > > Attachments: Client.java, MessageListener.java, Server.java, > amq-6142.diff, pom.xml > > > In our environment we use an embedded broker. On one topic where compression > is enabled, the server is also listening in on the messages. From ActiveMQ > 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check > exceptions on the tcp clients due to corruption of the payload. Attached are > a test server and client. At some point, the client will exit due to > mentioned exception. Increase chances by running multiple clients. This > scenario works with 5.8.0 and 5.9.1. > If the server has multiple consumers on the same topic, they will encounter > corruption as well, but this has other side-effects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Tagliola updated AMQ-6142: -- Description: In our environment we use an embedded broker. On one topic where compression is enabled, the server is also listening in on the messages. From ActiveMQ 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check exceptions on the tcp clients due to corruption of the payload. Attached are a test server and client. At some point, the client will exit due to mentioned exception. Increase chances by running multiple clients. If the server has multiple consumers on the same topic, they will encounter corruption as well, but this has other side-effects. was: In our environment we use an embedded broker. On one topic, the server is also listening in on the messages. From ActiveMQ 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check exceptions on the tcp clients due to corruption of the payload. Attached are a test server and client. At some point, the client will exit due to mentioned exception. Increase chances by running multiple clients. If the server has multiple consumers on the same topic, they will encounter corruption as well, but this has other side-effects. > ActiveMQBytesMessage decompress throws DataFormatException incorrect header > check > - > > Key: AMQ-6142 > URL: https://issues.apache.org/jira/browse/AMQ-6142 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.10.2, 5.12.1, 5.11.3, 5.13.0 >Reporter: Claudio Tagliola > Attachments: Client.java, MessageListener.java, Server.java, pom.xml > > > In our environment we use an embedded broker. On one topic where compression > is enabled, the server is also listening in on the messages. From ActiveMQ > 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check > exceptions on the tcp clients due to corruption of the payload. Attached are > a test server and client. At some point, the client will exit due to > mentioned exception. Increase chances by running multiple clients. > If the server has multiple consumers on the same topic, they will encounter > corruption as well, but this has other side-effects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Tagliola updated AMQ-6142: -- Description: In our environment we use an embedded broker. On one topic where compression is enabled, the server is also listening in on the messages. From ActiveMQ 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check exceptions on the tcp clients due to corruption of the payload. Attached are a test server and client. At some point, the client will exit due to mentioned exception. Increase chances by running multiple clients. This scenario works with 5.8.0 and 5.9.1. If the server has multiple consumers on the same topic, they will encounter corruption as well, but this has other side-effects. was: In our environment we use an embedded broker. On one topic where compression is enabled, the server is also listening in on the messages. From ActiveMQ 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check exceptions on the tcp clients due to corruption of the payload. Attached are a test server and client. At some point, the client will exit due to mentioned exception. Increase chances by running multiple clients. If the server has multiple consumers on the same topic, they will encounter corruption as well, but this has other side-effects. > ActiveMQBytesMessage decompress throws DataFormatException incorrect header > check > - > > Key: AMQ-6142 > URL: https://issues.apache.org/jira/browse/AMQ-6142 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.10.2, 5.12.1, 5.11.3, 5.13.0 >Reporter: Claudio Tagliola > Attachments: Client.java, MessageListener.java, Server.java, pom.xml > > > In our environment we use an embedded broker. On one topic where compression > is enabled, the server is also listening in on the messages. From ActiveMQ > 5.10.0 up to 5.13.0, we encounter DataFormatException: incorrect header check > exceptions on the tcp clients due to corruption of the payload. Attached are > a test server and client. At some point, the client will exit due to > mentioned exception. Increase chances by running multiple clients. This > scenario works with 5.8.0 and 5.9.1. > If the server has multiple consumers on the same topic, they will encounter > corruption as well, but this has other side-effects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Tagliola updated AMQ-6142: -- Attachment: pom.xml Server.java MessageListener.java Client.java > ActiveMQBytesMessage decompress throws DataFormatException incorrect header > check > - > > Key: AMQ-6142 > URL: https://issues.apache.org/jira/browse/AMQ-6142 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.10.2, 5.12.1, 5.11.3, 5.13.0 >Reporter: Claudio Tagliola > Attachments: Client.java, MessageListener.java, Server.java, pom.xml > > > In our environment we use an embedded broker. On one topic, the server is > also listening in on the messages. From ActiveMQ 5.10.0 up to 5.13.0, we > encounter DataFormatException: incorrect header check exceptions on the tcp > clients due to corruption of the payload. Attached are a test server and > client. At some point, the client will exit due to mentioned exception. > Increase chances by running multiple clients. > If the server has multiple consumers on the same topic, they will encounter > corruption as well, but this has other side-effects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
