Tibco EMS integration not working after enabling authorization

Solution Verified - Updated -

Issue

  • After enabling Tibco EMS authorization the resource adapter deployed in JBoss EAP stopped working with the following WARN message.
WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: java:jboss/exported/jms/QueueConnectionFactory java:/jms/XAQueueConnectionFactory: javax.resource.ResourceException: javax.resource.ResourceException: Unable to setup connection
        at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:195)
        at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:109)
        at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1327)
        at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.fillTo(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1139)
        at org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97)
        at java.lang.Thread.run(Thread.java:745)
Caused by: javax.resource.ResourceException: Unable to setup connection
        at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:710)
        at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:189)
        ... 5 more
Caused by: javax.naming.AuthenticationException: Not permitted: Failed to connect to any server at: tcp://192.168.1.2:1234, tcp://192.168.1.2:1234 [Error: authentication failed: url that returned this exception = tcp://192.168.1.2:1234 ] [Root exception is javax.jms.JMSSecurityException: Failed to connect to any server at: tcp://192.168.1.2:1234, tcp://192.168.1.2:1234 [Error: authentication failed: url that returned this exception = tcp://192.168.1.2:1234 ]]
        at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:670)
        at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:491)
        at javax.naming.InitialContext.lookup(InitialContext.java:417)
        at javax.naming.InitialContext.lookup(InitialContext.java:417)
        at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:669)
        ... 6 more
Caused by: javax.jms.JMSSecurityException: Failed to connect to any server at: tcp://192.168.1.2:1234, tcp://192.168.1.2:1234 [Error: authentication failed: url that returned this exception = tcp://192.168.1.2:1234 ]
        at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1458)
        at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4333)
        at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:39)
        at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:200)
        at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:253)
        at com.tibco.tibjms.TibjmsQueueConnectionFactory.createQueueConnection(TibjmsQueueConnectionFactory.java:89)
        at com.tibco.tibjms.naming.TibjmsContext$Messenger.request(TibjmsContext.java:325)
        at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:657)
        ... 10 more

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.1.x

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