Question

2
Replies
486
Views
PunitS66 Member since 2015 3 posts
Accenture
Posted: 4 years ago
Last activity: 4 years ago
Closed

Connect JMS in Tomcat 6.0.37 via Resource Reference

I am trying to Connect-JMS to a tibco queue using a P2P connection. I have created following entries in:

1)   /prweb/WEB-INF/web.xml

 <resource-ref id="ResourceRef_11">
        <description>location of JMS Connection Queue</description>          
        <res-ref-name>jms/QueueConnectionFactory</res-ref-name>
        <res-type>javax.jms.QueueConnectionFactory</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>

2) /tomcat/Context.xml --> XXXXXXX mentioned below is replaced with the actual URL which is working fine with the Direct JNDI lookup in the JNDI Server Rule

<Resource name="jms/QueueConnectionFactory"
            auth="Container"
            type="javax.jms.QueueConnectionFactory"
            initialContextFactory="com.tibco.tibjms.naming.TibjmsInitialContextFactory"
            url="tcp://XXXXXXXX"
            username="admin"
            password="admin"
     />

3) /tomcat/conf/Server.xml

    <Resource name="jms/QueueConnectionFactory"
            auth="Container"
            type="com.tibco.tibjms.naming.TibjmsInitialContextFactory"
            factory="com.tibco.tibjms.naming.TibjmsInitialContextFactory"
            brokerurl="tcp://XXXXXX"
            username="admin"
            password="admin"
     />

4) In addition to above I have created a Connect JMS rule in Pega in which I am trying to do a Resource Reference look up as java:comp/env/jms/QueueConnectionFactory. I also tried to perform a lookup via '/jms/QueueConnectionFactory', but that too didn't worked.

This connection always throws an execption when I try to do a test connectivity via the Connect-JMS Rule.

JNDI lookup of JMS connection factory 'QueueConnectionFactory' failed: javax.naming.NameNotFoundException: Name QueueConnectionFactory is not bound in this Context

Alternatively, If i try to do the same via Direct JNDI Lookup and specify the same TCP url, username and password in the JNDI Server Rule, I am able to connect Successfully.

 

Data Integration System Administration
Moderation Team has archived post
Share this page LinkedIn