DO NOT REPLY [Bug 31459] - org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out

2004-11-30 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31459. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 27104] - got an exception when testing a simple cluster app

2004-11-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27104. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 31659] - Page context not fully populated for Exception if using app-wide error page

2004-11-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31659. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-11-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

RE: DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-11-15 Thread support
ContextConfig Exception DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org

RE: DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-11-15 Thread support
ContextConfig Exception Dear customer, we received your email and will get back to you shortly. Sincerely, Toshiba Global Support Centre - In Touch with the World -Original Message- From: [EMAIL PROTECTED] Sent: 15.11.2004 12:44:43 To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 25217

DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-11-15 Thread bugzilla
common/lib it loads, but then cries for other jar file.Note that we do not get the error for all the jar files but selected one. Attached is a jar file which fails to open with the error in log: 2004-11-15 16:42:48 ContextConfig[/] Exception processing JAR at resource path /WEB-INF/lib/saxpath.jar

RE: DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-11-15 Thread support
ContextConfig Exception DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25217. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org

RE: DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-11-15 Thread support
ContextConfig Exception Dear customer, we received your email and will get back to you shortly. Sincerely, Toshiba Global Support Centre - In Touch with the World -Original Message- From: [EMAIL PROTECTED] Sent: 15.11.2004 12:47:10 To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 25217

DO NOT REPLY [Bug 31459] - org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out

2004-11-10 Thread bugzilla
/show_bug.cgi?id=31459 org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 22388] - TC 5.0.* Startup Exception (ConcurrentModificationException)

2004-10-11 Thread bugzilla
/show_bug.cgi?id=22388 TC 5.0.* Startup Exception (ConcurrentModificationException) [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL

DO NOT REPLY [Bug 22388] - TC 5.0.* Startup Exception (ConcurrentModificationException)

2004-10-11 Thread bugzilla
/show_bug.cgi?id=22388 TC 5.0.* Startup Exception (ConcurrentModificationException) [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED

DO NOT REPLY [Bug 31659] New: - Page context not fully populated for Exception if using app-wide error page

2004-10-11 Thread bugzilla
/show_bug.cgi?id=31659 Page context not fully populated for Exception if using app-wide error page Summary: Page context not fully populated for Exception if using app-wide error page Product: Tomcat 5 Version: 5.0.28 Platform: PC OS

DO NOT REPLY [Bug 31459] New: - org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out

2004-09-28 Thread bugzilla
/show_bug.cgi?id=31459 org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out Summary: org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept

DO NOT REPLY [Bug 31459] - org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out

2004-09-28 Thread bugzilla
/show_bug.cgi?id=31459 org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketTimeoutException: Accept timed out --- Additional Comments From [EMAIL PROTECTED] 2004-09-28 22:02 --- Created an attachment (id=12887

DO NOT REPLY [Bug 31388] New: - Exception: too many open files on Win2003

2004-09-23 Thread bugzilla
/show_bug.cgi?id=31388 Exception: too many open files on Win2003 Summary: Exception: too many open files on Win2003 Product: Tomcat 5 Version: 5.0.24 Platform: Other OS/Version: Windows NT/2K Status: NEW Severity: Critical

DO NOT REPLY [Bug 31388] - Exception: too many open files on Win2003

2004-09-23 Thread bugzilla
/show_bug.cgi?id=31388 Exception: too many open files on Win2003 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 31204] - Tomcat exits on null pointer exception

2004-09-23 Thread bugzilla
/show_bug.cgi?id=31204 Tomcat exits on null pointer exception [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

DO NOT REPLY [Bug 31204] - Tomcat exits on null pointer exception

2004-09-23 Thread bugzilla
/show_bug.cgi?id=31204 Tomcat exits on null pointer exception [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

DO NOT REPLY [Bug 31204] - Tomcat exits on null pointer exception

2004-09-23 Thread bugzilla
/show_bug.cgi?id=31204 Tomcat exits on null pointer exception --- Additional Comments From [EMAIL PROTECTED] 2004-09-23 21:13 --- Created an attachment (id=12852) Client to reproduce this - To unsubscribe, e-mail: [EMAIL

DO NOT REPLY [Bug 31369] New: - Tomcat throws an exception when using a formular with pocket pc

2004-09-22 Thread bugzilla
/show_bug.cgi?id=31369 Tomcat throws an exception when using a formular with pocket pc Summary: Tomcat throws an exception when using a formular with pocket pc Product: Tomcat 5 Version: 5.0.27 Platform: PC OS/Version: Linux

DO NOT REPLY [Bug 31369] - Tomcat throws an exception when using a formular with pocket pc

2004-09-22 Thread bugzilla
/show_bug.cgi?id=31369 Tomcat throws an exception when using a formular with pocket pc [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 31369] - Tomcat throws an exception when using a formular with pocket pc

2004-09-22 Thread bugzilla
/show_bug.cgi?id=31369 Tomcat throws an exception when using a formular with pocket pc --- Additional Comments From [EMAIL PROTECTED] 2004-09-22 16:49 --- happens when trying to upload a form multipart similar to the situation in Bug 25527

DO NOT REPLY [Bug 29855] - Broken pipe exception on large POST data

2004-09-15 Thread bugzilla
/show_bug.cgi?id=29855 Broken pipe exception on large POST data [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 31204] New: - Tomcat exits on null pointer exception

2004-09-13 Thread bugzilla
/show_bug.cgi?id=31204 Tomcat exits on null pointer exception Summary: Tomcat exits on null pointer exception Product: Tomcat 5 Version: 5.0.28 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: Other

DO NOT REPLY [Bug 31204] - Tomcat exits on null pointer exception

2004-09-13 Thread bugzilla
/show_bug.cgi?id=31204 Tomcat exits on null pointer exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 22695] - TC 5.0.9 Exception During Startup

2004-08-31 Thread bugzilla
/show_bug.cgi?id=22695 TC 5.0.9 Exception During Startup [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

DO NOT REPLY [Bug 30274] - Servlet.service() for servlet jsp threw exception

2004-08-30 Thread bugzilla
/show_bug.cgi?id=30274 Servlet.service() for servlet jsp threw exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

Re: anyone seen this coyote Exception?

2004-08-19 Thread Mark Swanson
Solution: upgrade from 5.0.25 to 5.0.27. At least then coyote won't throw an exception. The third party library I was using was returning a contentLength of -1 and null data. I believe that was the cause and 5.0.27 seems to handle this better. Cheers. -- Free SyncML-capable replacement

anyone seen this coyote Exception?

2004-08-17 Thread Mark Swanson
Tomcat 5.0.25: Aug 17, 2004 11:24:44 PM org.apache.coyote.tomcat5.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request processing java.lang.ArrayIndexOutOfBoundsException: 0 at org.apache.coyote.tomcat5.CoyoteAdapter.normalize

DO NOT REPLY [Bug 29855] - Broken pipe exception on large POST data

2004-07-28 Thread bugzilla
/show_bug.cgi?id=29855 Broken pipe exception on large POST data --- Additional Comments From [EMAIL PROTECTED] 2004-07-28 15:05 --- Tomcat 5 has made changes to the CGI servlet as well as relevant Connector code. Please re-test on Tomcat 5.0.27 or later. Thanks

DO NOT REPLY [Bug 30274] - Servlet.service() for servlet jsp threw exception

2004-07-26 Thread bugzilla
/show_bug.cgi?id=30274 Servlet.service() for servlet jsp threw exception --- Additional Comments From [EMAIL PROTECTED] 2004-07-26 15:54 --- Well, seeing as how the exception is in your code, maybe you can post upload.jsp? As an aside, you might want to use the mailing list for bug

DO NOT REPLY [Bug 30274] New: - Servlet.service() for servlet jsp threw exception

2004-07-22 Thread bugzilla
Servlet.service() for servlet jsp threw exception java.lang.ClassCastException DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30274. ANY REPLY MADE TO THIS MESSAGE

DO NOT REPLY [Bug 30274] - Servlet.service() for servlet jsp threw exception

2004-07-22 Thread bugzilla
/show_bug.cgi?id=30274 Servlet.service() for servlet jsp threw exception [EMAIL PROTECTED] changed: What|Removed |Added Summary|Servlet.service() for |Servlet.service

DO NOT REPLY [Bug 22695] - TC 5.0.9 Exception During Startup

2004-07-21 Thread bugzilla
/show_bug.cgi?id=22695 TC 5.0.9 Exception During Startup --- Additional Comments From [EMAIL PROTECTED] 2004-07-21 18:15 --- Can you please post steps and a WAR we can use to reproduce this exception? - To unsubscribe, e-mail

DO NOT REPLY [Bug 22695] - TC 5.0.9 Exception During Startup

2004-07-15 Thread bugzilla
/show_bug.cgi?id=22695 TC 5.0.9 Exception During Startup [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

DO NOT REPLY [Bug 22695] - TC 5.0.9 Exception During Startup

2004-07-15 Thread bugzilla
/show_bug.cgi?id=22695 TC 5.0.9 Exception During Startup --- Additional Comments From [EMAIL PROTECTED] 2004-07-15 22:52 --- Correction, I have to shutdown, reinstall my war, then startup again. - To unsubscribe, e-mail

DO NOT REPLY [Bug 30067] New: - Scripting elements are disallowed here exception behind scriptless tag

2004-07-13 Thread bugzilla
/show_bug.cgi?id=30067 Scripting elements are disallowed here exception behind scriptless tag Summary: Scripting elements are disallowed here exception behind scriptless tag Product: Tomcat 5 Version: 5.0.25 Platform: PC OS/Version

DO NOT REPLY [Bug 30067] - Scripting elements are disallowed here exception behind scriptless tag

2004-07-13 Thread bugzilla
/show_bug.cgi?id=30067 Scripting elements are disallowed here exception behind scriptless tag --- Additional Comments From [EMAIL PROTECTED] 2004-07-13 09:55 --- Created an attachment (id=12098) Scripting elements exception are disallowed here - exception

DO NOT REPLY [Bug 30067] - Scripting elements are disallowed here exception behind scriptless tag

2004-07-13 Thread bugzilla
/show_bug.cgi?id=30067 Scripting elements are disallowed here exception behind scriptless tag [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 27829] - server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable

2004-07-12 Thread bugzilla
/show_bug.cgi?id=27829 server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 27829] - server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable

2004-07-12 Thread bugzilla
/show_bug.cgi?id=27829 server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 27829] - server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable

2004-07-12 Thread bugzilla
/show_bug.cgi?id=27829 server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable --- Additional Comments From [EMAIL PROTECTED] 2004-07-12 18:32 --- *** Bug 27141 has been marked as a duplicate of this bug

DO NOT REPLY [Bug 30063] New: - tomcat suddenly terminated with following messages - Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=80] ignored exception:

2004-07-12 Thread bugzilla
/show_bug.cgi?id=30063 tomcat suddenly terminated with following messages - Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=80] ignored exception: Summary: tomcat suddenly terminated with following messages - Endpoint ServerSocket[addr=0.0.0.0

DO NOT REPLY [Bug 27829] - server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable

2004-07-11 Thread bugzilla
/show_bug.cgi?id=27829 server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 29855] New: - Broken pipe exception on large POST data

2004-06-29 Thread bugzilla
/show_bug.cgi?id=29855 Broken pipe exception on large POST data Summary: Broken pipe exception on large POST data Product: Tomcat 5 Version: 5.0.0 Platform: All OS/Version: Solaris Status: NEW Severity: Major Priority: Other

DO NOT REPLY [Bug 25217] - Catalina ContextConfig Exception

2004-06-22 Thread bugzilla
/show_bug.cgi?id=25217 Catalina ContextConfig Exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 18650] - Exception while processing a JAR file

2004-06-21 Thread bugzilla
/show_bug.cgi?id=18650 Exception while processing a JAR file [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

DO NOT REPLY [Bug 9997] - Servlet.service() for servlet default threw exception java.net.SocketException: Operation would block

2004-06-19 Thread bugzilla
/show_bug.cgi?id=9997 Servlet.service() for servlet default threw exception java.net.SocketException: Operation would block [EMAIL PROTECTED] changed: What|Removed |Added Status

DO NOT REPLY [Bug 29681] New: - Null pointer exception when connecting to my servlet

2004-06-18 Thread bugzilla
/show_bug.cgi?id=29681 Null pointer exception when connecting to my servlet Summary: Null pointer exception when connecting to my servlet Product: Tomcat 5 Version: 5.0.25 Platform: Other OS/Version: Linux Status: NEW Severity: Major

DO NOT REPLY [Bug 29681] - Null pointer exception when connecting to my servlet

2004-06-18 Thread bugzilla
/show_bug.cgi?id=29681 Null pointer exception when connecting to my servlet [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 29387] - Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word

2004-06-18 Thread bugzilla
/show_bug.cgi?id=29387 Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word [EMAIL PROTECTED] changed: What|Removed |Added CC

DO NOT REPLY [Bug 29641] New: - Socket exception hangs tomcat

2004-06-17 Thread bugzilla
/show_bug.cgi?id=29641 Socket exception hangs tomcat Summary: Socket exception hangs tomcat Product: Tomcat 5 Version: 5.0.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component

DO NOT REPLY [Bug 29641] - Socket exception hangs tomcat

2004-06-17 Thread bugzilla
/show_bug.cgi?id=29641 Socket exception hangs tomcat [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 29387] - Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word

2004-06-07 Thread bugzilla
/show_bug.cgi?id=29387 Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 29387] New: - Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word

2004-06-04 Thread bugzilla
/show_bug.cgi?id=29387 Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word Summary: Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word Product: Tomcat 5

DO NOT REPLY [Bug 29387] - Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word

2004-06-04 Thread bugzilla
/show_bug.cgi?id=29387 Null pointer exception in CoyoteRequest in parseCookies() method when cookie name is reserved word --- Additional Comments From [EMAIL PROTECTED] 2004-06-04 10:39 --- The most reasonable is to remove the log statement

DO NOT REPLY [Bug 29327] New: - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null Summary: ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null Product: Tomcat 5 Version: 5.0.25

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 17:55 --- Created an attachment (id=11711) web app to reproduce; its source code and class files

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 17:56 --- How about mentioning the exception as well, in case the problem is obvious

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 18:20 --- I bet this is a duplicate of 23211 http://issues.apache.org/bugzilla/show_bug.cgi?id=23211

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 18:38 --- Created an attachment (id=11712) Simpler version of the test case - same URL to reproduce

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:08 --- Created an attachment (id=11713) third attachment with correct path to a servlet

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:22 --- Whatever ;) I won't waste any more time of this issue, that's for sure

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 20:18 --- If crossContext is false then getContext(path_context) would return null. If context is null then trying

DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

2004-06-01 Thread bugzilla
/show_bug.cgi?id=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 29283] New: - Exception: StandardSession.invalidate

2004-05-28 Thread bugzilla
/show_bug.cgi?id=29283 Exception: StandardSession.invalidate Summary: Exception: StandardSession.invalidate Product: Tomcat 4 Version: 4.1.29 Platform: PC OS/Version: Linux Status: NEW Severity: Critical Priority: Other

DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 Thread bugzilla
/show_bug.cgi?id=29283 Exception: StandardSession.invalidate [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 Thread bugzilla
/show_bug.cgi?id=29283 Exception: StandardSession.invalidate [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 Thread bugzilla
/show_bug.cgi?id=29283 Exception: StandardSession.invalidate [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution

DO NOT REPLY [Bug 29283] - Exception: StandardSession.invalidate

2004-05-28 Thread bugzilla
/show_bug.cgi?id=29283 Exception: StandardSession.invalidate --- Additional Comments From [EMAIL PROTECTED] 2004-05-28 21:56 --- Thank you. This does not resolve the my current situation, but at least I better understand the issue. This problem did not occur at our site(s) with version

DO NOT REPLY [Bug 29240] - java.sql.SQLException: Io exception: Connection reset by peer: socket write error

2004-05-27 Thread bugzilla
/show_bug.cgi?id=29240 java.sql.SQLException: Io exception: Connection reset by peer: socket write error [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 29240] New: - java.sql.SQLException: Io exception: Connection reset by peer: socket write error

2004-05-26 Thread bugzilla
/show_bug.cgi?id=29240 java.sql.SQLException: Io exception: Connection reset by peer: socket write error Summary: java.sql.SQLException: Io exception: Connection reset by peer: socket write error Product: Tomcat 4 Version: 4.1.24 Platform

DO NOT REPLY [Bug 22359] - class won't reload automatically after an exception

2004-05-14 Thread bugzilla
/show_bug.cgi?id=22359 class won't reload automatically after an exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-29 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source --- Additional Comments From [EMAIL PROTECTED] 2004-04-29 17:05 --- The exception in the admin log is given at the bottom of this post. However I just did a clean (deleting all files but build.xml) CVS build, so

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-29 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-28 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-28 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-28 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-28 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source --- Additional Comments From [EMAIL PROTECTED] 2004-04-28 22:01 --- What does admin log say? The log should display the exception that's causing the error. The datasource add works for me. The page now displays

DO NOT REPLY [Bug 18488] - it will throw exception when I logout

2004-04-28 Thread bugzilla
/show_bug.cgi?id=18488 it will throw exception when I logout [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-27 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 28524] New: - Exception throw when creating new JNDI data source

2004-04-21 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source Summary: Exception throw when creating new JNDI data source Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-21 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source --- Additional Comments From [EMAIL PROTECTED] 2004-04-21 23:35 --- I think you're getting the error because you have resource-ref in your web.xml but no context datasource definition on either server.xml or context.xml

DO NOT REPLY [Bug 28524] - Exception throw when creating new JNDI data source

2004-04-21 Thread bugzilla
/show_bug.cgi?id=28524 Exception throw when creating new JNDI data source --- Additional Comments From [EMAIL PROTECTED] 2004-04-21 23:51 --- I have confirmed that Amy Roh's workaround works. Thank You. - To unsubscribe, e

DO NOT REPLY [Bug 20136] - SAX parse exception

2004-04-20 Thread bugzilla
/show_bug.cgi?id=20136 SAX parse exception [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution

DO NOT REPLY [Bug 19871] - When above URI is entered Default-Servlet raises Exception

2004-04-18 Thread bugzilla
/show_bug.cgi?id=19871 When above URI is entered Default-Servlet raises Exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread David Cassidy
in ..) If you have a page that does request.getParameter(paramName) and you specify page.jsp?paramName=% The result is an exception report that details what version of tomcat you are running (I've tried this with 4.1.29 and it does make a wonderful exception report!) Anyone seen this before

Autoreply: single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread DirectXtras
+0100 Subject: single percent sign in a parameter causes an exception report detailing tomcat version To: Tomcat Developers List [EMAIL PROTECTED] X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: [EMAIL PROTECTED] From: David Cassidy [EMAIL PROTECTED] Date: Fri, 16 Apr 2004 11:09:42

RE: single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread Shapira, Yoav
List Subject: single percent sign in a parameter causes an exception report detailing tomcat version Guys, We've had a pen test done on one of the apps we look after and they an issue which I'd like a little guidance on ... (Accept that these guys are specifically sending iffy requests to cause

RE: single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread David Cassidy
: Subject: RE: single percent sign in a parameter causes an exception report detailing tomcat version 16/04/2004 13:52

RE: single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread Shapira, Yoav
Hi, still makes a nasty mess on your screen :) That's subjective: I tend to like all the information I can get, but then again I'm a developer. The error pages at least are easily customizable (including in a global way for the tomcat server admin) to include or not include whatever you want.

RE: single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread David Cassidy
causes an exception report detailing tomcat version 16/04/2004 14:16 Please respond

Re: single percent sign in a parameter causes an exception report detailing tomcat version

2004-04-16 Thread jean-frederic clere
in a parameter causes an exception report detailing tomcat version 16/04/2004 14:16 Please respond

<    1   2   3   4   5   6   >