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

All destinations in EAP 7.1 have prefix jms.queue or jms.topic. New destinations in EAP 7.2 won’t have these prefixes anymore, but if you import them from 7.1, they will.

Even if users correctly migrate the 7.1 configuration, they may end up in situation that destinations stored in the EAP 7.1 journal will still have “jms” prefixes after migration to EAP 7.2.

Customer impact: After migration of messaging data from EAP 7.1 to EAP 7.2 there may be differences in core addresses between old and new destinations.