Just ran another test with the following configuration (transport
connectors). The queue stats for
this test are as follows:
ConsumerCount > 1
DequeueCount > 15117
DispatchCount > 15118
EnqueueCount > 15118
QueueSize > 1
-
Hello active mq users ,
I am having a issue with derby database log , it
has grown to 5 GB in 15 days. Iam using an embedded broker .
What is this log used for ? This log is named derby.log; Our
application uses Topic Publishers are durable subscribers.
The active mq ve
I have:
- Jdbc Master Slave brokers setup in a weblogic cluster.
- Each instance has set of receivers/consumer consuming message from queues
with exclusive consumer
behavior so at a time any one of the cluster instance will be receiving
and processing all the messages.
- the receivers use co
Hello,
I am currently load testing activemq using 1 queue & a variant of the
test.php(stomp) client. I have
probably run up 30 iterations of the test, changing various values in the
xml configuration file, each
time, the thread > ActiveMQ Transport: tcp:///127.0.0.1: dies within a
DispatchCou
You need to add a transport connector to the broker for stomp
Different protocols don't exist on the same port in the broker, each is
configured to its own port in the xml file as seen above.
Then connect using the correct uri via the c++ client
tcp://172.18.117.126:61613?wireFormat=stomp&tr
Hi folks,
i get the above error message and i am absolutely clueless about what to do.
I googled a lot, many hits deal with the same error message but with a quite
different situation (in most cases the error occurs when the broker shuts
down)
The situation:
I got activemq running with one sin
For what it's worth, it would appear that MantaRay is dead. At least, the
website (www.mantamq.org) seems to be gone, and I can't get any replies from
anyone associated with the project. Trying finding the source or a download
of it...
Hi
Could anyone please tell me if they they have compar
Have A create a temporary queue. A sends B the "are you there?" message, with
the "JMSReplyTo" message property set to the temporary queue. After sending
the message on the main queue, A turns around and issues a receive on the
temporary queue, w/the appropriate timeout, to await the reply from B