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

[Miroslav Novak (JIRA)]

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

Miroslav Novak commented on WFWIP-22:
-------------------------------------

Issue is still present in Artemis to 2.6.0 and Wildfly branch jmesnil/WFLY-9407_upgrade_artemis_2.4.0_with_prefix (commit 54b131dc63dfd4bb74bb44b3f8c3402964059afa)


> [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups 
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFWIP-22
>                 URL: https://issues.jboss.org/browse/WFWIP-22
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Artemis, JMS
>            Reporter: Miroslav Novak
>            Assignee: Martyn Taylor
>            Priority: Blocker
>              Labels: activemq, 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)