I am facing similar issue with ActiveMQ 5.10.
My question at Stackoverflow
http://stackoverflow.com/questions/26967455/failed-to-browse-topic-exception-in-activemq-logs
.
Can somebody help me here?
It seems to be a old bug which is supposed to get fix as part of this
Heres the code I run to get the errormessages.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Errors-when-using-h2-as-message-store-tp4686889p4687607.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
No, this is OK. The problems is that when the consumer VERSION 2 is off and
the consumer VERSION 2 is on, and I send messages of the 2 VERSION the
messages of VERSION 1 stay in the queue and are not consumed by the consumer
or sometimes are consumed a little part and the other stay in the queue.
Sorry, which consumer is off and which is on? Your email said VERSION 2
for both, but I assume that's not what you meant.
On Nov 18, 2014 5:41 AM, juanmanuel.romeraferrio
juanmanuel.romerafer...@gmail.com wrote:
No, this is OK. The problems is that when the consumer VERSION 2 is off and
the
Also, which version of ActiveMQ are you using?
On Nov 18, 2014 5:41 AM, juanmanuel.romeraferrio
juanmanuel.romerafer...@gmail.com wrote:
No, this is OK. The problems is that when the consumer VERSION 2 is off and
the consumer VERSION 2 is on, and I send messages of the 2 VERSION the
messages
Sorry, I know that my English is not good.
Consumer with selector Version=1 - ON
Consumer with selector Version 2 - OFF
I sent message of Version 1, and Version 2.
The messages of Version 2 are storage in the queue this is OK, because the
consumer is OFF.
The messages of Version 1, some are
Hi
I've just setup a three ActiveMQ 5.10 nodes in master/slave configuration
with replicated LevelDB. I've also setup the Zookeeper server in the same
nodes. Zookeeper seems running pretty much okay as far I can see.
When I crank up the first ActiveMQ node, it stops waiting for another node
in
Never mind. There is a issue already open against it. Fixed on 5.11
https://issues.apache.org/jira/browse/AMQ-5105
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-stucks-with-replicated-LevelDB-on-startup-tp4687634p4687662.html
Sent from the ActiveMQ - User
There's a workaround for 5.10 in the comments too, in case you didn't see
that.
On Tue, Nov 18, 2014 at 9:29 AM, guerra jg.gue...@gmail.com wrote:
Never mind. There is a issue already open against it. Fixed on 5.11
https://issues.apache.org/jira/browse/AMQ-5105
--
View this message in
It might be a problem with selectors, or with cursors, or maybe something
else.
What version of ActiveMQ are you using? I remember seeing JIRAs against
pre-5.8.0 versions about cursors that allowed messages to get stuck, so if
you're using an older version, you might just need to upgrade.
On
One problem we've run across while debugging ActiveMQ problems after the
fact (after the broker and clients have all been cycled) is that it's often
difficult to figure out which client was the one that corresponded to a
particular error in the broker's logs. The broker's log file will
generally
I'm using version 5.10.0
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-Selector-or-Composite-Destinations-tp4687564p4687673.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
It sounds like it could be a bug, though it might not be. Assuming you can
reproduce this in a test environment, you should try attaching a debugger
to the broker, setting breakpoints, and stepping through the relevant
code. AbstractSubscription.matches() and Queue.doAcutalDispatch() seem
like
13 matches
Mail list logo
