3 Replies Latest reply on Jun 4, 2007 9:01 AM by jaikiran pai

    message driven bean error

    subrat jyetki Newbie

      hi
      i need a little help
      i have a mdb called as ExportRequestProcessorBean
      i want to deply this on jboss
      i am having ejb-jar.xml as

      <message-driven>
      <ejb-name>net.vertical.sa.web.export.ExportRequestProcessorBean</ejb-name>
      <ejb-class>net.vertical.sa.web.export.ExportRequestProcessorBean</ejb-class>
      <transaction-type>Container</transaction-type>
      <message-driven-destination>
      <destination-type>
      javax.jms.Topic
      </destination-type>
      </message-driven-destination>
      </message-driven>
      <container-transaction>

      <ejb-name>net.vertical.sa.web.export.ExportRequestProcessorBean</ejb-name>
      <method-name>*</method-name>

      <trans-attribute>Required</trans-attribute>
      </container-transaction>


      and jboss.xml as


      <message-driven>
      <ejb-name>net.vertical.sa.web.export.ExportRequestProcessorBean</ejb-name>
      <destination-jndi-name>WebRuleExportTopic</destination-jndi-name>
      </message-driven>


      still i am getting error as


      23:26:46,068 WARN [JMSContainerInvoker] destination not found: topic/WebRuleImportTopic reason: javax.naming.NameNotFoundExc
      eption: WebRuleImportTopic not bound

        • 1. Re: message driven bean error
          jaikiran pai Master

           

          <destination-jndi-name>WebRuleExportTopic</destination-jndi-name>


          23:26:46,068 WARN [JMSContainerInvoker] destination not found: topic/WebRuleImportTopic reason: javax.naming.NameNotFoundExc
          eption: WebRuleImportTopic not bound


          We need more details:

          1) When does this WARN message come up? Is it during deploying the application? Is there any exception stacktrace that you can post?

          2) Also note that your MDB is pointing to the WebRuleExportTopic topic whereas the NamenotFoundException mentions WebRuleImportTopic - which means either there's a typo in your post or you havent configured the MDB/topic correctly.

          3) Have you configured your topic. This is usually done in the jbossmq-destinations-service.xml file present under %JBOSS_HOME%/server/default/deploy/jms folder. If you havent configured it and if there's a MDB that is listening on a non-existent topic/queue, JBoss creates a temporary queue/topic for you when the application is being deployed.



          • 2. Re: message driven bean error
            subrat jyetki Newbie

            your 3rd option is correct but how to do it in

            • 3. Re: message driven bean error
              jaikiran pai Master

              Here's a very simple topic configuration:

              <mbean code="org.jboss.mq.server.jmx.Topic"
               name="jboss.mq.destination:service=Topic,name=YourTopicName">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
              
               </mbean>
              


              Replace the "YourTopicName" above with whatever is the name of your topic. Add the above mbean configuration to the already existing list of topic/queue in jbossmq-destinations-service.xml file present under %JBOSS_HOME%/server/default/deploy/jms folder