• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

Continuous logging of java.net.SocketException: Connection reset in activeMQ logs

Ranch Hand
Posts: 558
Hibernate Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,

      Recently we started noticing WARN level message in our activeMQ logs

WARN  | Transport Connection to: tcp://xx.xx.xx.xx:xxxxxx failed: java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///xx.xx.xx.xx:xxxxxx@61616

Our network engineers determined that the IP address belongs to a subnet of one our subscribers. So, in order to pin point the issue, we asked all our subscribers to shut down their listeners and we ensured that there are no open connections on openwire. However, we still continued to see this warn messages being logged, even though there are no active subscribers.

What could be an issue here? What else can be done, to pin point the issue. Even though our network team confirmed that the IP address listed in the WARN, is coming from the same subnet as one of the subscribers, we were  still getting the warn, even after all subscribers are down.

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!