Hi,
is there a way to ensure that ActiveMQ does not use Distributed
Transactions? We tried starting the session with
AcknowledgementMode.AutoAcknowledge, but it appears ActiveMq still initiates
a distributed transaction.
We are using ActiveMq 5.11.1 with Apache.NMS.ActiveMQ 1.6.0.3072.
--
Vie
Hi Christopher, thanks for quick responds.
I have some further information regarding my setup.
Regarding the client ID and subscription ID, I am using the same value (i.e.
"client-1") as the clientID and durableSubscriptionName.
My applicationContext.xml file has set this as follows:
Have you made any progress on this? I'm getting ready to devote a bit of time
to this and wanted to make sure I wasn't going to implement something you
already had working.
Justin
- Original Message -
From: "slew77"
To: users@activemq.apache.org
Sent: Friday, October 16, 2015 2:34:02
Final update:
I finalized my proof-of-concept implementation of a messaging system using
AMQ that is:
* fault tolerant
* guaranteed delivery
* asynchronous (non-blocking application code)
* dynamically routed
* JNDI (JNP) discovered
Tim Bain wrote
> Yeah, that was what I found. But the fact th
Hi,
I am using REST API
http://localhost:8081/api/message/MyQueue5?type=queue&body=name=jack;age=23
to publish my message.
Now I want only those messages that have name=Smantha.
http://localhost:8081/api/message/MyQueue5?type=queueheader with
selector: name=Smantha doesnot work.
How should