[
https://issues.apache.org/jira/browse/QPID-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179579#comment-13179579
]
Keith Wall commented on QPID-3715:
----------------------------------
Isn't it because an implementation of InputStream#read() is required to return
the byte as an int in the range 0..255 rather than value -127..128? I think
ByteBufferInputStream#read() should be guarding the get() with hasRemaining (in
the way you did in your patch) and returning -1 when the ByteBuffer is
exhausted.
> On receiving an empty ObjectMessage java client hangs forever
> -------------------------------------------------------------
>
> Key: QPID-3715
> URL: https://issues.apache.org/jira/browse/QPID-3715
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.15
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: 0.15
>
> Attachments:
> 0001-QPID-3715-Fix-the-receiving-of-an-empty-ObjectMessag.patch
>
>
> If ObjectMessage message is created and sent without a body than on receiving
> such a message the consumer hangs regardless whether timeout specified or not.
> The following snippet demonstrates the problem
> {code:title=Sending and receiving an empty object message|borderStyle=solid}
> Message message = session.createObjectMessage();
> producer.send(message);
> ObjectMessage receivedMessage = (ObjectMessage) consumer.receive(1000);//
> <--- hanging here
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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:[email protected]
