6 Replies Latest reply on Jan 10, 2005 9:21 AM by chenna1978

    DefaultJMSProvider not bound

    chenna1978

      Hi,

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

      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. Re: DefaultJMSProvider not bound
          chenna1978

          HI,

          We are using Jboss-3.2.1 and EJB 2.0

          Thanks.

          • 2. Re: DefaultJMSProvider not bound
            hariv

            We have used message beans in JBOSS3.2.3. There should be a file jms-ds.xml under the deploy/jms directory. This file defines the DefaultJMSProvider. I am not sure whether it is different in JBOSS3.2.1

            • 3. Re: DefaultJMSProvider not bound
              chenna1978

              Hi Hari,

              We are using jboss-3.2.1 and this also have jms-ds.xml under deploy/jms directory. The file defines the DefaultJMSProvider. Eventhought it is defined in jms-ds.xml i am gettint that error. Why is not recognizing DefaultJMSProvider from jms-ds.xml.
              Any help on this.

              Thanks.

              • 4. Re: DefaultJMSProvider not bound
                hariv

                Did you check when jboss starts up; is there any error while trying to bind DefaultJMSProvider. Look at the jndi view.
                http://<server_name>:<8080>/jmx-console and check whether DefaultJMSProvider is listed.

                The following is the sample jms-ds.xml I have in jboss-3.2.3

                <?xml version="1.0" encoding="UTF-8"?>

                <connection-factories>

                <!-- ==================================================================== -->
                <!-- JMS Stuff -->
                <!-- ==================================================================== -->

                <!-- The JMS provider loader -->

                DefaultJMSProvider

                org.jboss.jms.jndi.JBossMQProvider

                java:/XAConnectionFactory
                JMSFactory


                <!-- The server session pool for Message Driven Beans -->

                <depends optional-attribute-name="XidFactory">jboss:service=XidFactory
                StdJMSPool

                org.jboss.jms.asf.StdServerSessionPoolFactory



                <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->

                <tx-connection-factory>

                <jndi-name>JmsXA</jndi-name>

                <xa-transaction/>

                <adapter-display-name>JMS Adapter</adapter-display-name>

                <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>

                <security-domain-and-application>JmsXARealm</security-domain-and-application>

                </tx-connection-factory>

                </connection-factories>


                • 5. Re: DefaultJMSProvider not bound
                  chenna1978

                  Hi Hari,

                  I didn't see any error in jmx-console.

                  I can the following under jmx-console

                  jboss.mq
                  name=JMSProvider,service=JMSProviderLoader
                  name=StdJMSPool,service=ServerSessionPoolMBean
                  service=InvocationLayer,type=HTTP
                  service=Invoker
                  service=SecurityManager
                  service=TracingInterceptor

                  I click on the above link name=JMSProvider,service=JMSProviderLoader I am getting the follwoing.

                  MBean View
                  MBean Name: Domain Name: jboss.mq
                  service: JMSProviderLoader
                  name: JMSProvider
                  MBean Java Class: org.jboss.jms.jndi.JMSProviderLoader

                  Back to Agent View Refresh MBean View
                  --------------------------------------------------------------------------------

                  MBean description:
                  Management Bean.
                  --------------------------------------------------------------------------------

                  List of MBean attributes:
                  Name Type Access Value Description
                  ProviderUrl java.lang.String RW MBean Attribute.
                  StateString java.lang.String R Failed MBean Attribute.
                  AdapterJNDIName java.lang.String RW MBean Attribute.
                  State int R 4 MBean Attribute.
                  ProviderAdapterClass java.lang.String RW MBean Attribute.
                  TopicFactoryRef java.lang.String RW MBean Attribute.
                  ProviderName java.lang.String RW MBean Attribute.
                  QueueFactoryRef java.lang.String RW MBean Attribute.
                  Name java.lang.String R DefaultJMSProvider MBean Attribute.


                  --------------------------------------------------------------------------------

                  List of MBean operations:

                  --------------------------------------------------------------------------------

                  void start()
                  MBean Operation.

                  --------------------------------------------------------------------------------

                  void create()
                  MBean Operation.


                  I dd

                  • 6. 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.