that should be fine. for the most part the TimeStampPlugin is used when client clocks are out of sync with the broker.
Feel free to patch the TimeStampPlugin so just add a missing expiration as an option and submit a diff. Seems like an sensible enhancement and all contributions are welcome. On 6 November 2013 11:01, Sophia Wright <sophiawrigh...@gmail.com> wrote: > Sorry for the late reply... > > Actually I don't want to use TimeStampPlugin because it also set JMS > Client's timestamp on the message with a broker timestamp according to the > broker's clock. I don't want to disturb the time stamp which is set by the > producers. > > So I thought that I can write my own plugin which only expires messages by > setting expiration time for each message using > "message.setExpiration(expiration);" if expiration time is not provided by > the producer. > > So is this a right way to do this ? Are there any consequences of > this(something related to time stamp) > > Thanks, > Sophia > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-Expiration-thorugh-broker-tp4672873p4673940.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
