[
https://issues.jboss.org/browse/WFLY-10109?page=com.atlassian.jira.plugin...
]
Jeff Mesnil commented on WFLY-10109:
------------------------------------
[~eduda] are you reproducing the issue with Artemis upstream?
Your run at
https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eduda-verifier...
is using Artemis 2.5.0:
{code}
13:58:17,832 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool --
74) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.5.0 [default,
nodeID=956f65b7-43d9-11e8-a727-fa163ec17fb4]
{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)