ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Active MQ connectivity is not working in VSM
Article ID: 104097
Updated On:
Products
CA Application Test
CA Continuous Application Insight (PathFinder)
Issue/Introduction
We have imported Active MQ jar files and deployed in hot deploy. Still, the VSM is not able to connect.
Using the deprecated listen step as part of a VS we could see an error in inspection view:
Exception Executing Messaging/ESB Step: javax.naming.NameNotFoundException: abc.request
abc.request is the name of the JMS queue that was used in the step. It appears that this message is coming back from the ActiveMQ server.
There are no errors that there is a problem connecting or that there is a problem with the authorization of the userid.
Using the deprecated listen step as part of a VS we could see an error in inspection view:
Exception Executing Messaging/ESB Step: javax.naming.NameNotFoundException: abc.request
abc.request is the name of the JMS queue that was used in the step. It appears that this message is coming back from the ActiveMQ server.
There are no errors that there is a problem connecting or that there is a problem with the authorization of the userid.
Environment
DevTest on release 10.2 and Apache ActiveMQ 5.15
Resolution
After setting up the assets and using the new JMS Send Receive step in a test, the test could both send and receive a message.
The same assets can be used in configuring a Virtual Service.
Use the new steps (not deprecated) and test the assets in a test case first, using the JMS Send Receive step.
The same assets can be used in configuring a Virtual Service.
Use the new steps (not deprecated) and test the assets in a test case first, using the JMS Send Receive step.
Feedback
Yes
No
Powered by
