Win a copy of The Journey To Enterprise Agility this week in the Agile and Other Processes forum! And see the welcome thread for 20% off.
  • 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 ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

wrong broker address with multicast lookup  RSS feed

 
Ranch Hand
Posts: 260
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi,

my jms broker (activemq) is installed on server "JMSBROKER".

the connector settings are as following:

<transportConnectors>
<transportConnector name="zTransport" uri="tcp://localhost:61616" discoveryUri="multicast://zNet"/>
</transportConnectors>

<networkConnectors>
<networkConnector name="zJMSNetwork" uri="multicast://zNet" dynamicOnly="true"/>
</networkConnectors>

i have 3 other machines at the same subnet, running the clients that should connect to the broker on JMSBROKER. all clients are run totally in the same way: 3 instances of the same application are running by tomcat containers installed on all of the machines. the clients are using the following discovery uri to find a broker: discoverymulticast://zNet)?initialReconnectDelay=100
now to the problem itself.
while 2 machines are successfully connecting to the broker, the third one just doesn't make it.
QueueConnection.start() method never returns, there are no exceptions or errors thrown.
when i run netstat command on each of the clients machines i see that those connected show the following:
Proto Local Address Foreign Address State
TCP client_machine's_ip:port JMSBROKER_ip:61616 ESTABLISHED

but on the machine that makes troubles i see the following:
TCP client_machine's_ip:port 192.168.2.222:61616 SYN_SENT

i can't figure out where that 192.168.2.222 (which sometimes turns into 192.168.2.221) is coming from.
when tomcat is down, there is no connection to port 61616, so there is no additional process working with the same port running on this machine.
i guess that multicast broadcast mistakenly returns a wrong ip or something.

has anyone ever seen such behavior and have an idea where should i look for a solution?

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