-
1. Re: Facing issue with the clustering in JBoss 5
wdfink Nov 18, 2010 8:27 AM (in response to saurvals)The log:
<N,11/18/10 10:28:17 UTC,NAKACK> 137.72.224.231:1710] discarded message from non-member 137.72.224.112:4356, my view is [137.72.224.231:1710|0] [137.72.224.231:1710]
looks like that you have set the cluster parameter different and the JBoss instances will drop the message from the other....
also the entries of SQLExceptions points to some problems.
BTW you should use the JBoss 5.1 because of different fixes.
Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@d87731[state=NORMAL mc=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@12606c9 handles=0 lastUse=1290081600015 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$PoolBySubject@e6c8d2 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@18a9414 xaResource=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@12606c9 txSync=null]java.sql.SQLException: pingDatabase failed status=-1 -
2. Re: Facing issue with the clustering in JBoss 5
saurvals Nov 18, 2010 8:34 AM (in response to wdfink)Thanks for the quick reply,
When you say clustered parameter are different, could you please let us know which files we should be looking at? Those SQL exceptions were due to Database unavailability and we know the reason, so we can ignore that.
Thanks,
Saurabh V.
-
3. Re: Facing issue with the clustering in JBoss 5
saurvals Nov 18, 2010 9:11 AM (in response to saurvals)We found the difference in jgroup conf parameter and now it is working.
THanks,
Saurabh V.
-
4. Re: Facing issue with the clustering in JBoss 5
wdfink Nov 18, 2010 10:45 AM (in response to saurvals)A good starting point will be the JBossHA wiki http://community.jboss.org/wiki/JBossHA