[ 
https://issues.apache.org/jira/browse/AMQNET-625?focusedWorklogId=344620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-344620
 ]

ASF GitHub Bot logged work on AMQNET-625:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Nov/19 22:25
            Start Date: 15/Nov/19 22:25
    Worklog Time Spent: 10m 
      Work Description: Havret commented on pull request #48: AMQNET-625: 
Content Property of IBytesMessage should be idempotent
URL: https://github.com/apache/activemq-nms-amqp/pull/48
 
 
   Content Property should not generate side effects. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 344620)
    Remaining Estimate: 0h
            Time Spent: 10m

> byte[] Content property of IBytesMessage is accessible only once
> ----------------------------------------------------------------
>
>                 Key: AMQNET-625
>                 URL: https://issues.apache.org/jira/browse/AMQNET-625
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: AMQP
>            Reporter: Kamil Nowak
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> byte[] Content property of IBytesMessage is accessible only once. Further 
> readings yield byte array with all zeroes assigned.
> *Steps to reproduce:*
> Put a breakpoint in a method which handles the upcoming messaging in the 
> consumer. This results in a reading operation of the byte[] Content of a 
> message of type IBytesMessage. Therefore, further reading operations yield 
> the array with all elements having the '0' assigned.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to