Re: Changing JK_OPT_FWDURIDEFAULT to JK_OPT_FWDURICOMPATUNPARSED

On Tue, 2007-05-15 at 18:37 +0200, Rainer Jung wrote: > I didn't follow this, but the comment in the httpd 2.x module code says: > > /* > * The 2.2 servlet spec errata says the uri from > * HttpServletRequest.getRequestURI() should remain encoded. > * [http://java.sun.com/pr

Tomcat is not responding

Hi, I am using Tomcat 5.0.28 in a RedHat Linux machine. We have deployed a j2ee application under root context of Tomcat server and we are using MySQL as database which is exists on different box. Our application was running fine when we have first deployed it on Jan, 2006 Max connection limit

Re: DO NOT REPLY [Bug 42353] - org.apache.jk.core.MsgContext Error sending end packet

--- Additional Comments From [EMAIL PROTECTED] 2007-05-14 16:31 --- There are other explanations but Bugzilla is not a support forum to provide these explanations. Please sue the users list. Isn't that rather a heavy-handed course of action? :-) ---

DO NOT REPLY [Bug 40070] - APR causes JVM to crashon SEGV

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40070] - APR causes JVM to crashon SEGV

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40070] - APR causes JVM to crashon SEGV

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Changing JK_OPT_FWDURIDEFAULT to JK_OPT_FWDURICOMPATUNPARSED

I didn't follow this, but the comment in the httpd 2.x module code says: /* * The 2.2 servlet spec errata says the uri from * HttpServletRequest.getRequestURI() should remain encoded. * [http://java.sun.com/products/servlet/errata_042700.html] * * We use JkOptions to

Re: tcnative-1.dll crashes jvm: how do i provide

Stu Thompson wrote: > My webapp can somewhat regularly crash the JVM on multiple machines. > Most of the hotspot dump files are remarkably consistence with where the > error is occurring...then again, I do know what is important and what is > not. Running tomcat without tcnative-1.dll resolves th

Changing JK_OPT_FWDURIDEFAULT to JK_OPT_FWDURICOMPATUNPARSED

Hi, I think that the default value of JK_OPT_FWDURIDEFAULT is bad and should be JK_OPT_FWDURICOMPATUNPARSED. Any comments? Cheers Jean-Frederic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMA

tcnative-1.dll crashes jvm: how do i provide

Hi all, My webapp can somewhat regularly crash the JVM on multiple machines. Most of the hotspot dump files are remarkably consistence with where the error is occurring...then again, I do know what is important and what is not. Running tomcat without tcnative-1.dll resolves the problem but I'd

[ANN] Apache Tomcat 6.0.13 released

The Apache Tomcat team announces the immediate availability of Apache Tomcat 6.0.13 stable. This release is the second stable release of the 6.0.x branch, and includes bugfixes over Apache Tomcat 6.0.10. Apache Tomcat 6.0 includes new features over Apache Tomcat 5.5, including support for the new

[RESULT] Release build 6.0.13

9 "stable" binding votes, no other votes. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release build 6.0.13

Martin Dubuc wrote: I have been using 6.0.13 for a few days. I was using 6.0.11 for some time up to then. My app was running pretty smooth with 6.0.11. I do not not if it is a coincidence or not, but since seitching to 6.0.13, I have seen a few cases of Java exceptions, all seems to be related to

Re: [VOTE] Release build 6.0.13

I have been using 6.0.13 for a few days. I was using 6.0.11 for some time up to then. My app was running pretty smooth with 6.0.11. I do not not if it is a coincidence or not, but since seitching to 6.0.13, I have seen a few cases of Java exceptions, all seems to be related to MySQL Connector/J co

DO NOT REPLY [Bug 42424] New: - Missing Hint about Adblock in the docs/FAQs

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 42419] New: - Options for changing jsessionid cookie name

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu