Tomcat 6 and JOBSS (4.0.3 & 4.3)
Posted on 2010-11-26
I'm using the the following java classes that come bundled with Tomcat 6.0 to compress the response object prior to sending it to the client:
The filter uses a default threshold value of 128 meaning that if the response size is less that 128 bytes don't compress the response and it uses ServletOutPutStream but if the size is greater that 128 bytes then it uses GZIPOutputSteam to compress the response. We can also set the threshold value in web.xml, so the default value will be overriden.
1. When I tested this with Jboss 4.3, it didn't work for all the transactions if the threshold value was set to 128 or 90000 or even 50000. But all transactions worked if the value is set to 100000.
2. When I tested this with JBOSS 4.0.3 by setting the thresold to 50000, it works for all the transactions. I didn't test JBOSS 4.0.3. with the values 128 or 90000. But I don't understand why JBOSS 4.3 does'n work for any threshold value but JBOSS 4.0.3.
does anybody know why there is a strange behaviour with JBOSS 4.3?
(as far as I know JBOSS uses Tomcat as a webContainer)