You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2016/11/23 07:55:58 UTC
[jira] [Updated] (QPID-7544) [Java Client][AMQP 0-10] After
resending a previously sent Message, the JMSMessageId is not updated
[ https://issues.apache.org/jira/browse/QPID-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-7544:
------------------------------
Description:
When a Message object is sent by the JMS client the JMSMessageId should be updated with a new message id (unless message id generation has been turned off).
When using the 0-10 protocol, however, the following code will fail
{code}
Message msg = session.createBytesMessage();
producer.send(msg);
String firstId = msg.getJMSMessageID();
producer.send(msg);
assertFalse(firstId.equals(msg.getJMSMessageID());
{code}
In fact the send sending of the message does result in a different message-id being sent over the wire, but this new message id is not exposed in the JMS message.
was:
When a Message object is sent by the JMS client the JMSMessageId should be updated with a new message id (unless message id generation has been turned off).
When using the 0-10 protocol, however, the following code will fail
{code}
Message msg = session.createBytesMessage();
producer.send(msg);
String firstId = msg.getJMSMessageID();
produce.send(msg);
assertFalse(firstId.equals(msg.getJMSMessageID());
{code}
In fact the send sending of the message does result in a different message-id being sent over the wire, but this new message id is not exposed in the JMS message.
> [Java Client][AMQP 0-10] After resending a previously sent Message, the JMSMessageId is not updated
> ---------------------------------------------------------------------------------------------------
>
> Key: QPID-7544
> URL: https://issues.apache.org/jira/browse/QPID-7544
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: qpid-java-6.2
>
>
> When a Message object is sent by the JMS client the JMSMessageId should be updated with a new message id (unless message id generation has been turned off).
> When using the 0-10 protocol, however, the following code will fail
> {code}
> Message msg = session.createBytesMessage();
> producer.send(msg);
> String firstId = msg.getJMSMessageID();
> producer.send(msg);
> assertFalse(firstId.equals(msg.getJMSMessageID());
> {code}
> In fact the send sending of the message does result in a different message-id being sent over the wire, but this new message id is not exposed in the JMS message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org