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() method.

Robbie

On Tue, 5 Feb 2019 at 19:44, Robbie Gemmell <[email protected]> wrote:
>
> 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 enlisting multiple
> resources. I'll need to refer you to Solace about whether their
> offering supports transactions or not.
>
> Robbie
>
> On Tue, 5 Feb 2019 at 19:35, jerrin94 <[email protected]> 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
> > should not get deleted from the queue.
> >
> > Is there any provision to configure a transactor commit or rollback boundary
> > to message reading from the queue and registering in db for the above
> > implementation (Qpid JMS 2.0 Solace AMQP 1.0 implementation
> > (qpid-jms-client-0.37.0)).
> >
> >
> >
> > --
> > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to