Thanks Tim. There is no consistency, it appears to be somewhat random.
I can't attach a debugger unfortunately, I'll have to setup a test network
of sorts to try to reproduce it. :(
mike
--
View this message in context:
http://activemq.2283324.n4.nabble.com/durable-subscribers-causing-messag
Is there any consistency in which sensor brokers succeed and which fail, or
is it random every time?
If you're able to download the source code for your version of ActiveMQ and
attach a debugger to one of your sensor brokers, you could set breakpoints
and watch the subscription request from broker
You could start by doing code inspection and looking to see if there is any
code path where you could fail to close a connection once you open it,
which wouldn't require access to the customer environment.
Was there anything unusual in the logs around the time the errors were seen?
Finally, your
We are running ActiveMQ 5.10.0 with a network of brokers. For one topic
called 'results' we have one subscriber running on a single broker 'X' and
many (9 in staging, 24 in production and growing) brokers (let's call them
sensors) connected in with full duplex connections, each broker with a
produc
Hello,
This is happening in customer end and not in our local system to debug here.
This is happened only once and issue got resolved when customer restarted
their server.
But my asking is, What information i can gather from customer and what
customer needs to check at his end if this situation
Do anyone got a chance to look into it
Can someone help?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Virtual-Destination-vs-Composite-Destination-tp4685626p4685690.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi
I'm trying to get an existing (and working) apachemq installation running
as a specific user under init.d.
I have it working if I dont specify the user and allow it to run as root.
However if I change the user in the /etc/default/activemq file to the
required user I get the following output, an
