[mod_cluster-issues] [JBoss JIRA] Updated: (MODCLUSTER-85) HAModClusterService can throw NullPointerExceptions after a partition merge
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Thu Aug 20 12:36:23 EDT 2009
[ https://jira.jboss.org/jira/browse/MODCLUSTER-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro updated MODCLUSTER-85:
-----------------------------------
Fix Version/s: 1.0.3.GA
1.1.0.CR1
> HAModClusterService can throw NullPointerExceptions after a partition merge
> ---------------------------------------------------------------------------
>
> Key: MODCLUSTER-85
> URL: https://jira.jboss.org/jira/browse/MODCLUSTER-85
> Project: mod_cluster
> Issue Type: Bug
> Affects Versions: 1.0.0.GA
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 1.0.3.GA, 1.1.0.CR1
>
>
> This is caused by updateClusterStatus rpcs returning null if a merged node has master status.
> Make sure all rpcs get the same treatment.
> 2009-07-27 14:29:48,134 INFO [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (Incoming-20,10.248.107.114:32770) New cluster view for partition DefaultPartition: 4 ([10.240.62.47:1099, 10.248.107.114:1099, 10.249.195.196:1099] delta: 2)
> 2009-07-27 14:29:48,137 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) Merging partitions...
> 2009-07-27 14:29:48,137 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) Dead members: 0
> 2009-07-27 14:29:48,137 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] (AsynchViewChangeHandler Thread) Originating groups: [[10.240.62.47:32769|3] [10.240.62.47:32769, 10.249.195.196:32769], [10.248.107.114:32770|0] [10.248.107.114:32770]]
> 2009-07-27 14:29:50,878 ERROR [org.apache.catalina.core.ContainerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Exception invoking periodic operation:
> java.lang.NullPointerException
> at org.jboss.modcluster.ha.HAModClusterService$ClusteredCatalinaEventHandler.updateClusterStatus(HAModClusterService.java:896)
> at org.jboss.modcluster.ha.HAModClusterService$ClusteredCatalinaEventHandler.status(HAModClusterService.java:836)
> at org.jboss.modcluster.ha.HAModClusterService$ClusteredCatalinaEventHandler.status(HAModClusterService.java:781)
> at org.jboss.modcluster.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:157)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1348)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1612)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1601)
> at java.lang.Thread.run(Thread.java:636)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the mod_cluster-issues
mailing list