[jboss-jira] [JBoss JIRA] (WFLY-10109) [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil commented on WFLY-10109:
------------------------------------

thanks, your failure occurs when the RA on node2 tries to connect to Artemis on node1:

{code}
13:59:19,581 WARN  [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ152005: Failure in broker activation org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter at e77d2b4c destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster]
	at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:761) [artemis-core-client-2.5.0.jar:2.5.0]
	at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:307) [artemis-ra-2.5.0.jar:2.5.0]
	at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:696) [artemis-ra-2.5.0.jar:2.5.0]
	at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
	at org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
	at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
	at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
	at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
	at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
	at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
	at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_162]
	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{code}

It is not an issue with JGroups as we have logs on node2 that says that nodes are in the same cluster:

{code}
13:58:17,574 INFO  [org.infinispan.CLUSTER] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [node-1|1] (2) [node-1, node-2]
{code}

I'll investigate further why the RA on node2 does not receive the broadcast from node1.

> [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups 
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10109
>                 URL: https://issues.jboss.org/browse/WFLY-10109
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Miroslav Novak
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>              Labels: feature-branch-blocker
>         Attachments: log
>
>
> Sometimes happens that MDB does not start to consume messages from remote server. There are not warning or error messages in log. 
> Test Scenario:
> * Start server with deployed InQueue and OutQueue
> * Start 2nd server with configured pooled-connection-factory to connect to 1st server
> * Deploy MDB to 2nd server - mdb is consuming messages from InQueue and sending to OutQueue
> * Start sending messages to InQueue to 1st server
> * Let MDB processing messages from InQueue
> * Start consuming messages from OutQueue from 1st server
> Pass Criteria: There is the same number of sent and received messages
> Actual Result: Sometimes happens that Mdb does not start to consume messages. 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)