April 4, 2015

Common Errors you encounter in SOAP over JMS protocol

HP UFT 12.01

In this post, we will see about the common errors you encounter in SOAP over JMS protocol in HP LoadRunner or JMeter.

Sanity checks:

Ensure that you have associated all the latest JARs in HP LoadRunner/Apache JMeter. You can get the relevant JARs from the development team or you can download it from

To associate JARs in HP LoadRunner, go to Replay > Runtime Settings or press F4 key, and then click on Advanced tab under JMS as shown below.

Runtime Settings in LoadRunner

Runtime Settings in LoadRunner

Enter the full path of JARs in Classpath text field with semicolon separated or you simply enter %CLASSPATH% and map the JARs in your computer’s environment variables.

Add JAR to Classpath in JMeter

Add JAR to Classpath in JMeter

To map the JARs in JMeter, click on Test Plan and click on Browse button to map all the JARs as shown below.

Most of the errors that you encounter during unit testing can be solved by mapping right set of JARs and mention right send/receive queue names in the HP LoadRunner or Apache JMeter.

Now we will see about the common errors:

  1. Error: Failed to send message with javax.naming.NameNotFoundException

This error can be solved easily. The common mistake that testers do is mapping the wrong queue name in the script. Check for the right queue and map it accordingly to the script.

  1. naming.InvalidNameException

You get javax.naming.InvalidNameException when the port number is invalid, you need to check for the correct port and append it in the set property name.

  1. naming.AuthenticationException

You get javax.naming.AuthenticationException error when the JMS username and password is incorrect. Please check for any extra spaces in the username/password. You can get the username from the TIBCO configuration as well.

  1. Incorrect Initial Context Factory

Always make sure that you select appropriate initial context factory details in the settings. E.g. by default you can select com.tibco.tibjms.naming.TibjmsInitialContextFactory from the dropdown as shown below.

Initial Context Factory Settings in LoadRunner

Initial Context Factory Settings in LoadRunner

About NaveenKumar Namachivayam

Hi there! is a passionate and experienced Performance Test Analyst based in Chicago, USA with skill sets in Manual Testing, Test Automation, Performance Testing, and Test Estimation. He loves to learn and experiment new trends and models in Software Testing. Please stop by at his personal blogs: Excel Blog, DealsBrook,, and Affiliate Insights blog and Software Testing Memes.

Leave a Reply

Your email address will not be published. Required fields are marked *