Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SOAP JMS Endpoint URL gives configurationException

SA-8475

Summary



While configuring Connect-SOAP rule to generate a SOAP message and sending it using JMS via a JMS Transport rule received error.

Error Messages



The stacktrace in the logfile is shown below:

JMS: RULE-CONNECT-SOAP RULENAME  JNDI lookup of JMS destination 'jndi:jms/JMSQ ' failed: javax.naming.ConfigurationException: NamingManager.getURLContext cannot find the factory for this scheme: jndi
javax.naming.ConfigurationException: NamingManager.getURLContext cannot find the factory for this scheme: jndi
at com.ibm.ws.naming.jndicos.CNContextImpl.checkForUrlContext(CNContextImpl.java:480)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:161)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:180)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at com.pegarules.generated.activity.ra_action_validateinfrastructureconnectjms_dbbcea0efbe598bf5c1dd4d1acd44bab.step2_circum0(ra_action_validateinfrastructureconnectjms_dbbcea0efbe598bf5c1dd4d1acd44bab.java:663)
at com.pegarules.generated.activity.ra_action_validateinfrastructureconnectjms_dbbcea0efbe598bf5c1dd4d1acd44bab.perform(ra_action_validateinfrastructureconnectjms_dbbcea0efbe598bf5c1dd4d1acd44bab.java:95)


Steps to Reproduce



1- Create Connect-SOAP rule.
2- Create JMS-Transport rule.
3- Make sure "jms/
JMSQ" is configured as a JNDI entry in WAS 7.0 JNDI Registry.
4- Use the "TEST Connection" button on the SOAP rule to test the setup.

The error message appears
.


Root Cause



The root cause of this problem is software use/operation error. 

As per initial investigation it is observed that configuration defined in WAS7.0 does not seem to match with configuration used in Connect rule.
 

Resolution



The SOAP JMS enpoint URL works using the following destination configuration: 

 jms:jndi:jms/imit_pega_prpc_JMSQ?jndiURL=iiop://localhost:port_no 

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us