As an alternative to commit+rollback, you could instead use
CLIENT_ACKNOWLEDGE mode, which would let you govern the point
acknowledgements are sent by using the message/context.acknowlege()
method (which operates on all unacknowledged messages on the
session/context) and session/context recover() m
The solace message broker currently does not support transactions (local or
XA) over the amqp protocol see solace amqp protocol conformance docs,
https://docs.solace.com/Open-APIs-Protocols/AMQP/AMQP-Protocol-Conformance.htm#Sec4-1.
It's been a while since I used the Solace AMQP 1.0 implementation,
The client itself supports local transactions, use the
SESSION_TRANSACTED acknowledgement mode when creating the Session or
JMSContext, and then you would need to commit/rollback the
session/context after handling messages successfully or not. The
client does not support distributed transactions en
On 05/02/19 14:43, jerrin94 wrote:
Hii,
I am using Apache Qpid JMS 2.0 Solace AMQP 1.0 implementation
(qpid-jms-client-0.37.0) to connect to Solace message broker.
Does this implementation provide transaction support.
When receiving message from the queue, before registering in db the message
Hii,
I am using Apache Qpid JMS 2.0 Solace AMQP 1.0 implementation
(qpid-jms-client-0.37.0) to connect to Solace message broker.
Does this implementation provide transaction support.
When receiving message from the queue, before registering in db the message
should not get deleted from the queu
