4 Replies Latest reply on Jun 20, 2010 5:09 AM by Tim Fox

    JDK 1.5 clients

    Clebert Suconic Master

      We have had a few requests for being able to run JDK 1.5 clients.

       

      We had an user saying he could run the client allright as soon as the set javac.target = 1.5..

       

       

      I just looked at HornetQConcurrentLinkedQueue, and it seems it is being used at ClientConsumer. (At least Eclipse tells me HornetQConsumerLinedQueue is used by PriorityLinkedListImpl which is used by the ClientConsumer.  (unless I'm missing something).

       

       

      Isn't there a version of the class we need outside of the JDK 1.6? that would make our lifes easier on supporting 1.5.

       

       

      I remember on that thread (where we decided about 1.6) that we would still support 1.5 on clients. say You're McDonalds.. it would be hard to upgrade the runtime in all the X thousand stores.... I guess it would be best to support 1.5 on clients at least.

        • 1. Re: JDK 1.5 clients
          Leos Bitto Novice

          Clebert Suconic wrote:

           

          I just looked at HornetQConcurrentLinkedQueue, and it seems it is being used at ClientConsumer. (At least Eclipse tells me HornetQConsumerLinedQueue is used by PriorityLinkedListImpl which is used by the ClientConsumer.  (unless I'm missing something).

           

          Isn't there a version of the class we need outside of the JDK 1.6? that would make our lifes easier on supporting 1.5.

           

           

          It seems to me that in HornetQConcurrentLinkedQueue it is only the method lazySet of AtomicReferenceFieldUpdater which prevents it to be used with Java 5. Maybe that lazySet could be omitted (replaced with a direct access to the volatile field) with only a negligable performance penalty? Check the attached patch.

          • 2. Re: JDK 1.5 clients
            Tim Fox Master

            The issue here is not technical, producing a Java 5 client would be simple.

             

            The issue is on product policy - whether EAP will accept and support a Java 5 client. Currently EAP 5+ is Java 6 only.

            • 3. Re: JDK 1.5 clients
              Leos Bitto Novice

              Tim Fox wrote:

               

              The issue here is not technical, producing a Java 5 client would be simple.

               

              The issue is on product policy - whether EAP will accept and support a Java 5 client. Currently EAP 5+ is Java 6 only.

               

              This brings another question regarding the product policy: Will it be possible to buy support for running HornetQ standalone, without EAP? There are situations where messaging provider is all that is needed, without (the need to pay for) the whole EAP...

              • 4. Re: JDK 1.5 clients
                Tim Fox Master

                Leos Bitto wrote:

                 

                Tim Fox wrote:

                 

                The issue here is not technical, producing a Java 5 client would be simple.

                 

                The issue is on product policy - whether EAP will accept and support a Java 5 client. Currently EAP 5+ is Java 6 only.

                 

                This brings another question regarding the product policy: Will it be possible to buy support for running HornetQ standalone, without EAP? There are situations where messaging provider is all that is needed, without (the need to pay for) the whole EAP...

                The million dollar question

                 

                I quite agree we need HornetQ to be supported standalone. But these kinds of decisions are not mine to make.