Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Poornachandra Veluri (poorna18)
Evonsys
Senior Architect
Evonsys
IN
poorna18 Member since 2018 5 posts
Evonsys
Posted: May 29, 2019
Last activity: May 30, 2019
Posted: 29 May 2019 18:30 EDT
Last activity: 30 May 2019 8:59 EDT
Closed

Test Connectivity for JMS MDB using JNDI is failing after deployment of ejb-jar.xml

When I'm trying to do test connectivity, getting the following error

javax.naming.NamingException: Error getting WsnNameService properties [Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor code: E07 completed: No]

We added additional queue and Listener and generated deployment descriptor. We deployed the newly generated ejb-jar.xml and restarted the server. From that moment, we are getting test connectivity failed. Let me know if you have come across this and how to solve it. Thank you.

PEGA version- 7.1.7

Appserver - Websphere

To see attachments, please log in.
Data Integration

Posted: 5 years ago
Posted: 30 May 2019 8:59 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

Were your MDB started correctly without any errors? (check the Websphere log). You should not have to worry about test connectivity and MDB is processing inbound messages into the Websphere containers.

To see attachments, please log in.

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

Pega Collaboration Center 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