[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

[Erich Duda (JIRA)]

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

Erich Duda commented on WFLY-10109:
-----------------------------------

[~jmesnil] I think this is not environment issue. The servers communicate through localhost.

I tried to run the test with thread which prints regularly thread dumps of all servers to files. However with this thread the test passed 50 times in row. I think the issue is caused by race condition and making of thread dumps changed slightly the execution so the issue hasn't appeared.

I think the best way how to investigate it is by adding more logs to the code. You can clone my job and use it for this purpose. It accepts parameters ARTEMIS_REPO and ARTEMIS_VERSION. When they are filled, custom version of Artemis is built and used with Wildfly build so you can easily add more logs to Artemis code.

> [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)