se the timedout message and send the next valid one?
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/expireMessagesPeriod-for-activemq-broker-tp4685839p4685868.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
one?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/expireMessagesPeriod-for-activemq-broker-tp4685839p4685868.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
sage within
> 10
> seconds, I am expecting it to expire and be deleted from the broker. This
> functionality does not seem to be working at all, even reducing the time to
> 1 has no effect. When the receiver program reconnects, it receives all the
> messages that should have expired.
>
> Is there something I am missing in the xml to enable this feature, or
> something I could be doing in my sending client to cause this? I am using
> ActiveMQ 5.9, both Java and C++ APIs. But in this scenario I am sending
> with
> Java and receiving with C++.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/expireMessagesPeriod-for-activemq-broker-tp4685839.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
io I am sending with
Java and receiving with C++.
Thanks
--
View this message in context:
http://activemq.2283324.n4.nabble.com/expireMessagesPeriod-for-activemq-broker-tp4685839.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
