[jboss-jira] [JBoss JIRA] (AS7-4854) Failures on clustered remote EJB invocations in event of server shutting down using DIST SYNC cache (NullPointerException: Null keys are not supported!)

Radoslav Husar (JIRA) jira-events at lists.jboss.org
Tue May 22 04:50:18 EDT 2012


     [ https://issues.jboss.org/browse/AS7-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated AS7-4854:
--------------------------------

    Workaround Description: Workaround would be not to use DIST cache and use REPL instead.

    
> Failures on clustered remote EJB invocations in event of server shutting down using DIST SYNC cache (NullPointerException: Null keys are not supported!)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4854
>                 URL: https://issues.jboss.org/browse/AS7-4854
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Radoslav Husar
>            Assignee: jaikiran pai
>             Fix For: 7.1.3.Final (EAP)
>
>
> Remote client is up, but one server shuts down, results at first in 
> {noformat}
> 2012/05/21 12:09:33:112 EDT [WARN ][Runner - 177] SFCORE_LOG - Error sampling data:  <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not lookup session bean.>
>         org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not lookup session bean.
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.initSession(StatefulSBProcessorFactoryImpl.java:157)
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:58)
> 	at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
> 	at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.naming.NamingException: Failed to create proxy [Root exception is java.lang.RuntimeException: java.io.IOException: Channel Channel ID 8907f2dd (outbound) of Remoting connection 7821f46a to perf18/10.16.90.54:4447 has been closed]
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:115)
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.lookup(EjbNamingContext.java:96)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:392)
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.initSession(StatefulSBProcessorFactoryImpl.java:148)
> 	... 4 more
> Caused by: java.lang.RuntimeException: java.io.IOException: Channel Channel ID 8907f2dd (outbound) of Remoting connection 7821f46a to perf18/10.16.90.54:4447 has been closed
> 	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.openSession(RemotingConnectionEJBReceiver.java:247)
> 	at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:163)
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.doCreateProxy(EjbNamingContext.java:135)
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:113)
> 	... 7 more
> Caused by: java.io.IOException: Channel Channel ID 8907f2dd (outbound) of Remoting connection 7821f46a to perf18/10.16.90.54:4447 has been closed
> 	at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:111)
> 	at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:103)
> 	at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:517)
> 	at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:382)
> 	at org.jboss.remoting3.remote.RemoteConnectionHandler.receiveCloseRequest(RemoteConnectionHandler.java:205)
> 	at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:106)
> 	at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
> 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> 	at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> 	at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> 	at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> 	at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
> {noformat}
> and on later failures on NullPointerException: Null keys are not supported!
> {noformat}
> 2012/05/21 12:11:41:077 EDT [WARN ][Runner - 7] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data:  <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not lookup session bean.>
>         org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not lookup session bean.
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.initSession(StatefulSBProcessorFactoryImpl.java:157)
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:58)
> 	at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
> 	at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.naming.NamingException: Failed to create proxy [Root exception is java.lang.RuntimeException: java.lang.NullPointerException: Null keys are not supported!]
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:115)
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.lookup(EjbNamingContext.java:96)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:392)
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.initSession(StatefulSBProcessorFactoryImpl.java:148)
> 	... 4 more
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException: Null keys are not supported!
> 	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.openSession(RemotingConnectionEJBReceiver.java:247)
> 	at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:163)
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.doCreateProxy(EjbNamingContext.java:135)
> 	at org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:113)
> 	... 7 more
> Caused by: java.lang.NullPointerException: Null keys are not supported!
> 	at org.infinispan.CacheImpl.assertKeyNotNull(CacheImpl.java:196)
> 	at org.infinispan.CacheImpl.assertKeyValueNotNull(CacheImpl.java:201)
> 	at org.infinispan.CacheImpl.put(CacheImpl.java:699)
> 	at org.infinispan.DecoratedCache.put(DecoratedCache.java:319)
> 	at org.infinispan.AbstractDelegatingCache.put(AbstractDelegatingCache.java:308)
> 	at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore$1.invoke(InfinispanBackingCacheEntryStore.java:173)
> 	at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore$1.invoke(InfinispanBackingCacheEntryStore.java:170)
> 	at org.jboss.as.clustering.infinispan.invoker.BatchOperation.invoke(BatchOperation.java:19)
> 	at org.jboss.as.clustering.infinispan.invoker.RetryingCacheInvoker.invoke(RetryingCacheInvoker.java:60)
> 	at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.invoke(InfinispanBackingCacheEntryStore.java:239)
> 	at org.jboss.as.clustering.ejb3.cache.backing.infinispan.InfinispanBackingCacheEntryStore.insert(InfinispanBackingCacheEntryStore.java:177)
> 	at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.insert(SerializationGroupMemberContainer.java:304)
> 	at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.insert(SerializationGroupMemberContainer.java:51)
> 	at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.create(PassivatingBackingCacheImpl.java:122)
> 	at org.jboss.as.ejb3.cache.impl.GroupAwareCache.create(GroupAwareCache.java:67)
> 	at org.jboss.as.ejb3.cache.impl.GroupAwareCache.create(GroupAwareCache.java:41)
> 	at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:242)
> 	at org.jboss.as.ejb3.remote.protocol.versionone.SessionOpenRequestHandler$SessionIDGeneratorTask.run(SessionOpenRequestHandler.java:148)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 	at ...asynchronous invocation...(Unknown Source)
> 	at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:99)
> 	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.openSession(RemotingConnectionEJBReceiver.java:243)
> 	... 10 more
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list