Any reason why this is happening? It says connected from "NULL" ? Sounds like
a bug.
Thanks,
Anuj
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I'm sorry, the only thing I understand from your question is that scheduled
messages aren't working for you, but I didn't understand the rest of what
you were saying. Can you please explain further? And can you please explain
what behavior you expect and what behavior you see instead?
Can you plea
I was wondering looking at the releases on github
(https://github.com/apache/activemq/releases) and it looks like new releases
came out pretty frequently, but it's been a while and we're waiting on a
particular fix, so was wondering if there was a way to know when the next
release would be made or
In addition, read and follow the Stuck Messages section of the Network of
Brokers page I linked to earlier to avoid stranding messages.
On Sep 18, 2017 12:42 PM, "Raffi" wrote:
> Remove "rebalanceClusterClients=true", it distributes connections across
> brokers, likely exacerbating your problem.
Remove "rebalanceClusterClients=true", it distributes connections across
brokers, likely exacerbating your problem. Is "duplex="true" enabled from
both ends of the connector? If so, enable it from one end only, or, remove
it entirely and use static connections between the brokers.
--
Sent from:
Yes our Consumers are always up and running and there were actually two
subscribers at the time of this issue we have seen with stuck messages. This
is more seems to happen very frequently with 5.15.0 version causing panic
withing the team on whether its good to set up network of brokers or not. I
AMQ scheduled delay messages are not delivered ,any limit value for
scheduled messages to be configured ?or exceeding any limit on the number of
delayed messages
Version Activemq 5.14
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Trying to understand the cause for the following error getting logged each
time the auth plugin syncs with LDAP. We use LDAP server for storing
queue/topic permissions, but all destinations are dynamic, so a policy entry
may not always have a physical destination counterpart in ActiveMQ; that's
our
Will this work on messages that are marked as 'Persistent'?
I have changed the config to now have processexpired to false. I understand
why the previous one would be circular in processing.
Just wondering about persistent messages.
Chris
--
Sent from: http://activemq.2283324.n4.nabble.com/Act
On 09/18/2017 10:25 AM, khandelwalanuj wrote:
Hi,
I am using ActiveMQv5.14.
We observed issues with durable java subscribers using TCP connector that
lot of time after client/broker restart clients were not able to connect
back to the broker and see below exception *"connected from null"*
Lot
Hi,
I am using ActiveMQv5.14.
We observed issues with durable java subscribers using TCP connector that
lot of time after client/broker restart clients were not able to connect
back to the broker and see below exception *"connected from null"*
Lot of time after client restart, we get below exce
11 matches
Mail list logo