In this post, we will see about the common errors you encounter in SOAP over JMS protocol in HP LoadRunner or JMeter.
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 http://www.findjar.com/index.x
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.
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.
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:
- 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.
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.
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.
- 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.