JMS5007: Illegal connection factory access

Question

Hi,
I'm getting this warning when my MDB is creating a connection to a queue to start consuming messages (onMessage method). The application works, but I'd like to know what this message really means and how to avoid it:
JMS5007: Illegal connection factory access to [jms/InteractionTrackerQCF]. J2EE Components should access JMS Connection Factories through a resource-ref in java:comp/env
My ejb-jar.xml is as follow:
<ejb-jar>
<display-name>InteractionTrackerJAR</display-name>
<enterprise-beans>
<message-driven>
<display-name>InteractionTrackerEJB</display-name>
<ejb-name>InteractionTrackerEJB</ejb-name>
<ejb-class>com.xxxxxx.InteractionTrackerBean</ejb-class>
<transaction-type>Bean</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
<resource-ref>
<res-ref-name>jms/InteractionTrackerQCF</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms/InteractionTracker</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
</enterprise-beans>
</ejb-jar>
and my sun-ejb-jar.xml is
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>InteractionTrackerEJB</ejb-name>
<jndi-name>jms/InteractionTracker</jndi-name>
<resource-ref>
<res-ref-name>jms/InteractionTrackerQCF</res-ref-name>
<jndi-name>jms/InteractionTrackerQCF</jndi-name>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms/InteractionTracker</resource-env-ref-name>
<jndi-name>jms/InteractionTracker</jndi-name>
</resource-env-ref>
<mdb-connection-factory>
<jndi-name>jms/InteractionTrackerQCF</jndi-name>
</mdb-connection-factory>
<jms-max-messages-load>1</jms-max-messages-load>
<is-read-only-bean>false</is-read-only-bean>
<gen-classes />
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In my application server instance, I've created a Connection Factory entry and a Destination Resource with the correct jndi names (and the imqDestinationName property).
Does anyone know how to resolve this problem?
Thanks
miki

Answer 1

Hi Isa,
thanks a lot for your reply. I've tried to change the way I'm looking up for things in the jndi context but I had no success.
If I update the client code, that's the code that creates the messages and I put the complete java:comp/env/jms/InteractionTrackerQCF and java:comp/env/jms/InteractionTracker I get an exception (javax.naming.NameNotFoundException: No object bound to name java:comp/env/jms/InteractionTrackerQCF)
If I update the ejb deployment descritptor to use java:comp/env/jms/InteractionTracker as <jndi-name> element of the <mdb-connection-factory> tag I get the following exception:
javax.naming.NamingException: invocation exception
at com.sun.enterprise.naming.NamingManagerImpl.getComponentId(NamingMana
gerImpl.java:990)
at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.
java:789)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
ava:107)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sun.ejb.containers.MessageBeanHelperBase.checkConnectionFactoryOb
ject(MessageBeanHelperBase.java:490)
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperB
ase.java:374)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContain
er.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Container
FactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:34
5)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:
81)
at com.iplanet.ias.server.AbstractManager.load(AbstractManager.java:134)
at com.iplanet.ias.server.ApplicationLifecycle.onStartup(ApplicationLife
cycle.java:147)
at com.iplanet.ias.server.ApplicationServer.onStartup(ApplicationServer.
java:269)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:162)
Any other idea on what I can do about this?
Thanks
miki