Re: aliases attribute tomcat7

Hi Pid, Tried your suggestion but got the same results. Any way to debug this? Thanks, Michael 2012/5/21, Pid p...@pidster.com: On 17/05/2012 07:11, Michael Ravits wrote: Hey Pidster, This is the tag I've used: Context

connection reset errors

Dear Tomcat community, I am trying to resolve the problem where some client code in Java frequently gets the following error in the logs: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at

Re: connection reset errors

2012/5/22 Kees Jan Koster kjkos...@gmail.com: Dear Tomcat community, I am trying to resolve the problem where some client code in Java frequently gets the following error in the logs: java.net.SocketException: Connection reset        at

Re: connection reset errors

Dear Jose, 2012/5/22 Kees Jan Koster kjkos...@gmail.com: Dear Tomcat community, I am trying to resolve the problem where some client code in Java frequently gets the following error in the logs: java.net.SocketException: Connection reset at

Re: connection reset errors

Kees Jan Koster wrote: Dear Tomcat community, I am trying to resolve the problem where some client code in Java frequently gets the following error in the logs: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at

Re: connection reset errors

Yes I am. In finally{} block. Here is the client code: Calling the disconnect() method of HttpURLConnection may close the underlying socket if a persistent connection is otherwise idle at that time Try don't call it, test it and tell us :-)

Re: connection reset errors

Dear Jose, Yes I am. In finally{} block. Here is the client code: Calling the disconnect() method of HttpURLConnection may close the underlying socket if a persistent connection is otherwise idle at that time Try don't call it, test it and tell us :-)

Re: connection reset errors

Dear André, Assuming that your client is really connecting to that HTTP connector on port 8080 mentioned above.. Yes, it has a forwarded port 80 (using FreeBSD ipfw) that also points to 8080, and there is an Apache with mod_proxy_http that hooks into 8081. My tests are on the vanilla port,

Re: connection reset errors

Kees Jan Koster wrote: Dear André, Assuming that your client is really connecting to that HTTP connector on port 8080 mentioned above.. Yes, it has a forwarded port 80 (using FreeBSD ipfw) that also points to 8080, and there is an Apache with mod_proxy_http that hooks into 8081. My tests

Tomcat 7. MX4J

Hello, We are going to migrate our application from tomcat 6 to tomcat 7. But during migration we've faced with the following issue: we have the following configuration to have possbility to manage JMX Bean using browser (through http): ... Connector port=8009 handler.list=mx

Re: Fwd: Tomcat 7. MX4J

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vadim, Bringing this back onto the list... On 5/22/12 4:29 PM, Vadzim Mikhalenak wrote: Thank you for the reply! Yes, link http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for version 5.5 but we are migrating from version 6 (sorry for

Re: Tomcat 7. MX4J

2012/5/22 Vadzim Mikhalenak vadzim.mikhale...@gmail.com: Hello  Christopher, * * Thank you for the reply! Yes, link http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for version 5.5 but we are migrating from version 6 (sorry for the confusion) but the configuration above was valid

Re: Tomcat 7. MX4J

On Wed, May 23, 2012 at 12:31 AM, Konstantin Kolinko knst.koli...@gmail.com wrote: 2012/5/22 Vadzim Mikhalenak vadzim.mikhale...@gmail.com: Hello Christopher, * * Thank you for the reply! Yes, link http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for version 5.5 but we