3 Replies Latest reply on Jul 27, 2004 7:12 PM by Adrian Brock

    Local JMS is gone??

    Tim McCune Novice

      I'm looking at upgrading from JBoss 3.2.3 to 3.2.5, and noticing that JMS has changed significantly. So I found the Wiki page and read this:

      "It is important to note that applications, which used to run in JBoss configuration "all" might have to be refactored. Since JBoss 3.2.4 the JMS server is deployed and running on exactly one node in the cluster, whereas in the past each node used to run an independent JMS server instance."

      Refactored? Howabout rewritten? Geez, guys, this is a HUGE change for a patch release. I also read this:

      "Applications should consider using JMS as a reliable means of exchanging messages in a distributed environment, rather than a general purpose low-latency event mechanism. For example when the problem at hand can be solved by implementing a strongly typed, in VM Observer/Observed pattern, the application should resolve to the best practices esablished by Java Swing, rather than JMS."

      I strongly disagree. I need the reliability and scalability of JMS. But I REALLY need to be able to make the decision in my app when and when not to send messages remotely to another server. The JMS configuration in 3.2.3, where you have the option to use either the local JMS server or the HA server was exactly what I needed, and then someone decided to take it away. You're leaving me with little option here than to basically rewrite JMS to ensure that my messages stay local.

      2 questions:
      1) Can you PLEASE change this back to the way it was in 3.2.3 and leave it up to the application whether or not to send messages to a local JMS server or an HA server?
      2) Is it possible in 3.2.5 to configure a local JMS server, in a clustered environment, to look like 3.2.3?

        • 1. Re: Local JMS is gone??
          Adrian Brock Master

           

          "javajedi" wrote:

          2 questions:
          1) Can you PLEASE change this back to the way it was in 3.2.3 and leave it up to the application whether or not to send messages to a local JMS server or an HA server?


          It is the deployer's responsibility not the application's, that is why resource-refs exist.
          If you've followed the j2ee recommendations no refactoring should be required.


          2) Is it possible in 3.2.5 to configure a local JMS server, in a clustered environment, to look like 3.2.3?


          You mean like server/default/deploy/jms
          rather than server/all/deploy-hasingleton/jms?

          • 2. Re: Local JMS is gone??
            Tim McCune Novice

             

            "It is the deployer's responsibility not the application's, that is why resource-refs exist.
            If you've followed the j2ee recommendations no refactoring should be required. "


            Ok, fine, then leave it up to the application deployer. As it stands, it's not even an option to choose a local JMS server because it is GONE.

            You mean like server/default/deploy/jms
            rather than server/all/deploy-hasingleton/jms


            Almost. I mean a server/all/deploy/jms that contains a local JMS server, with a way to get at it through HA. Basically, I want the exact same configuration that existed in 3.2.3.

            • 3. Re: Local JMS is gone??
              Adrian Brock Master

              You did not grok my response.

              We preconfigure the "all" configuration for HA, a good thing IMHO.
              Few people figured out how to do it in 3.2.3, no matter how many times it was explained,
              so we do it for you.

              HA does not exist in "default" there is no cluster. This is your "local" config.

              So... 3.2.5 has both configurations. Pick one.

              Just for total clarification (I'm sure you'll ask)
              if you don't want the jdbc state manager look at docs/examples/jms/file-state-service.xml

              volia we are back at 3.2.3, except with all these fixes/improvements
              http://jboss.org/index.html?module=bb&op=viewtopic&t=48419