[jboss-jira] [JBoss JIRA] (WFLY-2330) Test set org.jboss.as.test.clustering.cluster.registry.RegistryTestCase fails with NPE

Wed Oct 23 11:54:02 EDT 2013

    [ https://issues.jboss.org/browse/WFLY-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12824355#comment-12824355 ] 

Paul Ferraro commented on WFLY-2330:
------------------------------------

That is weird.  It appears that a thread is attempting to connect the jgroups channel before it is completely built.  The former is triggered by the GlobalComponentRegistryService, the latter is triggered via the ChannelService.  The MSC dependency chain is supposed to ensure that this does not happen.
Suspiciously, the ChannelService dependency of an EmbeddedCacheManagerService (on which the GlobalComponentRegistryService depends) is optional.  Perhaps this allows the GlobalComponentRegistryService to start before the ChannelService is fully started?

> Test set org.jboss.as.test.clustering.cluster.registry.RegistryTestCase fails with NPE
> --------------------------------------------------------------------------------------
>
>                 Key: WFLY-2330
>                 URL: https://issues.jboss.org/browse/WFLY-2330
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 8.0.0.CR1
>         Environment: Oracle JDK 1.7.0_45 on Solaris SPARC on SunBlade 2000.
>            Reporter: Frank Langelage
>            Assignee: Paul Ferraro
>         Attachments: org.jboss.as.test.clustering.cluster.registry.RegistryTestCase-SYNC-tcp-output.txt, org.jboss.as.test.clustering.cluster.registry.RegistryTestCase-SYNC-tcp.txt, TEST-org.jboss.as.test.clustering.cluster.registry.RegistryTestCase-SYNC-tcp.xml
>
>
> Test org.jboss.as.test.clustering.cluster.registry.RegistryTestCase fails for me because of a NPE.
> See attached log files of this test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira