FYI, the Qpid JMS 0.42.0 release contains a client change that should
help avoid the broker bug. It should sync to Maven Central in the next
hour or two.
On Sun, 5 May 2019 at 16:30, Patrick Vansevenant
wrote:
>
>
> Thank you for the quick response, Tim.
>
> I'm indeed confronted with the same pr
Thank you for the quick response, Tim.
I'm indeed confronted with the same problem as described in
https://issues.apache.org/jira/browse/AMQ-7189.
The JMS transformer is, as you indicated, the perfect workaround.
Patrick
---
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User
On 5/3/19 5:58 AM, Patrick Vansevenant wrote:
I'm not able to send non_persistent messages to an ActiveMQ broker (5.15.3)
with version 0.20.0 or higher of the qpid-jms-client library.
The messages are shown as persistent on the console and they behave also as
persistent.
Sending non_persistent me
I'm not able to send non_persistent messages to an ActiveMQ broker (5.15.3)
with version 0.20.0 or higher of the qpid-jms-client library.
The messages are shown as persistent on the console and they behave also as
persistent.
Sending non_persistent messages with the qpid-jms-client 0.11.1 or lower
