[
https://issues.jboss.org/browse/WFLY-10109?page=com.atlassian.jira.plugin...
]
Jeff Mesnil edited comment on WFLY-10109 at 4/24/18 5:46 AM:
-------------------------------------------------------------
I'm assigning this issue to the activemq component as it requires additional log/info
from Artemis to be able to track down the race condition
was (Author: jmesnil):
I'm assigning this issue to the activemq component as it requires addition log/info
from Artemis to be able to track down the race condition
[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: 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)