3 Replies Latest reply on Feb 4, 2009 9:51 AM by Yong Hao Gao

    Bridge Deployment Failures: queue not bound on AS startup, r

    Ross Nicholson Apprentice

      If I start jboss AS 5, my bridge will not deploy as it would appear that the local queue is created after the attempt to start the bridge. If I then touch the bridge configuration once jboss has started, the bridge starts ok (In this case the remote node is up and running). Is there some way I can make the bridge deployment be dependent on the local queue being active?

      2009-02-04 13:50:20,790 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      jboss.messaging:name=TestBridge,service=Bridge -> javax.naming.NameNotFoundException: queue not bound
      


      The other problem I have is that if the remote node is not running when I deploy the bridge after startup, deployment fails and so the bridge never starts. Surely the bridge should start regardless of the state of the other node, and connect when the node becomes available?

      My bridge configuration is as follows:

      <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=JMSProvider</depends>
       <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends>
      
       <attribute name="SourceDestinationLookup">/queue/speQueue</attribute>
       <attribute name="TargetDestinationLookup">/queue/speQueueEnd</attribute>
       <attribute name="QualityOfServiceMode">2</attribute>
       <attribute name="MaxBatchSize">1</attribute>
       <attribute name="MaxBatchTime">-1</attribute>
       <attribute name="FailureRetryInterval">5000</attribute>
       <attribute name="MaxRetries">-1</attribute>
       <attribute name="AddMessageIDInHeader">false</attribute>
      </mbean>
      


      Once the bridge is up and running everything is fine. The remote node can appear/disappear all it wants and the bridge delivers messages everytime the remote node becomes available.

      Any help appreciated, thanks

      Ross