[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: JGroups Protocol Stack Configuration & Shunning Behavior

[jhowell@redhat.com]

Yeah this seems like it could be an issue.  Since we don't sync state upon reconnect automatically and do it manually, a customer has run into this issue.

They are dynamically changing their datasource(change and redeploy).  When they do that it causes the jgroups channel to redeploy, which does away with the state. But since the post office is not restarting, the state is null and they get a null pointer exception.  I'm going to enter a bug about this, which will probably be fixed with a depends in a strategic location, so that the post office redeploys with the rest of the application. 

But it looks like that when a member gets shunned, they can't rejoin the cluster without a reboot.  The problem with this is that the other channels behaves differently and doesn't have to be rebooted(JBCache, Default Partition, etc).  This means that after a shun, all of the other channels can rejoin except for the JBM channels.  Everything else will work except for JBM.   It isn't clear at that point that the server has to be restarted.  If we continue, we should add messages that redisply in a loop, "This JBM member has been shunned, a reboot is REQUIRED of this server".

Thoughts? Jay:)  

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

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