Java VM 1.6.0_26 crashes Tomcat 6.0.32 when HTTP compression set to on
We are running the 64-bit version of Java VM 1.6_06 together with Apache Tomcat 6.0.32 on a 64-bit Windows Server 2003. After we installed the latest security updates this Wednesday to Windows the Java VM running Tomcat started to crash (it has now happened three times. After some investigation it seems to be the zip.dll in Java causing the problem (check the log below), so I now turned of HTTP compression in Tomcat. These are the parameters we used for compression for the Connector (it's running under port 443 on SSL). compression=2048 noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml,text/plain,text/css,text/javascri pt,text/xhtml Any advice or anyone familiar with this problem, I haven’t found anything useful in the Java bug database (I submitted a bug report for this problem) or in any discussion forum. Thanks in advance, André # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x6d8534a2, pid=1532, tid=5188 # # JRE version: 6.0_26-b03 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode windows-amd64 compressed oops) # Problematic frame: # C [zip.dll+0x34a2] # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --- T H R E A D --- Current thread (0x84b73800): JavaThread http-443-109 daemon [_thread_in_native, id=5188, stack(0x8ea5,0x8eb5)] siginfo: ExceptionCode=0xc005, reading address 0x9f93c000 Registers: RAX=0x9f929e60, RBX=0x9c697000, RCX=0x000121a0, RDX=0x RSP=0x8eb4e6a0, RBP=0x0001, RSI=0x0001, RDI=0x R8 =0x0001219e, R9 =0xfb44, R10=0x9c697000, R11=0xa275 R12=0x219c, R13=0x0002, R14=0x0003, R15=0x81f75900 RIP=0x6d8534a2, EFLAGS=0x00010282 Top of Stack: (sp=0x8eb4e6a0) 0x8eb4e6a0: 84e4d000 65621c8d 0x8eb4e6b0: 0003 029a 0x8eb4e6c0: 0003 029a 0x8eb4e6d0: 0001 9e677a90 0x8eb4e6e0: 0001 0x8eb4e6f0: 9c697000 6d852983 0x8eb4e700: 9b57c7b0 0200 0x8eb4e710: 705fef90 07ff7fc2daab 0x8eb4e720: 9b57c7b0 0200 0x8eb4e730: 6d85a850 9c697000 0x8eb4e740: 0x8eb4e750: 6d8539b6 0x8eb4e760: 705fef90 0200 0x8eb4e770: 0200 07ff7fc2db50 0x8eb4e780: 705fef90 9e677a90 0x8eb4e790: 8eb4e870 Instructions: (pc=0x6d8534a2) 0x6d853482: 4d 03 00 00 3b c7 0f 84 6e 03 00 00 41 3b c6 72 0x6d853492: 4f 48 8b 43 48 44 8b 83 8c 00 00 00 41 8d 48 02 0x6d8534a2: 0f b6 14 01 8b 43 68 8b 4b 78 d3 e0 33 d0 48 8b 0x6d8534b2: 43 60 23 53 74 8b ca 89 4b 68 44 0f b7 24 50 8b Register to memory mapping: RAX=0x9f929e60 is an unknown value RBX=0x9c697000 is an unknown value RCX=0x000121a0 is an unknown value RDX=0x is an unknown value RSP=0x8eb4e6a0 is pointing into the stack for thread: 0x84b73800 RBP=0x0001 is an unknown value RSI=0x0001 is an unknown value RDI=0x is an unknown value R8 =0x0001219e is an unknown value R9 =0xfb44 is an unknown value R10=0x9c697000 is an unknown value R11=0xa275 is an unknown value R12=0x219c is an unknown value R13=0x0002 is an unknown value R14=0x0003 is an unknown value R15=0x81f75900 is an unknown value Stack: [0x8ea5,0x8eb5], sp=0x8eb4e6a0, free space=1017k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [zip.dll+0x34a2] Java_java_util_zip_ZipEntry_initFields+0x1282 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J java.util.zip.Deflater.deflateBytes(J[BII)I J org.apache.coyote.http11.filters.GzipOutputFilter.flush()V J org.apache.coyote.http11.Http11AprProcessor.action(Lorg/apache/coyote/Acti onCode;Ljava/lang/Object;)V J org.apache.catalina.connector.OutputBuffer.doFlush(Z)V J org.apache.catalina.connector.CoyoteWriter.flush()V J java.io.BufferedWriter.flush()V J org.apache.xml.serializer.ToXMLStream.endDocument()V j com.planmill.translets.resourceplanner.transform(Lorg/apache/xalan/xsltc/D OM;Lorg/apache/xml/dtm/DTMAxisIterator
Re: HTTP compression
I need to generate thousands of test cases for a benchmark and I am trying to turn compression off (I want to edit one message and change the user ID, branch and account number to generate many files which I intend to use with JMeter Doing this manually with compressed messages will take ages) I have an application which runs under JBoss 420 I changed the server.xml connector by adding compression=off When I look at my fiddler intercepts I still see a compressed message: ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:BodyprocessEncrypted xmlns=http://www.vantagebanking.com;arg0 xmlns=ADwAUgBFAFEAVQBFAFMAVAA+ADwARwBFAE4ARQBSAEEATAAgAEwAbwBjAGEAbABlAD0AIgBlAG4ALQBBAFUAIgA+ADwARABBAFQARQAgAEYAbwByAG0AYQB0AD0AIgBkAC8ATQBNAC8AeQB5AHkAeQAiAD4AMwAvADAAMQAvADIAMAAxADAAPAAvAEQAQQBUAEUAPgA8AEIAUgBBAE4AQwBIAF8ATgBVAE0APgAwADAAMAAwADEAPAAvAEIAUgBBAE4AQwBIAF8ATgBVAE0APgA8AFUAUwBFAFIAXwBJAEQAPgAwADAAMAAwADEAPAAvAFUAUwBFAFIAXwBJAEQAPgA8AEwATwBDAEEATABFAD4AZQBuAC0AQQBVADwALwBMAE8AQwBBAEwARQA+ADwAVABSAEEATgBTAEEAQwBUAEkATwBOAF8AQwBPAEQARQAgAFQAUgBBAE4AXwBUAFkAUABFAD0AIgBDAEUATgBUAEUAUgBQAE8ASQBOAFQAIgA+AEQARABFADAAMAAwADIAPAAvAFQAUgBBAE4AUwBBAEMAVABJAE8ATgBfAEMATwBEAEUAPgA8AFMAQwBSAEUARQBOAF8ATgBBAE0ARQA+AEQAZQBwAG8AcwBpAHQAQQBjAGMAbwB1AG4AdAA8AC8AUwBDAFIARQBFAE4AXwBOAEEATQBFAD4APABTAEMAUgBFAEUATgBfAEcAVQBJAEQAPgBjAGYAYwBjADUAOAAyAGMALQA1ADIANgBiAC0ANABkADQANAAtAGIAMwBjADQALQBmAGQAYwA4AGYAZABkADYAOABlAGIAOQA8AC8AUwBDAFIARQBFAE4AXwBHAFUASQBEAD4APABOAEUAVwBTAF8AVgBFAFIAUwBJAE8ATgA+AC0AMQA8AC8ATgBFAFcAUwBfAFYARQBSAFMASQBPAE4APgA8AFQAQQBTAEsAXwBEAEEAVABFAF8AVABJAE0ARQAgAEYATwBSAE0AQQBUAD0AIgBkAC8ATQBNAC8AeQB5AHkAeQAgAEgASAA6AG0AbQA6AHMAcwAiACAATABvAGMAYQBsAGUAPQAiAGUAbgAtAEEAVQAiAD4AMQAvADAAMQAvADAAMAAwADEAIAAwADAAOgAwADAAOgAwADAAPAAvAFQAQQBTAEsAXwBEAEEAVABFAF8AVABJAE0ARQA+ADwASQBQAF8AQQBEAEQAUgBFAFMAUwA+ADoAOgAxADwALwBJAFAAXwBBAEQARABSAEUAUwBTAD4APAAvAEcARQBOAEUAUgBBAEwAPgA8AFMAQwBSAEUARQBOAF8ARABBAFQAQQA+ADwARgBJAEUATABEACAASQBEAD0AIgBBAGMAYwBvAHUAbgB0AE4AdQBtACIAIABUAFkAUABFAD0AIgBEAGkAZwBpAHQAIgA+ADEAMQA8AC8ARgBJAEUATABEAD4APAAvAFMAQwBSAEUARQBOAF8ARABBAFQAQQA+ADwALwBSAEUAUQBVAEUAUwBUAD4=/arg0/processEncrypted/soap:Body/soap:Envelope Can anyone point me in the right direction ? I am not worried about network speed because the benchmark used a Gbit network Thanks Johan ws_dev wrote: hello, Does Tomcat support HTTP compression. If yes, is there a way to enable/disable this feature Rajiv - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- View this message in context: http://old.nabble.com/HTTP-compression-tp10217600p29004649.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: HTTP compression
On 27/06/2010 10:02, johanvermeij wrote: I need to generate thousands of test cases for a benchmark and I am trying to turn compression off (I want to edit one message and change the user ID, branch and account number to generate many files which I intend to use with JMeter Doing this manually with compressed messages will take ages) I have an application which runs under JBoss 420 I changed the server.xml connector by adding compression=off When I look at my fiddler intercepts I still see a compressed message: ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:BodyprocessEncrypted xmlns=http://www.vantagebanking.com;arg0 xmlns=ADwAUgBFAFEAVQBFAFMAVAA+ADwARwBFAE4ARQBSAEEATAAgAEwAbwBjAGEAbABlAD0AIgBlAG4ALQBBAFUAIgA+ADwARABBAFQARQAgAEYAbwByAG0AYQB0AD0AIgBkAC8ATQBNAC8AeQB5AHkAeQAiAD4AMwAvADAAMQAvADIAMAAxADAAPAAvAEQAQQBUAEUAPgA8AEIAUgBBAE4AQwBIAF8ATgBVAE0APgAwADAAMAAwADEAPAAvAEIAUgBBAE4AQwBIAF8ATgBVAE0APgA8AFUAUwBFAFIAXwBJAEQAPgAwADAAMAAwADEAPAAvAFUAUwBFAFIAXwBJAEQAPgA8AEwATwBDAEEATABFAD4AZQBuAC0AQQBVADwALwBMAE8AQwBBAEwARQA+ADwAVABSAEEATgBTAEEAQwBUAEkATwBOAF8AQwBPAEQARQAgAFQAUgBBAE4AXwBUAFkAUABFAD0AIgBDAEUATgBUAEUAUgBQAE8ASQBOAFQAIgA+AEQARABFADAAMAAwADIAPAAvAFQAUgBBAE4AUwBBAEMAVABJAE8ATgBfAEMATwBEAEUAPgA8AFMAQwBSAEUARQBOAF8ATgBBAE0ARQA+AEQAZQBwAG8AcwBpAHQAQQBjAGMAbwB1AG4AdAA8AC8AUwBDAFIARQBFAE4AXwBOAEEATQBFAD4APABTAEMAUgBFAEUATgBfAEcAVQBJAEQAPgBjAGYAYwBjADUAOAAyAGMALQA1ADIANgBiAC0ANABkADQANAAtAGIAMwBjADQALQBmAGQAYwA4AGYAZABkADYAOABlAGIAOQA8AC8AUwBDAFIARQBFAE4AXwBHAFUASQBEAD4APABOAEUAVwBTAF8AVgBFAFIAUwBJAE8ATgA+AC0AMQA8AC8ATgBFAFcAUwBfAFYARQBSAFMASQBPAE4APgA8AFQAQQBTAEsAXwBEAEEAVABFAF8AVABJAE0 ARQAgAEYATwBSAE0AQQBUAD0AIgBkAC8ATQBNAC8AeQB5AHkAeQAgAEgASAA6AG0AbQA6AHMAcwAiACAATABvAGMAYQBsAGUAPQAiAGUAbgAtAEEAVQAiAD4AMQAvADAAMQAvADAAMAAwADEAIAAwADAAOgAwADAAOgAwADAAPAAvAFQAQQBTAEsAXwBEAEEAVABFAF8AVABJAE0ARQA+ADwASQBQAF8AQQBEAEQAUgBFAFMAUwA+ADoAOgAxADwALwBJAFAAXwBBAEQARABSAEUAUwBTAD4APAAvAEcARQBOAEUAUgBBAEwAPgA8AFMAQwBSAEUARQBOAF8ARABBAFQAQQA+ADwARgBJAEUATABEACAASQBEAD0AIgBBAGMAYwBvAHUAbgB0AE4AdQBtACIAIABUAFkAUABFAD0AIgBEAGkAZwBpAHQAIgA+ADEAMQA8AC8ARgBJAEUATABEAD4APAAvAFMAQwBSAEUARQBOAF8ARABBAFQAQQA+ADwALwBSAEUAUQBVAEUAUwBUAD4=/arg0/processEncrypted/soap:Body/soap:Envelope I'm not familiar with Fiddler, what does the above represent? Can anyone point me in the right direction ? I am not worried about network speed because the benchmark used a Gbit network Thanks Johan Did you find an old email and reply to it? Please just start a new message next time. p ws_dev wrote: hello, Does Tomcat support HTTP compression. If yes, is there a way to enable/disable this feature Rajiv - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org signature.asc Description: OpenPGP digital signature
RE: HTTP compression
From: Pid [mailto:p...@pidster.com] Subject: Re: HTTP compression ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:Body processEncrypted xmlns=http://www.vantagebanking.com; arg0 xmlns=ADwAUgBFAFEAVQBFAFMAVAA+ADwARwBFAE4ARQBSAEEATAAgAEwAbwBjAGEAbA I suspect the payload is /encrypted/, not compressed (hence the processEncrypted element). Fiddling (no pun intended) with the compression won't change that. I'm not familiar with Fiddler, what does the above represent? Fiddler2 is a very cool proxy that will display lots of interesting things about HTTP traffic: http://www.fiddler2.com/fiddler2/ Easier to use than Wireshark for typical HTTP messaging investigation. Unfortunately, it appears to be Windows-only, so it won't be terribly useful on Pid's Mac... - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
HTTP compression
hello, Does Tomcat support HTTP compression. If yes, is there a way to enable/disable this feature Rajiv - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: HTTP compression
See if the compression property is what you need: http://tomcat.apache.org/tomcat-5.5-doc/config/http.html -Original Message- From: Rajiv M [mailto:[EMAIL PROTECTED] Sent: Friday, April 27, 2007 5:10 PM To: Tomcat Users List Subject: HTTP compression hello, Does Tomcat support HTTP compression. If yes, is there a way to enable/disable this feature Rajiv - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP compression
Thank you! Is there a testcase/sample app where I can see the difference of enabling/disabling HTTP compression. On 4/27/07, Praveen Balaji [EMAIL PROTECTED] wrote: See if the compression property is what you need: http://tomcat.apache.org/tomcat-5.5-doc/config/http.html -Original Message- From: Rajiv M [mailto:[EMAIL PROTECTED] Sent: Friday, April 27, 2007 5:10 PM To: Tomcat Users List Subject: HTTP compression hello, Does Tomcat support HTTP compression. If yes, is there a way to enable/disable this feature Rajiv - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- ~~~Truth is out there.~~~ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP compression
On 4/27/07, Rajiv M [EMAIL PROTECTED] wrote: Is there a testcase/sample app where I can see the difference of enabling/disabling HTTP compression. DIY :-) -Rashmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP compression
Are you measuring throughput ??? Martin This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Rashmi Rubdi [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Friday, April 27, 2007 10:36 AM Subject: Re: HTTP compression On 4/27/07, Rajiv M [EMAIL PROTECTED] wrote: Is there a testcase/sample app where I can see the difference of enabling/disabling HTTP compression. DIY :-) -Rashmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS: tomcat always do http compression without watch min size
you won't be able to disable the chunked encoding. But you can disable the compression by ensure the client does NOT send a accept-encoding header with the a value containing gzip or by using the noCompressionUserAgents, compressableMimeType attributes on the connector. -Tim wakeup wrote: Thanks, I think you are right. Axis don't set content-leght because it is sending response chunked. Where do I have to disable chunk in the axis server o in the client? Thankss Tim Funk wrote: compressionMinSize only works with fixed file sizes. If axis is NOT setting the ContentLength before serving back results - then compressionMinSize can't be checked to see if compression can be done. And then compression will be done based on the client input headers. -Tim wakeup wrote: Hi, I have an apache tomcat 5.5.17. In my server.xml file I have put Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on *compressionMinSize=2048000 * noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml,text/plain,application/dime / It run sucessfull with normal html tomcat pages. But when I ask to axis 1.4 webservices it always compress the response althought it be less than 1kb. Why axis don't respect compressionMinSize parameter? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS: tomcat always do http compression without watch min size
Thanks but I don't want disable compress, because I want compress when the lenght exceeds a limit. In the client I can't disable response chuked? Tim Funk wrote: you won't be able to disable the chunked encoding. But you can disable the compression by ensure the client does NOT send a accept-encoding header with the a value containing gzip or by using the noCompressionUserAgents, compressableMimeType attributes on the connector. -Tim wakeup wrote: Thanks, I think you are right. Axis don't set content-leght because it is sending response chunked. Where do I have to disable chunk in the axis server o in the client? Thankss Tim Funk wrote: compressionMinSize only works with fixed file sizes. If axis is NOT setting the ContentLength before serving back results - then compressionMinSize can't be checked to see if compression can be done. And then compression will be done based on the client input headers. -Tim wakeup wrote: Hi, I have an apache tomcat 5.5.17. In my server.xml file I have put Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on *compressionMinSize=2048000 * noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml,text/plain,application/dime / It run sucessfull with normal html tomcat pages. But when I ask to axis 1.4 webservices it always compress the response althought it be less than 1kb. Why axis don't respect compressionMinSize parameter? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/AXIS%3A-tomcat-always-do-http-compression-without-watch-min-size-tf2386947.html#a6677693 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AXIS: tomcat always do http compression without watch min size
Hi, I have an apache tomcat 5.5.17. In my server.xml file I have put Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on *compressionMinSize=2048000 * noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml,text/plain,application/dime / It run sucessfull with normal html tomcat pages. But when I ask to axis 1.4 webservices it always compress the response althought it be less than 1kb. Why axis don't respect compressionMinSize parameter? Thanks -- View this message in context: http://www.nabble.com/AXIS%3A-tomcat-always-do-http-compression-without-watch-min-size-tf2386947.html#a6654078 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS: tomcat always do http compression without watch min size
Which mime type send axis as responce? Peter Am 05.10.2006 um 09:46 schrieb wakeup: Hi, I have an apache tomcat 5.5.17. In my server.xml file I have put Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on *compressionMinSize=2048000 * noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml,text/plain,application/dime / It run sucessfull with normal html tomcat pages. But when I ask to axis 1.4 webservices it always compress the response althought it be less than 1kb. Why axis don't respect compressionMinSize parameter? Thanks -- View this message in context: http://www.nabble.com/AXIS%3A-tomcat- always-do-http-compression-without-watch-min-size- tf2386947.html#a6654078 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS: tomcat always do http compression without watch min size
compressionMinSize only works with fixed file sizes. If axis is NOT setting the ContentLength before serving back results - then compressionMinSize can't be checked to see if compression can be done. And then compression will be done based on the client input headers. -Tim wakeup wrote: Hi, I have an apache tomcat 5.5.17. In my server.xml file I have put Connector port=8080 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true compression=on *compressionMinSize=2048000 * noCompressionUserAgents=gozilla, traviata compressableMimeType=text/html,text/xml,text/plain,application/dime / It run sucessfull with normal html tomcat pages. But when I ask to axis 1.4 webservices it always compress the response althought it be less than 1kb. Why axis don't respect compressionMinSize parameter? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
