7 Replies Latest reply on Oct 27, 2005 10:27 AM by tom.elrod
      • 1. Re: Is Remoting APR transport useful for Messaging?

        Probably. As it stands now, will be converting the http invokers within remoting to use the tomcat http connector. The http connector is able to use APR (but from remoting standpoint, will only be for http transport).

        We may add a direct APR transport within remoting (so use APR directly instead of on top of http), but this has been bumped down in priority.

        Note, if using APR (either via the http connector or directly), requires using native code (so will have to include the dll or so needed).

        • 2. Re: Is Remoting APR transport useful for Messaging?
          ovidiu.feodorov

           

          Note, if using APR (either via the http connector or directly), requires using native code (so will have to include the dll or so needed).


          If improvments in speed are noticeable, this is a price some would be willing to pay.



          • 3. Re: Is Remoting APR transport useful for Messaging?

            Ok. According to Mladen, will provide a marked improvement. Don't know exactly how much, but should be able to measure easily once integrated into remoting.

            • 4. Re: Is Remoting APR transport useful for Messaging?
              starksm64

              How much investigation into the pure java multiplexing version has been done so far?

              • 5. Re: Is Remoting APR transport useful for Messaging?

                Is done (in the 1.4.0 beta release). Working on performance for the final release, but is about 20% slower than regular socket transport now. Ron Sigal implemented this and implementation can be used directly outside of remoting.

                • 6. Re: Is Remoting APR transport useful for Messaging?
                  timfox

                  Sounds great.

                  Is it possible to combine a multiplex transport with an APR style (or NBIO) transport so we get small number of physical connections (I believe multiplex solves this problem??), but also avoid large number of server threads blocking on sockets in the server (I believe APR/NBIO solves this problem??)?

                  That would be very cool.

                  With APR, is the native code available for all the platforms JBossMessaging needs to run on? Could the same be done using Java NBIO and retain WORA?

                  Is native code something we would want to avoid in JBossMessaging?

                  Hmmm.... I'm not sure whether this is a messaging or remoting question any more :)

                  • 7. Re: Is Remoting APR transport useful for Messaging?

                    Direcct APR use within remoting is a ways off. Will need to build an abstraction layer first so anyone can use it via java interfaces (would take too long if code directly to the native API as it is now because have to keep up with native pointers in the java code and such).

                    Lets move this part of the discussion to the remoting forum and discuss as related to features for 1.6.0 release.