Deployed MDBs utilising generic JMS resource adapter fail to authenticate

Environment

• Red Hat JBoss Enterprise Application Platform
  • 7.3.x

Issue

MDBs deployed in JBoss EAP 7.3.5 utilising generic JMS resource adapter will fail to authenticate with external TIBCO EMS broker.

2021-01-29 13:55:47,927 WARN  [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 3) Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@25f70034(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@4b294f76 destination=jms/topic/inTopic destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=false reconnectInterval=10 reconnectAttempts=-1 user=quickuser maxMessages=1 minSession=1 maxSession=15 connectionFactory=jms/cf/XATopicConnectionFactory jndiParameters={java.naming.provider.url=tcp://localhost:7222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory, java.naming.security.principal=quickuser, java.naming.security.credentials=<not shown>}): javax.jms.JMSSecurityException: authentication failed
        at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:744)
        at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1465)
        at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4412)
        at com.tibco.tibjms.TibjmsXAConnection.<init>(TibjmsXAConnection.java:30)
        at com.tibco.tibjms.TibjmsXATopicConnection.<init>(TibjmsXATopicConnection.java:29)
        at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:147)
        at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:255)
        at com.tibco.tibjms.TibjmsXAConnectionFactory.createXAConnection(TibjmsXAConnectionFactory.java:61)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:442)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:417)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupActivation(JmsActivation.java:316)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation.access$100(JmsActivation.java:58)
        at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:546)
        at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
        at org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
        at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
        at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
        at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
        at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
        at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
        at java.lang.Thread.run(Thread.java:748)
        at org.jboss.threads.JBossThread.run(JBossThread.java:485)

Resolution

Upgrade to JBoss EAP 7.3.7 or later.

Root Cause

This is bug This content is not included.JBEAP-20925. This is caused by regression in generic JMS resource adapter.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.