You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Kennedy (JIRA)" <ji...@apache.org> on 2011/03/01 12:36:39 UTC
[jira] Created: (QPID-3093) BytesMessage is not readable after
createion
BytesMessage is not readable after createion
--------------------------------------------
Key: QPID-3093
URL: https://issues.apache.org/jira/browse/QPID-3093
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.5
Reporter: Andrew Kennedy
Assignee: Andrew Kennedy
Fix For: 0.5
When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-3093) BytesMessage is not readable after
creation
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3093:
---------------------------------
Fix Version/s: (was: 0.5)
> BytesMessage is not readable after creation
> -------------------------------------------
>
> Key: QPID-3093
> URL: https://issues.apache.org/jira/browse/QPID-3093
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Andrew Kennedy
> Assignee: Robbie Gemmell
>
> When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-3093) BytesMessage is not readable after
creation
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3093.
----------------------------------
Resolution: Fixed
Change looks good.
> BytesMessage is not readable after creation
> -------------------------------------------
>
> Key: QPID-3093
> URL: https://issues.apache.org/jira/browse/QPID-3093
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Andrew Kennedy
> Assignee: Robbie Gemmell
>
> When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-3093) BytesMessage is not readable after
createion
Posted by "Andrew Kennedy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kennedy updated QPID-3093:
---------------------------------
Status: Ready To Review (was: In Progress)
> BytesMessage is not readable after createion
> --------------------------------------------
>
> Key: QPID-3093
> URL: https://issues.apache.org/jira/browse/QPID-3093
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Andrew Kennedy
> Assignee: Andrew Kennedy
> Fix For: 0.5
>
>
> When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-3093) BytesMessage is not readable after
creation
Posted by "Andrew Kennedy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kennedy reassigned QPID-3093:
------------------------------------
Assignee: Robbie Gemmell (was: Andrew Kennedy)
Robbie, can you review this please
> BytesMessage is not readable after creation
> -------------------------------------------
>
> Key: QPID-3093
> URL: https://issues.apache.org/jira/browse/QPID-3093
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Andrew Kennedy
> Assignee: Robbie Gemmell
> Fix For: 0.5
>
>
> When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3093) BytesMessage is not readable after
createion
Posted by "Andrew Kennedy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000836#comment-13000836 ]
Andrew Kennedy commented on QPID-3093:
--------------------------------------
The backported fix was committed to the 0.5.x-dev branch as revision 1069472 on 10 February 2011
http://svn.apache.org/viewvc?view=rev&rev=1069472
> BytesMessage is not readable after createion
> --------------------------------------------
>
> Key: QPID-3093
> URL: https://issues.apache.org/jira/browse/QPID-3093
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Andrew Kennedy
> Assignee: Andrew Kennedy
> Fix For: 0.5
>
>
> When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-3093) BytesMessage is not readable after
creation
Posted by "Andrew Kennedy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kennedy updated QPID-3093:
---------------------------------
Summary: BytesMessage is not readable after creation (was: BytesMessage is not readable after createion)
> BytesMessage is not readable after creation
> -------------------------------------------
>
> Key: QPID-3093
> URL: https://issues.apache.org/jira/browse/QPID-3093
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.5
> Reporter: Andrew Kennedy
> Assignee: Andrew Kennedy
> Fix For: 0.5
>
>
> When Mule (however this could apply to any JMS application) creates an AbstractBytesMessage from a byte[] during message processing, it attempts to print the contents of the message. This cauxses a javax.jms.MessageNotReadableException to be thrown with the message"You need to call reset() to make the message readable". The issue has been fixed in the trunk code as QPID-1830 by removing the checkReadable() method from the toBodyString() and porting this fix to the 0.5 branch solves the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org