our users seeing tcp resets believe originating our server or intermediate device in between.
on our server application log, can see error tallies time(s) seeing resets.
the stack trace below:
may 14, 2016 5:04:04 pm org.apache.catalina.core.standardwrappervalve invoke severe: servlet.service() servlet adity threw exception java.io.eofexception @ java.util.zip.gzipinputstream.readubyte(gzipinputstream.java:207) @ java.util.zip.gzipinputstream.readushort(gzipinputstream.java:197) @ java.util.zip.gzipinputstream.readheader(gzipinputstream.java:136) @ java.util.zip.gzipinputstream.<init>(gzipinputstream.java:58) @ java.util.zip.gzipinputstream.<init>(gzipinputstream.java:68) @ com.osmoticweb.gzipfilter.gzip2wayrequeststream.<init>(gzip2wayrequeststream.java:20) @ com.osmoticweb.gzipfilter.gzip2wayrequestwrapper.<init>(gzip2wayrequestwrapper.java:25) @ com.osmoticweb.gzipfilter.gzip2wayfilter.dofilter(gzip2wayfilter.java:40) @ org.apache.catalina.core.applicationfilterchain.internaldofilter(applicationfilterchain.java:235) @ org.apache.catalina.core.applicationfilterchain.dofilter(applicationfilterchain.java:206) @ org.springframework.orm.hibernate3.support.opensessioninviewfilter.dofilterinternal(opensessioninviewfilter.java:198) @ org.springframework.web.filter.onceperrequestfilter.dofilter(onceperrequestfilter.java:76) @ org.apache.catalina.core.applicationfilterchain.internaldofilter(applicationfilterchain.java:235) @ org.apache.catalina.core.applicationfilterchain.dofilter(applicationfilterchain.java:206) @ org.apache.catalina.core.standardwrappervalve.invoke(standardwrappervalve.java:233) @ org.apache.catalina.core.standardcontextvalve.invoke(standardcontextvalve.java:191) @ org.apache.catalina.core.standardhostvalve.invoke(standardhostvalve.java:127) @ org.apache.catalina.valves.errorreportvalve.invoke(errorreportvalve.java:102) @ org.apache.catalina.valves.accesslogvalve.invoke(accesslogvalve.java:555) @ org.apache.catalina.core.standardenginevalve.invoke(standardenginevalve.java:109) @ org.apache.catalina.connector.coyoteadapter.service(coyoteadapter.java:298) @ org.apache.coyote.http11.http11processor.process(http11processor.java:852) @ org.apache.coyote.http11.http11protocol$http11connectionhandler.process(http11protocol.java:588) @ org.apache.tomcat.util.net.jioendpoint$worker.run(jioendpoint.java:489) @ java.lang.thread.run(thread.java:619) my question is: our application causing resets or client?
apologies lack of technicality around question.
the problem in client.
there 2 possibilities:
1) client not sending data. 2) client putting wrong value content-lenght header.
Comments
Post a Comment