On activeMQ site there is a mention of library lingo and I am wondering if
anyone has successfully used this library.
http://lingo.codehaus.org/Request+Response+with+JMS
1. By “persistent topics”, do you mean “durable topics”, where you have
subscription(s) tied to a specific topic where messages are being produced, or
do you mean “persistent messages”?
2. A topic with no durable subscriptions isn’t going to consume much disk space
when there aren’t any consume
I filed https://issues.apache.org/jira/browse/AMQ-5342 with the configuration
of the brokers, consumer, producer and full thread dump.
The two brokers are running in their own JVMs connecting to each other over
tcp open wire. Internally the brokers create vm transports to bridge among
their connec
If I use queues that are not temp for request/reply than the challenge is
that somehow I need to maintain the context of the calling thread and then
dispatch the response to the correct thread. It becomes rather difficult to
do that.
Currently, this is what I am doing:
1) Create connection, sessi
Broker is non-persistent. I am sending very small messages and the measure
is only between when I send the message and at the other end when I receive
the message. Consumers and producers are not busy at this point.
I am not re-creating sessions, I am using thread local and I am caching
sessions.
Hi, I am using a cluster of 2 brokers connected via Duplex connector. Brokers
version is 5.10.0, Windows Server 2012 R2, java = SE 1.7.0_51-b13.
Recently I found that both brokers log is full of the same messages:
Full text of warning:
2014-09-02 07:37:41,430 | WARN | Failed to register queue://
Can anyone explain the expected or likely order that a queue receiver will
receive messages when using a composite destination?
I tried sending messages to the following queues in this order: foo, bar,
baz, foo, bar, baz, foo.
I set my receiver to receive from the composite destination "foo,bar,b
On 09/01/2014 03:14 AM, preben wrote:
Good point.
I deleted the whole kahadb+tmp directory and started with a clean running
server, but the results are the same.
I'm still getting the default 6 amq redeliveries and then the broker
redelivery pluging kicks in on 7-10.
2014-09-01 09:01:10,224 |
Hi,
I have a problem that when using transactions all my consumers for a
particular queue are getting blocking waiting for the commit. We are using
the Spring DMLC and are caching at the consumer level. This is ActiveMQ
5.5.1
All threads end up at a WAITING state with the same stack trace as be
