RA JMS agent is unable to run topic type JMS jobs.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

After upgrading the JMS Agent, the JMS agent is able to run queue type JMS jobs. However, when they run topic type JMS jobs with the same CONN object, it errors with "[Error: authentication failed: url that returned this exception = tcp://jmstest1:7222 ]".

Reproduction:

A. Create a JMS job
B. In the JMS Receiver tab, select a CONN object
C. Click 'Topic' and enter a job name
D. Save and Execute
Outcome: [Error: authentication failed: url that returned this exception = tcp://jmstest1:7222 ]

Environment

Release:
Component: ARAJMS

Cause

The authentication for topic-type jobs required a different protocol. This has been addressed in the 2.1 Agent. 

Resolution

The issue was found and fixed with RA.JMS 2.1.0 in RA JMS Solution NoWeb. The Package is available for download at the Automic-Support-Zone (https://support.automic.com).

Hotfix-Description: Connection to Tibco topic fails with authentication error For Tibco or any other JMS provider that supports the 2.0 specification, connection to the topic fails with an authentication error due to the username & password not being passed Workaround:Use the 'Queue' instead of the 'Topic' for now.