-
Bug
-
Resolution: Duplicate
-
Blocker
I'm not able to connect with MDB deployed on WF14/EAP 7.2.0 with new Artemis to destination deployed on EAP6.
CLI for configuration EAP7:
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-eap6-binding:add(port=6445) /subsystem=messaging-activemq/server=default/remote-connector=remote-eap6-connector:add(socket-bidning=remote-eap6-binding) /subsystem=messaging-activemq/server=default/pooled-connection-factory=remote-eap6:add(connectors=[remote-eap6-connector], entries=["jms/remote-eap6", "java:jboss/exported/jms/remote-eap6"], protocol-manager-factory="org.apache.activemq.artemis.core.protocol.hornetq.client.HornetQClientProtocolManagerFactory)
The MDB is annotated with
@MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "InQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") }) @ResourceAdapter("remote-eap6")
This setup worked with EAP 7.1.x and EAP 7.2.0.Beta with older Artemis
- blocks
-
WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x
- Closed
- duplicates
-
WFWIP-26 [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false
- Resolved