5 Replies Latest reply on Jul 6, 2015 12:49 AM by jaikiran

    Wildfly 9.0 CR2 EJB client compression no longer working

    spittel

      Hello,

       

      I've been testing Wildfly 9 CR1 for ejb compression (with compression hints and org.jboss.ejb.client.view.annotation.scan.enabled System property set) and it was working fine.

       

      On changing to CR2 I'm no longer getting compression (tested with Wireshark).

       

      Is this a known bug, or is there an additional flag I have to set?

       

      Thanks for any help.

        • 1. Re: Wildfly 9.0 CR2 EJB client compression no longer working
          jaikiran

          Do you have relevant code/application to reproduce this?

          • 2. Re: Wildfly 9.0 CR2 EJB client compression no longer working
            spittel

            Hi Jaikiran,

             

            Any call on an EJB while listening with Wireshark will show that the request and response is not being compressed (it's clear readable text). This is a class level @CompressionHint annotation, with no method level compression hints.

             

            Looking at org.jboss.as.test.integration.ejb.compression.CompressionTestCase it seems it's not checking if compression is actually happening.


            Do you have a suggestion on how I can set up a proper test case that doesn't involve me staring very intently at wireshark captures (horribly prone to human error)?


            Thanks for any pointers or help you can send my way.


            Cheers,


            Jason

            • 3. Re: Wildfly 9.0 CR2 EJB client compression no longer working
              jaikiran

              It's fine if you don't have the wireshark captures. Just attaching the client code and the server side EJB code (binary and source code) which can be quickly run for someone to reproduce this, is fine. There are different ways, one can verify if the data is being compressed or not, so just the client and server side of this application will help.

              • 4. Re: Wildfly 9.0 CR2 EJB client compression no longer working
                spittel

                Hi Jaikiran,

                 

                My tests were faulty.  The app is a thick Swing client hitting EJBs on the server. And I was wiresharking while running both server and client on the same machine, which, for some reason, doesn't capture the compression. Running the client on another machine I can see the compression.

                 

                However, the speed of the data pull has degraded from CR1 to CR2. Running large datasets pulls from the EJB with default Deflater compression on CR1 we saw massive speed boosts, round trip times halved.

                 

                In CR2 running the same tests with the same hints we are seeing round trip times drop by about 10% if that. Is there something going on that would make the compression slower and thus negate the effect of smaller packets over the wire?

                 

                Thanks,

                 

                Jason

                • 5. Re: Wildfly 9.0 CR2 EJB client compression no longer working
                  jaikiran

                  Jason Spittel wrote:


                   

                  However, the speed of the data pull has degraded from CR1 to CR2. Running large datasets pulls from the EJB with default Deflater compression on CR1 we saw massive speed boosts, round trip times halved.

                   

                  In CR2 running the same tests with the same hints we are seeing round trip times drop by about 10% if that. Is there something going on that would make the compression slower and thus negate the effect of smaller packets over the wire?

                   

                  Sorry, I am not aware of what might have changed in that area. If you can still reproduce this consistently against the recently released 9.0.0.Final Announcement: WildFly 9.0.2.Final released then please attach an application which can be used to reproduce it.