4 Replies Latest reply on Sep 10, 2008 3:32 PM by Samuel Doyle

    HAJNDIJMSProvider mbean not installed

    Shailesh P Newbie

      HiI am using Jboss messaging bridge. I am getting following exception when server is started:

      -jasre/jboss-4.0.5.GA/server/all/deploy/vertice-ear-0.0.5.30-SNAPSHOT.ear
      11:26:11,962 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.messaging:service=Bridge,name=TestBridge
      State: CONFIGURED
      I Depend On:
      jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider
      jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider
      State: NOTYETINSTALLED
      Depends On Me:
      jboss.messaging:service=Bridge,name=TestBridge



      The source for the bridge is Tibco Topic and target is Queue. I have used JmsXA connetion factory for source Queue. Not sure why the above error is coming. Any suggestions will be really helpful.

      Thanks in advance.

        • 1. Re: HAJNDIJMSProvider mbean not installed
          Shailesh P Newbie

          I am using jboss-4.0.5.GA. I have placed jboss-messaging.jar(1.3.0.GA) in server lib.
          Here are the configurations that I have done:

          Added tibco-bridge-service.xml to server\all\deploy-hasingleton\jms folder.
          It looks as follows:

          
          <server>
           <mbean code="org.jboss.jms.server.bridge.BridgeService"
           name="jboss.messaging:service=Bridge,name=TestBridge"
           xmbean-dd="xmdesc/Bridge-xmbean.xml">
           <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider</depends>
           <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider</depends>
           <attribute name="SourceDestinationLookup">TopicName</attribute>
           <attribute name="TargetDestinationLookup">queue/testQueue</attribute>
           <attribute name="SourceUsername">userName</attribute>
           <attribute name="SourcePassword">password</attribute>
           <attribute name="QualityOfServiceMode">2</attribute>
           <attribute name="MaxBatchSize">5</attribute>
           <attribute name="MaxBatchTime">-1</attribute>
           <attribute name="SubName">Test</attribute>
           <!--attribute name="ClientID">myClientID</attribute-->
           <attribute name="FailureRetryInterval">5000</attribute>
           <attribute name="MaxRetries">-1</attribute>
           </mbean>
          </server>
          
          


          The target queue - queue/testQueue is the one which is by default in server\all\deploy-hasingleton\jms\jbossmq-destinations-service.xml file.

          The server\all\deploy\jms\hajndi-jms-ds.xml contains the following:

          <!-- Tibco JMS Provider -->
          <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider">
           <attribute name="ProviderName">TibcoJMSProvider</attribute>
           <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
           <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
           <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
           <attribute name="Properties">
           java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
           java.naming.provider.url=ldap://abc.xyz
           </attribute>
          </mbean>
          
          <!-- The JMS provider loader -->
          <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
           name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
           <attribute name="ProviderName">DefaultJMSProvider</attribute>
           <attribute name="ProviderAdapterClass">
           org.jboss.jms.jndi.JNDIProviderAdapter
           </attribute>
           <attribute name="FactoryRef">XAConnectionFactory</attribute>
           <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
           <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
           <attribute name="Properties">
           java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
           java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
           java.naming.provider.url=172.18.236.228:1100
           jnp.disableDiscovery=false
           jnp.partitionName=${jboss.partition.name:DefaultPartition}
           jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
           jnp.discoveryPort=1102
           jnp.discoveryTTL=16
           jnp.discoveryTimeout=5000
           jnp.maxRetries=1
           </attribute>
          </mbean>
          
          


          Please let me know where I am going wrong.

          • 2. Re: HAJNDIJMSProvider mbean not installed
            Shailesh P Newbie

             

            "shaileshhp" wrote:
            I am using jboss-4.0.5.GA. I have placed jboss-messaging.jar(1.3.0.GA) in server lib.
            Here are the configurations that I have done:

            Added tibco-bridge-service.xml to server\all\deploy-hasingleton\jms folder.
            It looks as follows:

            
            <server>
             <mbean code="org.jboss.jms.server.bridge.BridgeService"
             name="jboss.messaging:service=Bridge,name=TestBridge"
             xmbean-dd="xmdesc/Bridge-xmbean.xml">
             <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider</depends>
             <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider</depends>
             <attribute name="SourceDestinationLookup">TopicName</attribute>
             <attribute name="TargetDestinationLookup">queue/testQueue</attribute>
             <attribute name="SourceUsername">userName</attribute>
             <attribute name="SourcePassword">password</attribute>
             <attribute name="QualityOfServiceMode">2</attribute>
             <attribute name="MaxBatchSize">5</attribute>
             <attribute name="MaxBatchTime">-1</attribute>
             <attribute name="SubName">Test</attribute>
             <!--attribute name="ClientID">myClientID</attribute-->
             <attribute name="FailureRetryInterval">5000</attribute>
             <attribute name="MaxRetries">-1</attribute>
             </mbean>
            </server>
            
            


            The target queue - queue/testQueue is the one which is by default in server\all\deploy-hasingleton\jms\jbossmq-destinations-service.xml file.

            The server\all\deploy\jms\hajndi-jms-ds.xml contains the following:

            <!-- Tibco JMS Provider -->
            <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=TibJMSProvider">
             <attribute name="ProviderName">TibcoJMSProvider</attribute>
             <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
             <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
             <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
             <attribute name="Properties">
             java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
             java.naming.provider.url=ldap://abc.xyz
             </attribute>
            </mbean>
            
            <!-- The JMS provider loader -->
            <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
             name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
             <attribute name="ProviderName">DefaultJMSProvider</attribute>
             <attribute name="ProviderAdapterClass">
             org.jboss.jms.jndi.JNDIProviderAdapter
             </attribute>
             <attribute name="FactoryRef">XAConnectionFactory</attribute>
             <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
             <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
             <attribute name="Properties">
             java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
             java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
             java.naming.provider.url=localhost:1100
             jnp.disableDiscovery=false
             jnp.partitionName=${jboss.partition.name:DefaultPartition}
             jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
             jnp.discoveryPort=1102
             jnp.discoveryTTL=16
             jnp.discoveryTimeout=5000
             jnp.maxRetries=1
             </attribute>
            </mbean>
            
            


            Please let me know where I am going wrong.


            • 3. Re: HAJNDIJMSProvider mbean not installed
              Adrian Brock Master

              This is not the JBoss Messaging Forum

              • 4. Re: HAJNDIJMSProvider mbean not installed
                Samuel Doyle Apprentice

                Did you ever get an answer for this question? I know this isn't the JBoss Messaging forum but I'm seeing the same issue as well.