2 Replies Latest reply on Jul 31, 2009 4:29 AM by saropani

    SMX4 - JBI Cluster with smx-bean endpoints

    saropani

      Hi,

       

      I have been trying to see how SMX4 clutering works. I could see the shipped example working on top of ServiceMix4 runtime.

       

      As I have ServiceMix bean bundles in my projects, I am trying to make them as clustered endpoints, but without success so far!

       

      I have one CXF-BC consumer and two simple smxbean-based-pojo services, Service1 and Service2. I have a main smx instance with activemq broker, smx-instance-1 with Service1 and smx-instance-2 with Service2. The idea is to,

       

        1. Using a soap-client, invoke the consumer,

        2. let that consumer in turn call smx bean Service1

        3. and as Service1 is registered as Clustered, clustering will dispatch that request to Service2 deployed in smx-instance-2.

       

      The flow is all ok, until those stpes. When there is a return expected from Service2, I don't seem to get anything!

       

      The questions I had is:

       

      Can the JBI Clustering allow a return from remote service...? If thats possible, what has to be done?

       

      Thanks a lot!

        • 1. Re: SMX4 - JBI Cluster with smx-bean endpoints
          ubhole

          Do you have any test case we can look into? This should have worked. also, can you attach activemq configuration file from you deploy folder? Basic clustering support is provided by JMS broker along with new FUSE ESB 4 clustering engine.

           

          Ulhas

          • 2. Re: SMX4 - JBI Cluster with smx-bean endpoints
            saropani

            Apolozies for the late reply!

             

            The activemq broker config I use is the same as the one shipped. I use the JMS.xml files from the NMR-Cluster example.

             

            Basically I take that example, and instead of camel and quartz config files, I have two servicemix-bean based POJOs. The jms.xml and cluster.xml files remain the same.

             

            Please note that I am running 4.0.0 version.