[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] [Commented] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115228#comment-15115228 ] Claudio Tagliola commented on AMQ-6142: --- Prior thread on activemq-users: http://activemq.2283324.n4.nabble.com/ActiveMQBytesMessage-decompress-throws-DataFormatException-incorrect-header-check-tp4706292.html > 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)
[jira] [Created] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
Claudio Tagliola created AMQ-6142: - Summary: 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.13.0, 5.11.3, 5.12.1, 5.10.2 Reporter: Claudio Tagliola 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)
[jira] [Commented] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115226#comment-15115226
]
Claudio Tagliola commented on AMQ-6142:
---
Stack trace:
{noformat}
javax.jms.JMSException: java.util.zip.DataFormatException: incorrect header
check
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
at
org.apache.activemq.command.ActiveMQBytesMessage.initializeReading(ActiveMQBytesMessage.java:884)
at
org.apache.activemq.command.ActiveMQBytesMessage.getBodyLength(ActiveMQBytesMessage.java:198)
at
com.imc.activemqtest.MessageListener.onMessage(MessageListener.java:11)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1393)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: java.util.zip.DataFormatException: incorrect
header check
at
org.apache.activemq.command.ActiveMQBytesMessage.decompress(ActiveMQBytesMessage.java:902)
at
org.apache.activemq.command.ActiveMQBytesMessage.initializeReading(ActiveMQBytesMessage.java:876)
... 10 more
Caused by: java.util.zip.DataFormatException: incorrect header check
at java.util.zip.Inflater.inflateBytes(Native Method)
at java.util.zip.Inflater.inflate(Inflater.java:259)
at java.util.zip.Inflater.inflate(Inflater.java:280)
at
org.apache.activemq.command.ActiveMQBytesMessage.decompress(ActiveMQBytesMessage.java:898)
... 11 more
{noformat}
> 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
>
> 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)
[jira] [Comment Edited] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115226#comment-15115226
]
Claudio Tagliola edited comment on AMQ-6142 at 1/25/16 2:02 PM:
Stack trace:
{noformat}
javax.jms.JMSException: java.util.zip.DataFormatException: incorrect header
check
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
at
org.apache.activemq.command.ActiveMQBytesMessage.initializeReading(ActiveMQBytesMessage.java:884)
at
org.apache.activemq.command.ActiveMQBytesMessage.getBodyLength(ActiveMQBytesMessage.java:198)
at
com.foo.bar.activemqtest.MessageListener.onMessage(MessageListener.java:11)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1393)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: java.util.zip.DataFormatException: incorrect
header check
at
org.apache.activemq.command.ActiveMQBytesMessage.decompress(ActiveMQBytesMessage.java:902)
at
org.apache.activemq.command.ActiveMQBytesMessage.initializeReading(ActiveMQBytesMessage.java:876)
... 10 more
Caused by: java.util.zip.DataFormatException: incorrect header check
at java.util.zip.Inflater.inflateBytes(Native Method)
at java.util.zip.Inflater.inflate(Inflater.java:259)
at java.util.zip.Inflater.inflate(Inflater.java:280)
at
org.apache.activemq.command.ActiveMQBytesMessage.decompress(ActiveMQBytesMessage.java:898)
... 11 more
{noformat}
was (Author: tagliola):
Stack trace:
{noformat}
javax.jms.JMSException: java.util.zip.DataFormatException: incorrect header
check
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
at
org.apache.activemq.command.ActiveMQBytesMessage.initializeReading(ActiveMQBytesMessage.java:884)
at
org.apache.activemq.command.ActiveMQBytesMessage.getBodyLength(ActiveMQBytesMessage.java:198)
at
com.imc.activemqtest.MessageListener.onMessage(MessageListener.java:11)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1393)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: java.util.zip.DataFormatException: incorrect
header check
at
org.apache.activemq.command.ActiveMQBytesMessage.decompress(ActiveMQBytesMessage.java:902)
at
org.apache.activemq.command.ActiveMQBytesMessage.initializeReading(ActiveMQBytesMessage.java:876)
... 10 more
Caused by: java.util.zip.DataFormatException: incorrect header check
at java.util.zip.Inflater.inflateBytes(Native Method)
at java.util.zip.Inflater.inflate(Inflater.java:259)
at java.util.zip.Inflater.inflate(Inflater.java:280)
at
org.apache.activemq.command.ActiveMQBytesMessage.decompress(ActiveMQBytesMessage.java:898)
... 11 more
{noformat}
> 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
>
> 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.
[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)
