2 Replies Latest reply on Dec 16, 2011 3:34 PM by jcadam14

    Starting ESB without having all jms-providers online

    jcadam14
    jcadam14 Dec 5, 2011 5:08 PM

      I'm tasked with creating a test tool that can act as external endpoints to either receive or send messages through our ESB (version 4.9).  The nature of the test tool of course means that we should be able to test without having all the software subsystems up when the ESB comes up.  However, doing so throws "Caused by: java.net.ConnectException: Connection refused: connect" exceptions and my test.esb package never gets deployed. 

       

      Is there either a way to configure the ESB to ignore these exceptions so that it can load my package without having to have all the jms-providers up, or a change in my jboss-esb.xml (or somewhere else) to catch these exceptions and log or ignore them? Or is there a different approach that should be used?

       

      Appreciate any help provided, thanks!

      Jason

      • 1216 Views
      • Tags:
        • 1. Re: Starting ESB without having all jms-providers online
          jcadam14
          jcadam14 Dec 15, 2011 3:29 PM (in response to jcadam14)

          Since this doesn't seem possible, can someone point me to documentation on how to create JMS bridges or gateways in JBoss 6?  What I'm looking to do is when my application sends a message on Topic A, JBoss AS picks that up and sends it to a topic internal to the ESB.  From there, the ESB will process it as normal.  Having internal topics is the only way I can see making the ESB and the connecting software products "ignorant" of who is up or down at startup.

           

          Thanks for any help you can provide

          Jason

            • Actions
          • 2. Re: Starting ESB without having all jms-providers online
            jcadam14
            jcadam14 Dec 16, 2011 3:34 PM (in response to jcadam14)

            Unless I'm doing something wrong here, it also looks like our ESB configuration won't start  not only if a jms-provider isn't available, but also if any of our JMSRouter actions can't connect on startup.  Is this by design?  If so that seems like a fundamental flaw in the design.  Why should one failed connection cause an entire configuration to not be initialized?  Throwing an exception I could understand, but a complete failure of startup?

              • Actions