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

 Abhishek Dubey (AbhishekDubey)
HSBC

HSBC
IN
AbhishekDubey Member since 2013 1 post
HSBC
Posted: Aug 10, 2019
Last activity: Aug 13, 2019
Posted: 10 Aug 2019 8:27 EDT
Last activity: 13 Aug 2019 7:20 EDT
Closed

Unable to connect to SOLACE from Connect-JMS rule

Need to connect Pega Application to Solace queue.
Imported resource adapter (RAR file provided from Solace) on WebSphere Application Server.
JMS resources Connection Factory and Queue are configured on WebSphere Application Server.

a) Tried Direct JNDI lookup in connect-JMS rule getting following error

JNDI lookup of JMS connection factory 'JNDI/J2C/CF' failed: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NoClassDefFoundError: com.solacesystems.jndi.SolJNDIInitialContextFactory (initialization failure)]

b) Tried Resource Reference (JMS resources are added in ejb-jar.xml and ibm-ejb-jar-bnd.xmi) in connect-JMS rule getting following error

JNDI lookup of JMS connection factory 'java:comp/env/JNDI/J2C/CF' failed: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.ExceptionInInitializerError]]

please guide me in resolving the issue?

To see attachments, please log in.
Data Integration

Posted: 5 years ago
Posted: 10 Aug 2019 12:22 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

In general, Pega relies on the underlying app server to provide the JMS functionality. I hope you are not importing the Solace jar files into the Pega database, that will most certainly cause class conflict (if yes, remove those jars from the db - pr_engineclasses table under rules schema). Is this the guide (or something similar) you are following in integrating WAS with Solace: https://solacelabs.github.io/solace-integration-guides/websphere-app-server/

To see attachments, please log in.
Posted: 5 years ago
Posted: 13 Aug 2019 7:20 EDT
Abhishek Dubey (AbhishekDubey)
HSBC

HSBC
IN

Thanks Kevin,

We have tried to setup shared library for Solace jar on WebSphere Application Server but it is giving error and Connection factory lookup failed.

We have imported Solace jar into Pega DB and now we are able to send messages to Solace queue.

 

 

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