Loading...

XML

Word

Printable

Type: Bug
Resolution: Obsolete
Priority: Blocker
Fix Version/s: None
Affects Version/s: 7.2.0.GA
Component/s: ActiveMQ, JMS
Labels:
- feature-branch-blocker

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.2.0.GA

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

For more information about origin of this issue see ~~JBEAP-13856~~.

By convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the name "jms.queue.orders.europe". The address at which the core queue is bound is also given by the core queue name. Source: https://activemq.apache.org/artemis/docs/1.5.0/jms-core-mapping.html

In Artemis 2.x the JMS queues and topics are not prefixed by jms.queue and jms.topic anymore.

This is an umbrella Jira for all issues caused by change in address naming conventions.

blocks

WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x

Closed

is blocked by

ENTMQBR-1079 Address-full-policy isn't being applied properly for 1.x JMS client

Closed

JBEAP-13858 [Artemis upgrade] Cluster connections needs to be reconfigured

Closed

JBEAP-13859 [Artemis upgrade] Address settings needs to be reconfigured

Closed

JBEAP-13860 [Artemis upgrade] Security settings needs to be reconfigured

Closed

JBEAP-13861 [Artemis upgrade] Core bridges need to be reconfigured

Closed

JBEAP-13862 [Artemis upgrade] Diverts need to be reconfigured

Closed

JBEAP-13863 [Artemis upgrade] Migration of messaging data from EAP 7.1 to 7.2

Closed

JBEAP-13864 [Artemis upgrade] Client’s Core API references destinations using Artemis core addresses

Closed

JBEAP-13865 [Artemis upgrade] CLI operations may reference the destinations using Artemis core addresses

Closed

JBEAP-13866 [Artemis upgrade] JMX operations may reference the destinations using Artemis core address

Closed

JBEAP-14112 Address-full-policy isn't being applied properly for 1.x JMS client

Closed

WFWIP-14 [Artemis upgrade] MDB cannot connect to remote server via RA if destination is not deployed locally

Closed

(8 is blocked by)

Assignee:: Jeff Mesnil

Reporter:: Erich Duda (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2017/11/28 8:07 AM

Updated:: 2021/10/24 6:41 AM

Resolved:: 2018/03/08 6:55 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates