you still need to use the failover: scheme in 5.2 when you provide a url and want failover. The change only effects users who do not provide a brokerUrl to the ActiveMQConnectionFactory. That is the only case where the defaultUrl is used.
2009/3/13 Ryan Moquin <[email protected]> > I've been using ActivbeMQ 5.2 for a while now and am having a problem where > my topic subscribers seem to lose their connections to the ActiveMQ broker > after around 1,000 messages (it seems like they consistently lose their > connection at just over 1,000 messages). My publishers (SOA services in > Servicemix) and my consumers (in a separate VM) are on the same machine. I > can tell my consumers are losing their connections by looking at the > activemq web console, I can see the connections will just go away while my > publishers keep sending. I don't see any error anywhere on my consumer > side > indicating why the connections were dropped. Now, assuming some weird > network issue (even though they are on the same machine, it seems that > network issues will affect local connections) is causing my client to drop, > I thought that ActiveMQ 5.2.0 used failover by default when you use a URL > such as: > > tcp://localhost:61616 > > Since according to the release page it says: > > "The default ActiveMQConnectionFactory< > http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html > >brokerUrl > now uses the failover > transport <http://activemq.apache.org/failover-transport-reference.html>." > > Am I mistaken on that? Or do I still need to use the failover URL? Is it > common for a consumer to lose a connection like this and using a failover > URL is all I need to put back in? I never saw this problem when using > earlier versions of ActiveMQ with failover. Since I moved to 5.2, I > removed > the failover part of the URL because I thought 5.2 used it by default. Any > clarification on this would be helpful, or even a suggestion on how to > troubleshoot the issue. It seems like the only way I might be able to get > some log output to help with the problem is by turning on debug mode? > > Thanks for any help! > > Ryan > -- http://blog.garytully.com Open Source SOA http://FUSESource.com
