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

JNDI URL information does not get picked from the Transport rule

SA-9733

Summary


 

To get the "Test Connectivity" button working for SOAP over JMS, make sure to update the Service Endpoint URL in CONNECT SOAP rule to include the jndiURL.

For example:


jms:jndi:jms/pega_prpc_ReqQ


To:


jms:jndi:jms/pega_prpc_ReqQ?jndiURL=iiop://localhost:40645


The follow-on questions are raised by user:

1. Why the JNDI url information is not picked up from the Transport rule?

2. In the JMS URI scheme jndiURL is optional then why one must add jndiURL to get it working?

 

Resolution



Update service endpoint URL in CONNECT SOAP rule to "jms:jndi:jms/pega_prpc_ReqQ?jndiURL=iiop://localhost:40645" only to test connectivity functionality.

This is due to a bug in the logic used for Connect Soap test connectivity and is scheduled to be resolved in update release Pega 7.1.9.

You must note for runtime this Local-change is not required and it works as normal. 

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