Thanks for your reply!
So one could argue that the once-and-only-once guarantee of the jms spec
cannot be fulfilled in the special edge case, where there's a not yet
committed, reply lost happening.
--
View this message in context:
Wanted to ask if there's a way to disable MBeans creation for
sessions/producers/consumers in ActiveMQ?
In certain setups (such as when using JTA/XA), not everything can be pooled,
and new producers/sessions are frequently created. This causes a constant
stream of new MBeans as well.
James
note - as part of apollo - there was some tooling around export/import
of message stores.
apollo does import and 5.x does export [1].
I guess it would not be much work to provide a 5.x import tool.
Scheduler store is still an outlier though.
[1]
we are using activeMQ5.11.1 on REDHAT 6.5 server enterprise with kernel
2.6.32 we open two transports, TCP and STOMP clients send requests to queue
using stomp and consumer is consuming the requests through tcp. we face this
exception after 140 connections opened
that does not exist at the moment, but it has come up before and it
would be a nice enhancement. JMX becomes a bottleneck in a dynamic
broker and disabling jmx altogether is not a viable option.
I know in karaf 2.4/3.0 there is role based access control via an
mbean server filter - maybe that
that is an oversight, when purge is called from a jmx op, we want to
log the event, but it is also called to clear a temp queue when the
temp queue is deleted and that should not generate a log message. I
think that is your case.
Can you open a jira to track this so that others will see the
Import/export of the stores still won't roll a non-durable topic
subscription from the old to the new broker, which means that when the
consumer disconnects from the old broker it will lose all unconsumed
messages as well as any messages produced between when it disconnects from
the old broker and
OK. That’s good to know. I have a large number of connections so I have
to look at each one. I wonder if this could also be the issue. AKA too
many connections.
On Tue, Mar 10, 2015 at 6:19 PM, Tim Bain tb...@alumni.duke.edu wrote:
You should be able to confirm that the prefetch buffers are
I’m still trying to track down some issues with ActiveMQ …
One is that I have 5 ActiveMQ servers now, and each one has about 3000
messages pending. So 15000 messages in queues.
These are non-persistent queues, plenty of memory and plenty of CPU, but
the workers are just blocked waiting to
You should be able to confirm that the prefetch buffers are empty by
inspecting the JMX MBeans on the broker. Look at the consumers for the
destination, and for each one look at its DispatchedQueueSize attribute.
Keep in mind that slow consumers are identified *ONLY* if you configure one
of the
If you make a single consumer, you'll only get one message at a time by
default (so only one thread will be doing any work). You'd have to use
client acknowledgement or selective acknowledgement to get more than one
message at a time. I'd probably leave many consumers but tune down your
prefetch
Hi, I'm with a doubt about how configure fine my system.
I'm tryng to start a master/slave broker and using
createTablesOnStartup=true in jdbcPersistenceAdapter I watched that this
create 3 tables
ACTIVEMQ_ACKS;
ACTIVEMQ_LOCK;
ACTIVEMQ_MSGS;
But too this create a register with ID 1 in the table
Are the messages getting hung up in the broker or in the client? (Do the
consumers have empty or full prefetch buffers?)
On Tue, Mar 10, 2015 at 6:47 PM, Kevin Burton bur...@spinn3r.com wrote:
I’m still trying to track down some issues with ActiveMQ …
One is that I have 5 ActiveMQ servers
I’m actually wondering if this is my issues. I’m creating one session per
thread. So perhaps some of the threads have work to do, but they’re each
prefetching a bunch of work when in reality a better strategy might the to
have one master listener and then dispatch messages to each thread.
On
This is exceedingly bizarre. Now ActiveMQ is refusing to deliver ANY
messages to my workers.
This is very bizarre, no code has changed. Nothing. It’s just refusing to
give work.
If I set the prefetch to 0 or 1, it does work for a few moments, then halts.
99% certain I’m committing all my
The broker. I’ll assume the prefetch brokers are empty. I’m looking into
debugging that now but I don’t have tools to introspect.
The broker has thousands of messages.
I just confirmed that a restart DOES improve the situation.
It’s possible that they’re being marked as slow consumers but not
Ok, makes sense, thanks.
https://issues.apache.org/jira/browse/AMQ-5656
- Original Message -
From: Gary Tully gary.tu...@gmail.com
To: users@activemq.apache.org users@activemq.apache.org; Martin Lichtin
lich...@yahoo.com
Cc:
Sent: Tuesday, March 10, 2015 2:42 PM
Subject: Re:
We are planning on having 3 activemq brokers and 3 zookeeper with master
slave, replicated level db store configuration.
Can we have zookeeper on activemq server or they have to be seperate?
Seperate will require 6 vm's, whereas having zookeeper and activemq on same
server will require only 3
Working my way through the code and the debug log from
the test, I see that the ZooKeeper group is getting emptied
out after session expiration occurs:
before the timeout:
2015-03-10 12:09:50,614 | DEBUG | ActiveMQ Task | ZooKeeper group for
01 changed: Map(foo -
19 matches
Mail list logo
