Question

8
Replies
1103
Views
Close popover
Onkar Yerawar (OnkarY33)
HCL
Onkar Yerawar
HCL
NL
OnkarY33 Member since 2013 17 posts
HCL
Posted: March 6, 2018
Last activity: April 10, 2018
Closed

Unable to fetch connection factory from JMS set up on Oracle weblogic

Hi,

I am trying to set up a JMS listener to read messages from a Oracle weblogic JMS queue. I was able to set up the JNDI server data instance but then I was expecting the Connection factory name field on the JMS Properties tab in the JMS listener instance will give me list of connection factories on the JMS but it does not. So I myself put the JNDI name of the queue in that field but when I do a test connectivity I get below exception. See the attached screenshot of the test connectivity of JMS Listener. The error message says couldn't resolve connection factory object but the connection factory does exist, I am attaching the screenshot from weblogic console which displays the connection factory.

Any help is much appreciated. Thanks & Regards!

PS - I have copied weblogic.jar, wlclient.jar, wl-j2ee-client.jar, wljmsclient.jar and wljmxclient.jar to /tomcat/webapps/prweb/WEB-INF/lib directory. I am trying this setup on my Pega personal edition(7.3.1)

2018-03-06 22:45:41,059 [ JMS-Thread-16] [ ] [ ] [ ] ( services.jms.JMSListener) ERROR JMS.MycoJMSListener admin.mortgagemutation - Caught NamingException in listener MycoJMSListener
javax.naming.NameNotFoundException: Exception in lookup.: `jms/MycoConnectionFactory' could not be found.
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:65) ~[wlclient.jar:12.2.1.3.0]
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:260) ~[wlclient.jar:12.2.1.3.0]
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:192) ~[wlclient.jar:12.2.1.3.0]
at javax.naming.InitialContext.lookup(InitialContext.java:417) ~[?:1.8.0_121]
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.initializeConnection(JMSListener.java:1033) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runPoller(JMSListener.java:758) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.run_(JMSListener.java:753) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:454) ~[printegrint.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java:72) ~[wlclient.jar:12.2.1.3.0]
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87) ~[wlclient.jar:12.2.1.3.0]
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:238) ~[wlclient.jar:12.2.1.3.0]
... 7 more

Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.