NamingException from JMS clients after migration to EAP 7.2

Solution Verified - Updated -

Issue

  • NamingException from JMS clients after migration to EAP 7.2
  • When connecting to EAP 7.2 my old JMS clients don't work anymore

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In