-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
Having queue defined as follows
<jms-queue name="InQueue" entries="jms/queue/InQueue java:jboss/exported/jms/queue/InQueue" durable="true"/>
Client is instantiating it directly using its name.
HashMap<String, Object> map = new HashMap<String, Object>(); map.put("host", hostName); map.put(TransportConstants.HTTP_UPGRADE_ENABLED_PROP_NAME, true); map.put("port", httpPort); TransportConfiguration transportConfiguration = new TransportConfiguration(NettyConnectorFactory.class.getName(), map); try { ConnectionFactory cf = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration); Queue orderQueue = ActiveMQJMSClient.createQueue("InQueue"); connection = cf.createConnection(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); MessageProducer producer = session.createProducer(orderQueue); connection.start(); ...
Client is not able to send messages to, because session.createProducer(orderQueue) throws following exception
javax.jms.InvalidDestinationException: Destination InQueue does not exist at org.apache.activemq.artemis.jms.client.ActiveMQSession.createProducer(ActiveMQSession.java:326)
This is regression against EAP 7.1.0
Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_with_prefix (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
- blocks
-
WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x
- Closed
- clones
-
WFWIP-95 [Artemis 2.x Upgrade] Client is not able to instantiate destinations by names
- Closed
- duplicates
-
WFWIP-115 [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix
- Resolved
-
ENTMQBR-1621 [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix
- Closed
- is blocked by
-
ENTMQBR-1075 Client is not able to create queues
- Closed