You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/13 16:26:25 UTC

[jira] [Commented] (AMQ-6244) ActiveMQBytesMessage fails to set 'compressed=false' following restoration of compressed message content

    [ https://issues.apache.org/jira/browse/AMQ-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239329#comment-15239329 ] 

ASF GitHub Bot commented on AMQ-6244:
-------------------------------------

GitHub user bdjdev opened a pull request:

    https://github.com/apache/activemq/pull/177

    https://issues.apache.org/jira/browse/AMQ-6244

    Fix and test for https://issues.apache.org/jira/browse/AMQ-6244

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bdjdev/activemq AMQ-6244

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/177.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #177
    
----
commit 7a61718e0255728b7a822b25fcf75a030be14359
Author: Brian D. Johnson <br...@thejohnsonfamily.name>
Date:   2016-04-11T20:18:26Z

    https://issues.apache.org/jira/browse/AMQ-6244 - reset ActiveMQBytesMessage 'compressed' flag after restoring compressed content

----


> ActiveMQBytesMessage fails to set 'compressed=false' following restoration of compressed message content
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6244
>                 URL: https://issues.apache.org/jira/browse/AMQ-6244
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.13.2
>            Reporter: Brian D. Johnson
>              Labels: EasyFix
>
> {{ActiveMQBytesMessage}} does not reset its {{compressed}} flag to {{false}} following the restoration of compressed message content in {{restoreOldContent()}}.  This becomes a problem if an {{ActiveMQBytesMessage}} is reused by a client on an uncompressed connection after originally being published on a compressed connection.
> Steps to reproduce:
> # An {{ActiveMQBytesMessage}} is published by a producer on a connection with compression *_enabled_*
> Message State: compressed=true; content=compressed
> # The message is consumed by a client and republished on a connection with compression *_disabled_*
> Message State: compressed=true; content=uncompressed
> # The message is consumed by a client and its contents are read.  The ActiveMQ client library tries to decompress the message content, but fails because the content is not compressed.  This causes the consumer to throw either a {{DataFormatException}} or {{NegativeArraySizeException}}.
> This JIRA is similar in nature to AMQ-5381.
> I'll submit a pull request with a test to reproduce and a patch shortly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)