Messages born expired
---------------------
Key: AMQ-2587
URL: https://issues.apache.org/activemq/browse/AMQ-2587
Project: ActiveMQ
Issue Type: Bug
Components: Broker, JMS client
Affects Versions: 5.3.0
Environment: Windows XP, Sun Java 1.6u18
Reporter: Nacho Vargas
Under some circumstances, messages are born already expired. To reproduce it,
you need two computers, a "server" and a "client".
1. Set the current time in the client as appropiate in your time zone, say it
is 11:00am.
2. Set the current time in the server as a few minutes after the real current
time, say 11:10am.
3. Run an ActiveMQ broker in the server.
4. Run an ActiveMQ producer in the client.
5. Send a message from the producer with a short time to live, say 5 seconds.
6. The message is inmediately marked as "expired" and it is not delivered to
consumer(s).
I have been using ActiveMQ 4.1.1 for a couple of years and this has never been
an issue. I have recently moved to ActiveMQ 5.3.0 and I have found this issue.
A messaging system should *NOT* assume that clocks in every computer in the
network are synchronized.
Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
