This week's book giveaway is in the Open Source forum.
We're giving away four copies of Programmers Guide to Apache Thrift and have Randy Abernethy on-line!
See this thread for details.
Win a copy of Programmers Guide to Apache Thrift this week in the Open Source forum!
  • 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:
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
Bartenders:
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

Clustering issue with HA-JNDI with JBOSS 5 EAP  RSS feed

 
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am using JBOSS 5 EAP application server for our product.
We have created two separate nodes for testing node1 and node2.

I have done following for enabling clustering,
-> Gave partition name in startup file
-> Gave same multicast address.

My node1 is running on 1699 (JNDI) and 1700 (HA-JNDI)
and node2 is running on 1799 (JNDI) and 1800 (HA-JNDI)

I want to achieve below scenario,

If node1 gets fail, all request coming to 1700 port should be diverted in cluster's node2 (means 1800 port) and vice versa for node2.

I can achieve this using giving two jndi properties list in lookup code,
i.e
"p.put(Context.PROVIDER_URL, "192.168.6.102:1700,192.168.6.102:1800");"

Is this the proper way?

I want to give only "192.168.6.102:1700" and if node1 is disabled, then request should be forwarded to node2, as both nodes were in same cluster.

Please help me.

Thanks,
Rushabh
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!