Performancing Metrics

Vamsi Tokala's blog: Common Error Messages while sending SOAP over JMS

Wednesday, December 16, 2009

Common Error Messages while sending SOAP over JMS

I have collated some common error messages which may occur while sending SOAP over JMS messages through LoadRunner or any other performance testing tools.

1. You may get the following error if the class path (of your Proprietary Providers like Tibco/MQ etc) is not properly set under VuGen – Runtime settings –JMS (OR) if you have issues with JDK installation

javax.naming.NoInitialContextException: Cannot instantiate class: com.tibco.tibjms.naming.TibjmsInitialContextFactory [Root exception is java.lang.ClassNotFoundException: com.tibco.tibjms.naming.TibjmsInitialContextFactory]

2. You may also get the following exception if the JNDI context factory details entered if incorrect

javax.naming.NameNotFoundException: Name not found: ConnectionFactory1'

Action.c(29): Error: Failed to send message SAP6407051894Y000000000030765077Y to queue.sample due to the following exception : javax.naming.ConfigurationException: Server name is missing from provider URL of naming service
javax.naming.ConfigurationException: Server name is missing from provider URL of naming service

3. You may get the following error if java.naming.provider.url is incorrect
javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://tibq1.xxx.com:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://tibq1.xxx.com:7222]

No comments: