[jboss-jira] [JBoss JIRA] (AS7-4881) Remote EJB clients hanging after EJBClient.createSession when using DIST

[Paul Ferraro (JIRA)]

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

Paul Ferraro reassigned AS7-4881:
---------------------------------

    Assignee: Paul Ferraro  (was: jaikiran pai)

    
> Remote EJB clients hanging after EJBClient.createSession when using DIST
> ------------------------------------------------------------------------
>
>                 Key: AS7-4881
>                 URL: https://issues.jboss.org/browse/AS7-4881
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Radoslav Husar
>            Assignee: Paul Ferraro
>            Priority: Critical
>             Fix For: 7.1.3.Final (EAP)
>
>
> We are seeing that in stress tests (positive test, no failures), the clients hang when using DIST mode; both SYNC and ASYNC.
> The clients hang in method [1]; there is nothing suspicious on the server side. [2]
> The client has no knowledge about repl/dist topology, thus this should be a server-side issue.
> As of filing, we are investigating the issue.
> Job
> https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Performance-Clustering-4node/job/eap-6x-stress-ejbremote-dist-sync/2/
> Client code
> https://svn.devel.redhat.com/repos/jboss-qa/load-testing/sf-components/project-clustering-ejb3/trunk/
> App code
> https://github.com/rhusar/clusterbench
> [1]
> {noformat}
> "Runner - 1279" daemon prio=10 tid=0x00007f4388950000 nid=0x73df in Object.wait() [0x00007f423ed29000]
>    java.lang.Thread.State: WAITING (on object monitor)
> 	at java.lang.Object.wait(Native Method)
> 	at java.lang.Object.wait(Object.java:485)
> 	at org.xnio.AbstractIoFuture.awaitInterruptibly(AbstractIoFuture.java:123)
> 	- locked <0x00000006c0285ad0> (a java.lang.Object)
> 	at org.jboss.ejb.client.remoting.IoFutureHelper$1.get(IoFutureHelper.java:57)
> 	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.openSession(RemotingConnectionEJBReceiver.java:236)
> 	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)
> 	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)
> 	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)
> {noformat}
> [1]
> {noformat}
> "EJB default - 10" prio=10 tid=0x00007fefcc059000 nid=0x308b waiting on condition [0x00007fefa7a33000]
>    java.lang.Thread.State: WAITING (parking)
> 	at sun.misc.Unsafe.park(Native Method)
> 	- parking to wait for  <0x00000006bfe65cc8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> 	at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
> 	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
> 	at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
> 	at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> 	at java.lang.Thread.run(Thread.java:662)
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {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