Assuming that intranet == "stable network without any firewalls, misconfigurations, or hiccups" sounds like a huge mistake to me, and even more so when you've posted a question indicating that your logs are full of messages indicating that you have connection problems. That's not to say that there can't be bugs in the ActiveMQ code that could cause this behavior, but it's far from the only possible cause for what you're seeing. And I second what Art said: if your security department will allow it, you want to use a network sniffer such as WireShark or tcpdump (but WireShark is generally preferred) to figure out what's going on at a network level; trying to piece it together from only debug logs is likely to be difficult.
Also, to clarify: are you saying that for those 20ish clients who start experiencing connection problems, they experience those connection problems continually? Or do they recover after a few failures, only to have other clients fail later? One last thing: the version of ActiveMQ you're using is ALWAYS relevant information, and should be included in any post to this mailing list asking for help. How are we supposed to help figure out what's going on (or if it's a known bug that's been fixed in a later version) if you don't tell us what version you're using? For example, https://issues.apache.org/jira/browse/AMQ-5241 is fixed in 5.10.1 and 5.11.0, but I have no idea whether you're running a version that has that fix. Tim On Tue, Jul 7, 2015 at 6:32 PM, Cadmean <hzcadm...@hotmail.com> wrote: > 1. Since all the clients are in the INTRANET, I don't think the network > could > be a problem, but I will check it anyway. > > 2. Right now, I haven't started producing messages. In this case, all the > clients are just consumers without receving any messages. So I think the > message redeliveries can not be the cause of the problem. > > The next thing I will try to do is opening debug logging to see if there is > any helpful information. > > Thanks a lot. :D > > > artnaseef wrote > > First thing I would look at here is diagnostics from the network level > > itself. WireShark or tcpdump can be used to get a better understanding > of > > why the connections are dropping. > > > > If the network between the client and brokers is unreliable, this will > > happen a lot and it will significantly interfere with the messaging. > > > > Also check the broker log files for any indications of causes of the > > dropped connections. > > > > With all of that said, with the failover transport, these failures should > > be short-lived and all of the applications should continue to operate > > normally. The impact of greatest concern coming to mind is the increased > > probability of message redeliveries, but that is a normal occurrence with > > JMS (in other words, applications need to handle this possibility with or > > without these dropped connections). > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Transport-failed-please-helpT-T-tp4698539p4698757.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
