4 Replies Latest reply on Jan 10, 2005 9:22 AM by chenna1978

    DefaultJMSProvider not bound

    chenna1978

      Hi,

      I saw on google search about this problem. No one has solution to this.

      We are using Jboss-3.2.1 and EJB 2.0

      I am trying to deploy Message driven bean into Jboss-3.2.1 server and getting the following error.
      Can any one help me why I am getting this error?


      WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=local/SampleMDB,service=EJB


      javax.naming.NameNotFoundException: DefaultJMSProvider not bound

      ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'


      org.jboss.deployment.DeploymentInfo@e9a284c4 { url=file:/C:/jboss-3.2.1/server/default/deploy/jms/jbossmq-destinations-service.xml }
      deployer: org.jboss.deployment.SARDeployer@1d2b01b
      status: Deployment FAILED reason: create operation failed for package file:/C:/jboss-3.2.1/server/default/deploy/jms/jbossmq-destinations-service.xml; - nested throwable: (org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:service=Queue,name=testQueue)
      state: FAILED
      watch: file:/C:/jboss-3.2.1/server/default/deploy/jms/jbossmq-destinations-service.xml




      Depends On Me: jboss.mq:service=DestinationManager
      , ObjectName: jboss.mq.destination:service=Queue,name=DLQ
      state: CONFIGURED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      Depends On Me: , ObjectName: jboss.j2ee:jndiName=local/SampleMDB,service=EJB
      state: FAILED
      I Depend On:
      Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound]


      Here is the XML code I am using to deploy MDB.

      ejb-jar.xml code:
      *********************
      <enterprise-beans>
      <message-driven>
      <ejb-name>SampleMDB</ejb-name>
      <ejb-class>ejb.mdb.SampleMDB</ejb-class>
      <messaging-type>javax.jms.MessageListener</messaging-type>
      <transaction-type>Container</transaction-type>
      <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
      <message-driven-destination>
      <destination-type>javax.jms.Queue</destination-type>
      </message-driven-destination>
      </message-driven>
      </enterprise-beans>


      <method-permission>


      <ejb-name>SampleMDB</ejb-name>
      <method-name>*</method-name>

      </method-permission>

      <container-transaction>


      <ejb-name>SampleMDB</ejb-name>
      <method-name>*</method-name>

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


      jboss.xml code:
      **************

      <enterprise-beans>
      <message-driven>
      <ejb-name>SampleMDB</ejb-name>
      <configuration-name>Standard Message Driven Bean</configuration-name>
      <destination-jndi-name>queue/testQueue</destination-jndi-name>
      </message-driven>
      </enterprise-beans>

      jbossmq-destinations-service.xml
      *********************************


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


      Thanks.

        • 1. 3773989

          where do you find code conventions for Jboss? I know there used to be a link on the site but I can't seem to find it.

          • 2. Re: DefaultJMSProvider not bound
            genman


            Can you use a newer version of JBoss, like from the last six months? And usually there are gems of information earlier in the log that explain things that users like you tend to ignore. (Hint: There's something keeping DefaultJMSProvider from being deployed.)

            • 3. Re: DefaultJMSProvider not bound
              chenna1978

              Hi genmen,

              We are using jboss-3.2.1 on our production server. It is not easy to update the server. We have to do lot of configuration settings to work newer version of Jboss. What is the problem with Jboss-3.2.1? Why do I need to go higher verison of Jboss?

              Thanks.

              • 4. Re: DefaultJMSProvider not bound
                chenna1978

                Thanks for all ur response.
                I am able to deploy MDB and run after I re-install Jboss-3.2.1

                Thanks.