[jboss-jira] [JBoss JIRA] (WFLY-1690) Frequent failures in CommandDispatcherTestCase
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Sat Jul 13 01:52:21 EDT 2013
[ https://issues.jboss.org/browse/WFLY-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789469#comment-12789469 ]
jaikiran pai commented on WFLY-1690:
------------------------------------
The problem seems to be, after redeploying the application on a node (in this case node-1/ejb), the following WARN is written out:
{code}
[0m[0m00:42:12,723 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "command-dispatcher.jar" (runtime-name : "command-dispatcher.jar")
[0m[0m00:42:12,738 INFO [stdout] (EJB default - 2) Cluster 'ejb' successfully established view [node-0/ejb, node-1/ejb] within 0 ms.
[0m[0m00:42:12,744 INFO [stdout] (EJB default - 3) Executing command on cluster
[0m[0m00:42:12,749 INFO [stdout] (Incoming-4,shared=udp) Executing command on node-1/ejb
[0m[0m00:42:12,750 INFO [stdout] (Incoming-14,shared=udp) Executing command on node-0/ejb
[0m[0m00:42:12,752 INFO [stdout] (EJB default - 3) Executing command on node: node-1/ejb
[0m[33m00:42:18,605 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:24,148 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:30,068 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:35,631 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:41,548 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:47,478 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:53,392 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:42:59,086 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:43:05,026 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
[0m[33m00:43:11,065 WARN [org.jgroups.protocols.UDP] (TransferQueueBundler,shared=udp) null: no physical address for node-1/ejb, dropping message
{code}
Ultimately, the test fails with:
{code}
Caused by: java.lang.IllegalStateException: org.jgroups.TimeoutException: timeout sending message to node-1/ejb
at org.jboss.as.test.clustering.cluster.dispatcher.bean.ClusterTopologyRetrieverBean.getClusterTopology(ClusterTopologyRetrieverBean.java:50) [command-dispatcher.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [wildfly-ejb3-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273) [wildfly-ejb3-8.0.0.Alpha3-SNAPSHOT.jar:8.0.0.Alpha3-SNAPSHOT]
... 41 more
{code}
> Frequent failures in CommandDispatcherTestCase
> ----------------------------------------------
>
> Key: WFLY-1690
> URL: https://issues.jboss.org/browse/WFLY-1690
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
>
> Test is failing regularly. See http://lightning.mw.lab.eng.bos.redhat.com/project.html?projectId=WF&testNameId=6046695851152993698&tab=testDetails
> I'm going to @Ignore it.
--
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
More information about the jboss-jira
mailing list