[jboss-user] [JBossCache] - Re: Error starting cache with TCP and TCPPING

[urisherman]

anonymous wrote : If you have the full stack trace, JGroups should spit out the reason why you cannot create the stack. 

That's what you'd think, but no..... all I got was that error message I posted.

Anyway, I realized the distro's version I downloaded might be incompatible with the one jbosscache uses, so I downloaded an earlier JGroups distro and now it's starting up properly.

This is my configuration now - 
anonymous wrote : 		
  | 			<TCP start_port="7050" loopback="true"
  | 				send_buf_size="100000" recv_buf_size="200000" />
  | 			<TCPPING timeout="3000" initial_hosts="10.106.124.240[7050],10.106.124.239[7050]"
  | 				port_range="3" num_initial_members="2" />
  | 			<FD timeout="2000" max_tries="4" />
  | 			<VERIFY_SUSPECT timeout="1500" down_thread="false"
  | 				up_thread="false" />
  | 			<pbcast.NAKACK gc_lag="100"
  | 				retransmit_timeout="600,1200,2400,4800" />
  | 			<pbcast.STABLE stability_delay="1000"
  | 				desired_avg_gossip="20000" down_thread="false" max_bytes="0"
  | 				up_thread="false" />
  | 			<VIEW_SYNC avg_send_interval="60000" down_thread="false"
  | 				up_thread="false" />
  | 			<pbcast.GMS print_local_addr="true" join_timeout="5000"
  | 				join_retry_timeout="2000" shun="true" />
  | 			<pbcast.STATE_TRANSFER down_thread="true"
  | 				up_thread="true"/>
  | 		
But I got a new problem - 
The first machine starts up just fine, I then add a node to the tree and start the second machine, which fails to retrieve the initial state - 

org.jboss.cache.CacheException: Initial state transfer failed: Channel.getState() returned false
        at org.jboss.cache.TreeCache.fetchStateOnStartup()V(TreeCache.java:3191)
        at org.jboss.cache.TreeCache.startService()V(TreeCache.java:1429)
        at org.jboss.cache.example.j2eeservices.JBossCacheManager.main([Ljava.lang.String;)V(JBossCacheManager.java:75)
        at jrockit.reflect.NativeMethodInvoker.invoke0(Ljava.lang.Object;ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
        at weblogic.t3.srvr.StartupClassService.invokeMain(Ljava.lang.String;Ljava.lang.Class;Ljava.lang.String;)V(StartupClassService.java:229)
        at weblogic.t3.srvr.StartupClassService.invokeClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(StartupClassService.java:160)
        at weblogic.t3.srvr.StartupClassService.access$000(Lweblogic.t3.srvr.StartupClassService;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(StartupClassService.java:36)
        at weblogic.t3.srvr.StartupClassService$1.run()Ljava.lang.Object;(StartupClassService.java:121)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
        at weblogic.t3.srvr.StartupClassService.invokeStartupClass(Lweblogic.management.configuration.StartupClassMBean;)V(StartupClassService.java:116)
        at weblogic.t3.srvr.StartupClassService.initialize()V(StartupClassService.java:60)
        at weblogic.t3.srvr.SubsystemManager.initialize()V(SubsystemManager.java:118)
        at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:895)
        at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
        at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
        at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)

I tried the solution suggested at the troubleshooting section, that the state might be taking longer to retrieve than configured as "InitialStateRetrievalTimeout", but that wasn't it, I gave it 50000 millis and it fails after less than 3 seconds, so it obviously has nothing to do with the timeout.....
Any ideas?

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

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