Skip to content

Conversation

@acogoluegnes
Copy link
Contributor

The property is not supposed to be null in JMS, but it can in AMQP
0.9.1, so JMS messages consumed from AMQP resources can have a null
value. This commit mitigates the issue by returning a timestamp set to 0
in this case, just like the JMS 1.1 specification suggests it when
MessageProducer#setDisableMessageTimestamp(true) is called.

Fixes #126

The property is not supposed to be null in JMS, but it can in AMQP
0.9.1, so JMS messages consumed from AMQP resources can have a null
value. This commit mitigates the issue by returning a timestamp set to 0
in this case, just like the JMS 1.1 specification suggests it when
MessageProducer#setDisableMessageTimestamp(true) is called.

Fixes #126
@michaelklishin michaelklishin merged commit 04340a1 into master Jun 3, 2020
@michaelklishin michaelklishin deleted the rabbitmq-jms-client-126-jms-timestamp-crashes branch June 3, 2020 13:10
@michaelklishin
Copy link
Contributor

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reading JMSTimestamp from an 'amqp' destination results in exception

3 participants