Hi,
We have a number of devices in the field that are connecting to ActiveMQ.
ActiveMQ is setup in a master-slave configuration with a loadbalancer in
front of it. Devices connect through the loadbalancer using the Eclipse Paho
client library.
>From time to time we are receiving the following err
I'm grateful for the help I get from the people on this list, so I'm happy
to offer what help I can in return.
On Jan 12, 2015 3:49 PM, "Kevin Burton" wrote:
> BTW Tim.. thanks for all your feedback to all these posts. :)
>
> Kevin
>
> On Mon, Jan 12, 2015 at 7:41 AM, Tim Bain wrote:
>
> > Ther
The other obvious question is, have you confirmed that nothing else is
listening on the JMX port you're trying to use? You probably have, but
since you didn't say I thought it was worth double-checking.
On Jan 12, 2015 2:54 PM, "artnaseef" wrote:
> Check the setting in the XML file; if
> create
I will work on something to try to force the network connection failure
without using openvpn to be my networking failure trigger.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-hanging-after-a-producer-fails-for-being-inactive-tp4689775p4689828.html
Sent from t
Sounds like this is easy to reproduce. Can you write a small (well, as small
as possible) junit that reproduces the problem?
It may be necessary to get creative in forcing the network connection
failure.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-hanging-a
I have been able to reproduce the issue with 5.10.
I am currently trying to walk through the activemq 5.9 code to figure out
whats going on.
I am seeing
DEBUG Queue - Incoming toPageIn: 200, Inflight: 0, pagedInMessages.size 0 in
my log files
In the org.apache.activemq.broker.region.Queue at line
BTW Tim.. thanks for all your feedback to all these posts. :)
Kevin
On Mon, Jan 12, 2015 at 7:41 AM, Tim Bain wrote:
> There are three things that happened here:
>
>1. Your master broker stopped sending messages to this slave for 30
>seconds. (Did any other slaves experience a similar
That's a curious problem. Have you tried with 5.10? I know there has been
some effort around the area of the inactivity timeouts on connections.
Also, if you could produce a minimal test program, that would certainly
help.
--
View this message in context:
http://activemq.2283324.n4.nabble.co
Check the setting in the XML file; if
createConnector="true", then keep that line commented-out as it leads to
duplicate attempts to setup JMX.
If that's not the issue, please provide an error message or other symptoms
related to the broker failure to startup.
--
View this message in context:
Good point - when using this type of selector scenario, using message TTLs or
some other means of making sure messages are consumed is important.
As mentioned earlier, grabbing a stack trace may be telling, although it may
be a little more difficult to understand since the DMLC is involved.
Impac
You say you're doing request-response with a 60-second timeout on the
response. If some of those responses took longer than 60 seconds, I'd
expect that that particular response message wouldn't be removed from the
response queue, and after some number of them I'd expect that the response
queue wou
There are three things that happened here:
1. Your master broker stopped sending messages to this slave for 30
seconds. (Did any other slaves experience a similar disconnect?) This
caused the slave to abort the connection. This could happen due to network
perturbations, but I'd expe
Please help i am not able to get anywhere with this issue.
Atleast tell me what more information to collect and what things to look out
for next time this issue happens which can help to resolve/debug this issue.
Thanks,
Abhi
--
View this message in context:
http://activemq.2283324.n4.nabble.
13 matches
Mail list logo
