1 Reply Latest reply on May 14, 2003 4:14 PM by Adrian Brock

    WARN  [StatelessSessionContainer] No resource manager found

    Frank Griffin Novice

      I've set up a session bean in 3.0.4 and 3.0.7 to write a JMS message. When I try to deploy it, I get:

      21:05:09,795 INFO [JMSContainerInvoker] Started
      21:05:09,867 WARN [StatelessSessionContainer] No resource manager found for jms/QueueFactory

      Later on, if I try to use the bean, I get:

      21:16:14,544 ERROR [LogInterceptor] TransactionRolledbackException, causedBy:
      javax.ejb.EJBException: javax.naming.NameNotFoundException: QueueFactory not bound

      I've desk-checked this stuff till I'm blind. Obviously there is something I missed, but I need another set of eyes to find it. Can somebody help ? TIA...

      The JNDI name used by the bean to look up its connection factory is:

      java:comp/env/jms/QueueFactory


      The ejb-jar.xml corresponding fragment is:

      *******
      <resource-ref>
      <res-ref-name>jms/QueueFactory</res-ref-name>
      <res-type>javax.jms.QueueConnectionFactory</res-type>
      <res-auth>Container</res-auth>
      </resource-ref>

      <resource-env-ref>
      <resource-env-ref-name>jms/WDRequestRQDriverMessageBean</resource-env-ref-name>
      <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
      </resource-env-ref>

      **************


      The jboss.xml corresponding fragment is:

      ****************


      <ejb-name>WDRequestRQSessionBean</ejb-name>

      <resource-ref>
      <!--
      The <res-ref-name> value *must* match the <res-ref-name> in
      the <resource-ref> in the bean's ejb-jar.xml
      -->
      <res-ref-name>jms/QueueFactory</res-ref-name>
      <jndi-name>java:/JmsXA</jndi-name>
      </resource-ref>

      <resource-env-ref>
      <!--
      The <resource-env-ref-name> value *must* match the
      <resource-env-ref-name> in the <resource-env-ref> in the bean's
      ejb-jar.xml
      -->
      <resource-env-ref-name>jms/WDRequestRQDriverMessageBean</res-ref-name>
      <!--
      The <jndi-name> value *must* be composed of the lower-cased
      mbean name attribute "service" value, a slash, and the mbean
      name attribute "name" value from the jbossmq-*-service.xml
      file used to define the queue. The correct name will show
      up in the JBoss stdout when the service file is deployed, as
      ["name"] Bound to JNDI name "service"/"name"
      -->
      <jndi-name>queue/WDRequestRQDriverMessageBean</jndi-name>
      </resource-env-ref>


      **************

      and the *-service.xml file which defines the queue is:

      **************************



      <depends optional-attribute-name="DestinationManager">
      jboss.mq:service=DestinationManager




      *****************