[jboss-user] [Clustering/JBoss] - JBoss5.0.0.Beta1 multiple instances error

[jbs99]

Hi, 
 I am facing some issues while doing the multi server instances on the same machine using JBoss5.0.0.Beta1 on XP machine. I am able to run the same with JBoss 4.0.5GA version. I searched the threads but not able to find the solution. If any body come across this error please help me in resolving this. Here are the steps i followed (The similar steps are working fine in JBoss4.0.5GA)

  1. Copied "all" server as "jboss1" and mapped the ServiceBindingManager to "ports-01" (as described in the document)
  2. Copied "all" server as "jboss2" and mapped the ServiceBindingManager to "ports-02"
  3. Started the jboss1 server.
  4. Started the jboss2 server. Here i got the below error.


  | 2007-01-02 16:02:16,546 ERROR [org.apache.coyote.http11.Http11Protocol] Error initializing endpoint
  | java.net.BindException: Address already in use: JVM_Bind:8080
  | 	at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:499)
  | 	at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)
  | 	at org.apache.catalina.connector.Connector.initialize(Connector.java:1024)
  | 
  5. Even after the above error i could able to see that the jboss2 is joined to jboss1 and jboss1 has become the dataOwner.

  | 2007-01-02 16:03:25,890 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Data owner address 192.168.57.35:4608
  | 2007-01-02 16:03:25,890 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Entering updateGroup.  Current group: BuddyGroup: (dataOwner: 192.168.57.35:4608, groupName: 192.168.57.35_4608, buddies: []).  Current View membership: [192.168.57.35:4608, 192.168.57.35:4625]
  | 2007-01-02 16:03:26,781 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates - trying with colocated buddies as well.
  | 2007-01-02 16:03:26,796 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates - trying again, ignoring buddy pool hints.
  | 2007-01-02 16:03:26,812 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates - trying with colocated buddies as well.
  | 2007-01-02 16:03:26,859 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Assigning new buddies to buddy group [192.168.57.35_4608].  New buddies are [192.168.57.35:4625]
  6. I deploed the stateless session bean on both servers and able to get the out put.
  7. Now i stopped the jboss1. and immediatly the jboss2 console is displayed the message that the jboss2 has become the dataOwner

  | 2007-01-02 16:21:08,484 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Data owner address 192.168.57.35:4625
  | 2007-01-02 16:21:08,484 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Entering updateGroup.  Current group: BuddyGroup: (dataOwner: 192.168.57.35:4625, groupName: 192.168.57.35_4625, buddies: [192.168.57.35:4608]).  Current View membership: [192.168.57.35:4625]
  | 2007-01-02 16:21:08,546 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates - trying with colocated buddies as well.
  | 2007-01-02 16:21:08,546 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates - trying again, ignoring buddy pool hints.
  | 2007-01-02 16:21:08,546 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates - trying with colocated buddies as well.
  | 2007-01-02 16:21:08,562 INFO  [org.jboss.cache.buddyreplication.NextMemberBuddyLocator] Expected to look for 1 buddies but could only find 0 suitable candidates!
  | 2007-01-02 16:21:08,562 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Removing obsolete buddies from buddy group [192.168.57.35_4625].  Obsolete buddies are [192.168.57.35:4608]
  | 2007-01-02 16:21:08,593 INFO  [org.jboss.cache.buddyreplication.BuddyManager] New buddy group: BuddyGroup: (dataOwner: 192.168.57.35:4625, groupName: 192.168.57.35_4625, buddies: [])
  | 2007-01-02 16:21:08,609 DEBUG [org.jboss.cache.buddyreplication.BuddyManager] Instance 192.168.57.35:4625 broadcasting membership in buddy pool default to recipients null
  8. Now the server should able to server the session bean requests but it is throwing the errors. 

Thanks
-Jb

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997255#3997255

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997255