[jboss-jira] [JBoss JIRA] (WFLY-6047) NPE in InfinispanBeanManager.getWeakAffinity in split-brain test case

[Ladislav Thon (JIRA)]

Ladislav Thon created WFLY-6047:
-----------------------------------

             Summary: NPE in InfinispanBeanManager.getWeakAffinity in split-brain test case
                 Key: WFLY-6047
                 URL: https://issues.jboss.org/browse/WFLY-6047
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
            Reporter: Ladislav Thon
            Assignee: Paul Ferraro


In a DIST_SYNC test case involving remote EJBs and split brain ({{eap-7x-failover-ejb-ejbremote-netDown-dist-sync}}), I'm seeing NPEs in {{InfinispanBeanManager.getWeakAffinity}}:

{code}
06:10:50,514 ERROR [org.jboss.as.ejb3.remote] (default task-82) WFLYEJB0150: Could not write method invocation failure for method public abstract int org.jboss.test.clusterbench.common.ejb.CommonStatefulSB.getSerialAndIncrement() on bean named RemoteStatefulSBImpl for appname clusterbench-ee7 modulename clusterbench-ee7-ejb distinctname  due to: java.lang.NullPointerException
	at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.getWeakAffinity(InfinispanBeanManager.java:185)
	at org.jboss.as.ejb3.cache.distributable.DistributableCache.getWeakAffinity(DistributableCache.java:71)
	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.getWeakAffinity(MethodInvocationMessageHandler.java:260)
	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$500(MethodInvocationMessageHandler.java:68)
	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:230)
	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:254)
	at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.processMessage(VersionOneProtocolChannelReceiver.java:213)
	at org.jboss.as.ejb3.remote.protocol.versiontwo.VersionTwoProtocolChannelReceiver.processMessage(VersionTwoProtocolChannelReceiver.java:76)
	at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:159)
	at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
{code}

Various weird things are expected during split brain ({{AvailabilityException}}, replication timeouts etc.), but a NPE seems JIRA-worth.

Links:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-ejbremote-netDown-dist-sync/5/console-perf18/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-ejbremote-netDown-dist-sync/5/console-perf19/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-ejbremote-netDown-dist-sync/5/console-perf20/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-ejbremote-netDown-dist-sync/5/console-perf21/



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)