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.
