qpid Java client sets timestamp and expiration too far to future
Issue
Sending default JMS message via qpid Java client sets AMQP header properties "timestamp" and also "expiration" too far to future, e.g. to year 45572 instead of 2013.
Setting JMS expiration manually works fine, just the default value is wrong. Timestamp value is everytime wrong.
Environment
- MRG Messaging (any version)
- qpid-java client
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.