Hi,
Is there a way to limit the queue depth of an ActiveMQ queue in number of
messages?
I know there are ”per destination policies” that can detect queue usage in
terms of memory used. However, the number of messages may indicate other
things, like how many .log files (kahadb) that can be tied
Thanks for the reply. I don't have the stack trace currently with me and I
have not been able to reproduce this issue.
In my broker I log hourly destination stats and for this particular topic I
observed that the messages consumption doesn't stop immediately rather it
happens overtime.
[destName:
Hi ,I am running the activemq on windows . i am trying to implement activemq as
service . Now I have one question By watching the console windows we can see
error , info, warning when starting the activemq server. But with out watch the
console windows Is there any way to detect server is st
Oh, and JDBC has been known to have issues - especially having poor
performance. There is no optimization in its interactions with the DB at
all (e.g. no indices).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Is-JDBC-still-used-tp4689546p4689628.html
Sent from the Act
I agree that LevelDB has bugs. KahaDB with a shared filesystem master/slave
is still the standard practice for a highly-available broker installation.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Is-JDBC-still-used-tp4689546p4689627.html
Sent from the ActiveMQ - User
That's close. Selectors can be terrible for performance.
The way ActiveMQ applies selectors is like this:
ON MESSAGE DISPATCH
WHILE ( message is NOT dispatched ) AND ( more consumers exist )
IF selector matches
THEN
DISPATCH message
END IF
The problem for per
ActiveMQ Network connections are only supported using the OpenWire
protocol so you need to use something along the lines of your first
configuration:
The clients can use AMQP etc to connect to a given broker provided the
corresponding TransportConnector is c
Hi,
I am trying to setup an active mq cluster as "network of brokers" and facing
some issues in getting it to success if I use AMQP protocol ( between
consumer, producer and brokers). And With TCP/Openwire it seems to be
working fine. I am using 5.8.0 version of Active MQ.
Looking for some valua
I would look at a stack trace inside the application - try to find the
consumer threads and see if they are active, and if-so, what they are doing.
If all is normal, they should be waiting to receive a message from the
ActiveMQ transport.
Also, check the broker logs for messages. Anything relate
Hi,
I have a session aware message listener inside a DMLC with 5 concurrent
consumers consuming messages from a queue. This listener will send a message
everytime it receives a messages using the same session object to another
topic by creating a producer.
This setup runs fine for around 15 days a
10 matches
Mail list logo