Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20925

[GSS](7.3.z) WFLY-14378 - Generic JMS RA fails to authenticate

    XMLWordPrintable

Details

    Description

      MDBs deployed in on JBoss EAP 7.3.x utilising generic JMS resource adapter would fail to authenticate with external TIBCO broker due to missing password.

      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://aza: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)

      Authentication with TIBCO JNDI does works and JMS bridge would work only MDB are affected.

      This is due to missing getter() method on JMSActivationSpect class.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-14378 Generic JMS RA fails to authenticate

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-20935 [GSS](7.3.z) Upgrade generic jms from 2.0.8.Final-redhat-00001 to 2.0.9.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link Deployed MDBs utilising generic JMS resource adapter fail to authenticate

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: