4 Replies Latest reply on Jul 7, 2005 5:56 AM by Kamal Chandana

    Is it possible to use JMS to distribute processing

    Raymond Ong Newbie

      Hi,

      I have a typical JMS setup. A servlet sending messages to a JMS queue (using JBoss AS). Both are running on a single machine. A client (the message receiver) is running on the same machine do the the message processing.

      I plan to move my client into a second machine to distribute the processing. I also plan to use several machines that will run the same client. Will JMS be able to send to multiple machines running the same client? I plan to do this to distribute the processing to as many machines as possible. How will JMS know who to send when there are multiple instance of clients running on difference machines?

      -> client app
      Servlet -> Queue -> client app
      - client app
      -> client app

      Much like an MDB pool runing on an application server. only, i'd like my apps to run on different machines.

      Thanks in advance!

        • 1. Re: Is it possible to use JMS to distribute processing
          Ulf Schroeter Novice

          This is the intended usage model for JMS, so your design will work out of the box. Nevertheless don't stress your idea of processing distribution to multiple, multiple machines too much without prior propper testing of achievable performance gains.

          Regards
          Ulf

          • 2. Re: Is it possible to use JMS to distribute processing
            Raymond Ong Newbie

            I've read in a sun j2ee tutorial that distributed processing using multiple machines may be achieved by having a sender (client) connect to multiple JMS queues residing on remote machines. these remote machines can then host message driven beans (or a client applications) that receive the messages from the JMS queue.

            • 3. Re: Is it possible to use JMS to distribute processing
              Ulf Schroeter Novice

              Yes, using MDB is the 'design' pattern for parallel (multi-threaded) data processing within the J2EE environment. But keep in mind that message network data distibution to multiple machines also cause some performance penalties.

              So the general message is: do not distribute processing to multiple servers unless this is really needed. Especially do not distribute processing just because it's technically possible. And - as always in the context of performnce - detailed measurement is required to proof the general idea (more servers -> more performance).

              Regards
              Ulf

              • 4. Re: Is it possible to use JMS to distribute processing
                Kamal Chandana Newbie

                The distribution of processing is one of the advantages you gain when the client is not in the same machine.

                When multiple clients are running in multiple machines, there will be a problem for your response sender to decide the client that sent this particular request. Since JMS is asynchronous the server will not be able to memorize the request sender.

                One suggestion is to use some attrabutes by the client in the request message object informing the client IP. Then the server (JMS service) can decide the client to which the response has to be send.

                eg:

                StreamMessage streamMessage = session.createStreamMessage();
                streamMessage.setStringProperty("clientIP",192.168.1.25);


                Regards
                Kamal Chandana