|
From: ScottMarlowNovell <do-...@jb...> - 2006-07-05 18:00:54
|
anonymous wrote : Scott, can you take a look at this in conjunction with what Alex did on configuring the HASingleton election policy and try to determine if solving this will require some change that breaks interoperability between releases (as opposed to just introducing a new feature). If it will break interoperability, please reschedule to 5.0.0.Beta. Otherwise, let's do this for 5.0.1.CR1. I don't see an interoperability issue here. >From a cluster management point of view, it would be nice to apply a generic solution for handling cluster errors such as SingletonService stop failure. The handling code as previously suggested, could deal with solving the problem or notifying someone that can deal with it (email/pager/send snmp trap). Otherwise, we can continue to log the error as we do now and continue execution (starting the new singleton) with the hope that something might work. Of course users can catch the exception directly in their code and do something better (if there is a better thing to do.) Should we invite someone from the JBoss ON team to give input on this (cluster management) issue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955617#3955617 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955617 |