[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout

2012-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #3 from Mark Thomas --- I've been thinking about this and I think the following is the way to go. 1. Make the connection timeout infinite. 2. Add an idle timeout to the WebSocket implementation (defaults to infinite) that times

[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout

2012-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #4 from Jean-Francois Arcand --- Hi Mark, +1 for making the connection timeout infinite. +1 also to add support for websocket timeout property/attribute (will be really useful). Not sure for the ping ... some applications don

RE: svn commit: r1335546 - /tomcat/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/interceptor/ConnectionState.java

2012-05-15 Thread Filip Hanik (mailing lists)
Yes we should. I can do it today, unless you beat me to it > -Original Message- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Monday, May 14, 2012 5:55 AM > To: Tomcat Developers List > Subject: Re: svn commit: r1335546 - /tomcat/trunk/modules/jdbc- > pool/src/main/jav

svn commit: r1338797 - /tomcat/jk/trunk/native/common/jk_util.c

2012-05-15 Thread mturk
Author: mturk Date: Tue May 15 17:19:03 2012 New Revision: 1338797 URL: http://svn.apache.org/viewvc?rev=1338797&view=rev Log: This is just insane. Use memzero instead manually setting each and every struct member to zero Modified: tomcat/jk/trunk/native/common/jk_util.c Modified: tomcat/jk

[Bug 53237] New: TCP connections are stuck in SYN_RECV

2012-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53237 Priority: P2 Bug ID: 53237 Assignee: dev@tomcat.apache.org Summary: TCP connections are stuck in SYN_RECV Severity: normal Classification: Unclassified OS: Linux

[Bug 53237] TCP connections are stuck in SYN_RECV

2012-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53237 --- Comment #1 from wilbra...@iivip.com --- These symptoms were seen with both tomcat 6 and 7, using tomcat-native 1.1.14 and 1.1.22. Systems were centOS 4.4 32-bit. -- You are receiving this mail because: You are the assignee for the bug

[Bug 53231] Suggestion for the Windows 32/64 bit installer - include port 8443 in the configurator

2012-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53231 --- Comment #4 from Konstantin Kolinko --- Nothing listens on port 8443, so there is no conflict when several instances of Tomcat are installed with the same value for that port. The value of "redirectPort" attribute is just a number retur

[Bug 53237] TCP connections are stuck in SYN_RECV

2012-05-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53237 Konstantin Kolinko changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module tomcat-7.0.x) failed

2012-05-15 Thread Bill Barker
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc7.0.x-test has an issue affecting its community integration. This

[GUMP@vmgump]: Project tomcat-trunk-test (in module tomcat-trunk) failed

2012-05-15 Thread Bill Barker
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-trunk-test has an issue affecting its community integration. This i