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 14:16

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
.com>cc: Subject: RE: single percent sign in a parameter causes an exception report detailing tomcat version

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

2004-04-16 Thread Shapira, Yoav
April 16, 2004 6:10 AM >To: Tomcat Developers 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 g

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

2004-04-16 Thread DirectXtras
id i3GA9hKt031914; Fri, 16 Apr 2004 11:09:44 +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 PROT

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

2004-04-16 Thread David Cassidy
hacking 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!)

DO NOT REPLY [Bug 28123] - ClientAbortException should default to the description of the wrapped exception

2004-04-06 Thread bugzilla
gzilla/show_bug.cgi?id=28123 ClientAbortException should default to the description of the wrapped exception [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 28123] - ClientAbortException should default to the description of the wrapped exception

2004-04-02 Thread bugzilla
gzilla/show_bug.cgi?id=28123 ClientAbortException should default to the description of the wrapped exception --- Additional Comments From [EMAIL PROTECTED] 2004-04-02 23:56 --- Actually, ClientAbortException.toString will print out the "root-cause" exception. This means th

DO NOT REPLY [Bug 28123] New: - ClientAbortException should default to the description of the wrapped exception

2004-04-01 Thread bugzilla
gzilla/show_bug.cgi?id=28123 ClientAbortException should default to the description of the wrapped exception Summary: ClientAbortException should default to the description of the wrapped exception Product: Tomcat 5 Version: 5.0.19 Platfor

DO NOT REPLY [Bug 27894] - jmx throws exception if TC installation path contains spaces

2004-03-24 Thread bugzilla
gzilla/show_bug.cgi?id=27894 jmx throws exception if TC installation path contains spaces [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 27894] New: - jmx throws exception if TC installation path contains spaces

2004-03-24 Thread bugzilla
gzilla/show_bug.cgi?id=27894 jmx throws exception if TC installation path contains spaces Summary: jmx throws exception if TC installation path contains spaces Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Wind

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

2004-03-21 Thread MagicDraw Support Team
Hello [EMAIL PROTECTED]: Thank you for your inquiry. This is an automated response from MagicDraw support team. We have received your message regarding "DO NOT REPLY [Bug 27829] New: - server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketExce

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

2004-03-21 Thread bugzilla
gzilla/show_bug.cgi?id=27829 server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable Summary: server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Netw

DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-21 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RE

DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-21 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 --- Additional Comments From [EMAIL PROTECTED] 2004-03-21 21:28 --- I think I found the problem. One of the recent changes to Http11Protocol.java added pause() and resume() methods which call log.info() to reco

DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-21 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 --- Additional Comments From [EMAIL PROTECTED] 2004-03-21 17:44 --- Well, then go ahead and fix this. I certainly will not. - To unsubscribe,

DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-21 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-21 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 13499] - Jasper throws an exception on an immediate pageContext.forward()

2004-03-20 Thread bugzilla
gzilla/show_bug.cgi?id=13499 Jasper throws an exception on an immediate pageContext.forward() [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RE

DO NOT REPLY [Bug 13499] - Jasper throws an exception on an immediate pageContext.forward()

2004-03-19 Thread bugzilla
gzilla/show_bug.cgi?id=13499 Jasper throws an exception on an immediate pageContext.forward() [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

Autoreply: DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-18 Thread DirectXtras
:10 - Date: 19 Mar 2004 05:51:10 - Message-ID: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL,

DO NOT REPLY [Bug 27790] - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-18 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 --- Additional Comments From [EMAIL PROTECTED] 2004-03-19 05:51 --- Found a bit more information about the problem: the original exception that triggered the error was java/util/MissingResourceException, with a

DO NOT REPLY [Bug 27790] New: - Exception during shutdown of 5.0.19 on JDK 1.3.1

2004-03-18 Thread bugzilla
gzilla/show_bug.cgi?id=27790 Exception during shutdown of 5.0.19 on JDK 1.3.1 Summary: Exception during shutdown of 5.0.19 on JDK 1.3.1 Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity:

DO NOT REPLY [Bug 13499] - Jasper throws an exception on an immediate pageContext.forward()

2004-03-18 Thread bugzilla
gzilla/show_bug.cgi?id=13499 Jasper throws an exception on an immediate pageContext.forward() [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 27660] - Exception accessing parameters

2004-03-15 Thread bugzilla
gzilla/show_bug.cgi?id=27660 Exception accessing parameters [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 27660] New: - Exception accessing parameters

2004-03-15 Thread bugzilla
gzilla/show_bug.cgi?id=27660 Exception accessing parameters Summary: Exception accessing parameters Product: Tomcat 4 Version: 4.1.30 Platform: All OS/Version: All Status: NEW Severity: Critical Priority:

DO NOT REPLY [Bug 9917] - Exception from admin webapp

2004-03-04 Thread bugzilla
gzilla/show_bug.cgi?id=9917 Exception from admin webapp [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Reso

DO NOT REPLY [Bug 27395] - SOAPMonitor throws exception

2004-03-03 Thread bugzilla
gzilla/show_bug.cgi?id=27395 SOAPMonitor throws exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 27395] New: - SOAPMonitor throws exception

2004-03-02 Thread bugzilla
gzilla/show_bug.cgi?id=27395 SOAPMonitor throws exception Summary: SOAPMonitor throws exception Product: Tomcat 5 Version: 5.0.19 Platform: Macintosh OS/Version: MacOS X Status: NEW Severity: Normal Priority:

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

2004-02-24 Thread bugzilla
gzilla/show_bug.cgi?id=27104 got an exception when testing a simple cluster app [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

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

2004-02-20 Thread bugzilla
gzilla/show_bug.cgi?id=27104 got an exception when testing a simple cluster app Summary: got an exception when testing a simple cluster app Product: Tomcat 5 Version: 5.0.18 Platform: Sun OS/Version: Solaris Status: NEW Severity:

DO NOT REPLY [Bug 27086] - balancer webapp fails (Exception starting filter BalancerFilter)

2004-02-19 Thread bugzilla
gzilla/show_bug.cgi?id=27086 balancer webapp fails (Exception starting filter BalancerFilter) [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 27086] New: - balancer webapp fails (Exception starting filter BalancerFilter)

2004-02-19 Thread bugzilla
gzilla/show_bug.cgi?id=27086 balancer webapp fails (Exception starting filter BalancerFilter) Summary: balancer webapp fails (Exception starting filter BalancerFilter) Product: Tomcat 5 Version: 5.0.18 Platform: PC OS/Version:

DO NOT REPLY [Bug 26436] - Jasper generates code weak against exception in doAfterBody()

2004-02-15 Thread bugzilla
gzilla/show_bug.cgi?id=26436 Jasper generates code weak against exception in doAfterBody() --- Additional Comments From [EMAIL PROTECTED] 2004-02-15 14:15 --- I'm having a similar problem here. When using the TryCatchFinally interface popBody has to be called once more in the

DO NOT REPLY [Bug 22353] - Tomcat crashes with unexpected exception when used with MCVE API

2004-02-13 Thread bugzilla
gzilla/show_bug.cgi?id=22353 Tomcat crashes with unexpected exception when used with MCVE API [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 5998] - Exception hiding when a JspExceptioin is thrown by a tag

2004-02-07 Thread bugzilla
gzilla/show_bug.cgi?id=5998 Exception hiding when a JspExceptioin is thrown by a tag [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RE

DO NOT REPLY [Bug 26436] - Jasper generates code weak against exception in doAfterBody()

2004-01-26 Thread bugzilla
gzilla/show_bug.cgi?id=26436 Jasper generates code weak against exception in doAfterBody() --- Additional Comments From [EMAIL PROTECTED] 2004-01-26 13:19 --- Obviously, we're not going to add try/catch/finally in tag processing. I think this "bug&qu

DO NOT REPLY [Bug 26436] - Jasper generates code weak against exception in doAfterBody()

2004-01-26 Thread bugzilla
gzilla/show_bug.cgi?id=26436 Jasper generates code weak against exception in doAfterBody() [EMAIL PROTECTED] changed: What|Removed |Added Summary|Jasper generates code weak |

DO NOT REPLY [Bug 26436] New: - Jasper generates code weak against exception in doAfterTag()

2004-01-26 Thread bugzilla
gzilla/show_bug.cgi?id=26436 Jasper generates code weak against exception in doAfterTag() Summary: Jasper generates code weak against exception in doAfterTag() Product: Tomcat 4 Version: 4.1.29 Platform: All OS/Versio

Re: Exception in RealmBase

2004-01-08 Thread Mark Woon
seems the code under container==null should be executed when the realm is added via JMX using full object name only. It's using its own object name to figure out its container and calls setRealm to its container. I'm not sure what you mean by "adding your realm" exactly, but

Re: Exception in RealmBase

2004-01-08 Thread Amy Roh
Mark Woon wrote: Hi all, I'm reposting this in the hopes that someone will responsd. I have a custom Realm implementation that extends org.apache.catalina.realm.RealmBase. It used to work in 4.x, but in 5.0.16, I'm getting the following exception on startup: 21:17:29,719 ERROR Real

Exception in RealmBase

2004-01-07 Thread Mark Woon
Hi all, I'm reposting this in the hopes that someone will responsd. I have a custom Realm implementation that extends org.apache.catalina.realm.RealmBase. It used to work in 4.x, but in 5.0.16, I'm getting the following exception on startup: 21:17:29,719 ERROR RealmBase:1092 - Can&

Exception in RealmBase

2004-01-05 Thread Mark Woon
Hi all, I have a custom Realm implementation that extends org.apache.catalina.realm.RealmBase. It used to work in 4.x, but in 5.0.16, I'm getting the following exception on startup: 21:17:29,719 ERROR RealmBase:1092 - Can't register null java.lang.NullPointerExce

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-26 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name [EMAIL PROTECTED] changed: What|Removed |Added Version|

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-26 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name [EMAIL PROTECTED] changed: What|Removed |Added Severity|B

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-26 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-25 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-25 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name --- Additional Comments From [EMAIL PROTECTED] 2003-12-25 20:21 --- Created an attachment (id=9703) Trimmed down testcase: this caused out of bounds exception before the

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-25 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 9980] - exception object is null inside an error page (given certain conditions)

2003-12-23 Thread bugzilla
gzilla/show_bug.cgi?id=9980 exception object is null inside an error page (given certain conditions) [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 25680] - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-22 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name --- Additional Comments From [EMAIL PROTECTED] 2003-12-22 09:07 --- I am extremely glad that the fix is trivial, but I don't like your patch. I also find the explanation of the proble

DO NOT REPLY [Bug 25680] New: - Exception thrown when including a jsp mapped to a custom servlet name

2003-12-21 Thread bugzilla
gzilla/show_bug.cgi?id=25680 Exception thrown when including a jsp mapped to a custom servlet name Summary: Exception thrown when including a jsp mapped to a custom servlet name Product: Tomcat 5 Version: 5.0.16 Platform: PC OS/V

DO NOT REPLY [Bug 16701] - No exception if jsp:include fails

2003-12-15 Thread bugzilla
gzilla/show_bug.cgi?id=16701 No exception if jsp:include fails [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-12-11 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-12-11 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread [EMAIL PROTECTED] changed: What|Removed |Added Se

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-12-11 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 25374] - SEVERE: Exception in acceptSocket

2003-12-09 Thread bugzilla
gzilla/show_bug.cgi?id=25374 SEVERE: Exception in acceptSocket --- Additional Comments From [EMAIL PROTECTED] 2003-12-09 22:43 --- The commons-logging issue should not related, but is an important fix. The problem was that the context classloader was not properly reset at the end of the r

DO NOT REPLY [Bug 25374] - SEVERE: Exception in acceptSocket

2003-12-09 Thread bugzilla
gzilla/show_bug.cgi?id=25374 SEVERE: Exception in acceptSocket [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 25374] - SEVERE: Exception in acceptSocket

2003-12-09 Thread bugzilla
gzilla/show_bug.cgi?id=25374 SEVERE: Exception in acceptSocket --- Additional Comments From [EMAIL PROTECTED] 2003-12-09 22:35 --- I did notice on bug 22701 that there was a patch issued for 4.1.27 and that subsequent versions (.28 and .29) are supposed to have the fix built-in but that is

DO NOT REPLY [Bug 25374] - SEVERE: Exception in acceptSocket

2003-12-09 Thread bugzilla
gzilla/show_bug.cgi?id=25374 SEVERE: Exception in acceptSocket --- Additional Comments From [EMAIL PROTECTED] 2003-12-09 22:30 --- System Info: SuSE Linux 8.1 Sun Java 1.4.1_01-b01 Tomcat 4.1.27 (using both SSL and Non-SSL connectors on 8XXX ports) SAPDB 7.3.0.34 Struts 1.0 (I think...may

DO NOT REPLY [Bug 25374] - SEVERE: Exception in acceptSocket

2003-12-09 Thread bugzilla
gzilla/show_bug.cgi?id=25374 SEVERE: Exception in acceptSocket --- Additional Comments From [EMAIL PROTECTED] 2003-12-09 22:24 --- Created an attachment (id=9472) stack trace - To unsubscribe, e-mail: [EMAIL PROTECTE

DO NOT REPLY [Bug 25374] New: - SEVERE: Exception in acceptSocket

2003-12-09 Thread bugzilla
gzilla/show_bug.cgi?id=25374 SEVERE: Exception in acceptSocket Summary: SEVERE: Exception in acceptSocket Product: Tomcat 4 Version: 4.1.27 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority:

DO NOT REPLY [Bug 25273] New: - Exception processing TLD at resource path - say where it is really looking for this file

2003-12-07 Thread bugzilla
gzilla/show_bug.cgi?id=25273 Exception processing TLD at resource path - say where it is really looking for this file Summary: Exception processing TLD at resource path - say where it is really looking for this file Product: Tomcat 4 Version:

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

2003-12-04 Thread bugzilla
gzilla/show_bug.cgi?id=25217 Catalina ContextConfig Exception Summary: Catalina ContextConfig Exception Product: Tomcat 4 Version: 4.1.29 Platform: PC OS/Version: Windows XP Status: NEW Severity: Blocker Priority:

DO NOT REPLY [Bug 23379] - CoyoteAdapter An exception or error occurred in the container during the request processing

2003-12-04 Thread bugzilla
gzilla/show_bug.cgi?id=23379 CoyoteAdapter An exception or error occurred in the container during the request processing --- Additional Comments From [EMAIL PROTECTED] 2003-12-04 14:32 --- May be related to #23914. --

DO NOT REPLY [Bug 23379] - CoyoteAdapter An exception or error occurred in the container during the request processing

2003-12-04 Thread bugzilla
gzilla/show_bug.cgi?id=23379 CoyoteAdapter An exception or error occurred in the container during the request processing --- Additional Comments From [EMAIL PROTECTED] 2003-12-04 14:35 --- May be realted to bug 23914. --

Uploading large files - out of memory exception

2003-12-01 Thread Fabrizio Nesti
Dear tomcat developers, I've noticed a problem while uploading files with tomcat 4.1.x. - When uploading large files (say larger than 10MB) tomcat throws an out of memory exception. - The problem can be avoided raising the memory allocation (as found in other similar messages, -Xm

DO NOT REPLY [Bug 5998] - Exception hiding when a JspExceptioin is thrown by a tag

2003-11-27 Thread bugzilla
gzilla/show_bug.cgi?id=5998 Exception hiding when a JspExceptioin is thrown by a tag [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-16 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread [EMAIL PROTECTED] changed: What|Removed |Added Severity

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-14 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 24581] - File not found exception while starting catalina

2003-11-14 Thread bugzilla
gzilla/show_bug.cgi?id=24581 File not found exception while starting catalina [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-14 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-10 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 21:05 --- Regarding the proposed fixes, I would argue that it would be helpful to include a log statement

DO NOT REPLY [Bug 24581] New: - File not found exception while starting catalina

2003-11-10 Thread bugzilla
gzilla/show_bug.cgi?id=24581 File not found exception while starting catalina Summary: File not found exception while starting catalina Product: Tomcat 4 Version: 4.1.29 Platform: Other OS/Version: Windows NT/2K Status: NEW Se

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-10 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 19:51 --- With TC 5, there's no possible way the background thread can die like this. All it will do

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-10 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 19:46 --- Created an attachment (id=9033) Patch for TC5 to fix th

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-10 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 19:46 --- Created an attachment (id=9032) Patch for TC4 to fix th

DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-09 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 20:21 --- Present in TC4 and TC5. I have submitted patches to tomcat-dev. BTW, the code is not shared as the

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

2003-11-04 Thread bugzilla
gzilla/show_bug.cgi?id=18650 Exception while processing a JAR file --- Additional Comments From [EMAIL PROTECTED] 2003-11-04 20:36 --- The requirement that $CATALINA_BASE/temp must exist for temp files came somewhere between 4.0.3 and 4.1.27. I agree that it's now a necessary direct

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

2003-11-04 Thread bugzilla
gzilla/show_bug.cgi?id=18650 Exception while processing a JAR file --- Additional Comments From [EMAIL PROTECTED] 2003-11-04 07:27 --- This is not a valid test case. "temp" is the JDK temp dir, and as such is needed to be a

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

2003-11-03 Thread bugzilla
gzilla/show_bug.cgi?id=18650 Exception while processing a JAR file --- Additional Comments From [EMAIL PROTECTED] 2003-11-03 23:46 --- Here's a valid test case for you, as simple as it gets: 1. Install tomcat 4.1.27. 2. Delete, rename or remove write privileges on $CATALINA_BASE/tem

DO NOT REPLY [Bug 24368] New: - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread

2003-11-03 Thread bugzilla
gzilla/show_bug.cgi?id=24368 Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread Summary: Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread Product: To

DO NOT REPLY [Bug 23908] - Occasional Access Violation Exception in the VM when sockets don't bind

2003-10-20 Thread bugzilla
gzilla/show_bug.cgi?id=23908 Occasional Access Violation Exception in the VM when sockets don't bind [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 23908] - Occasional Access Violation Exception in the VM when sockets don't bind

2003-10-18 Thread bugzilla
gzilla/show_bug.cgi?id=23908 Occasional Access Violation Exception in the VM when sockets don't bind [EMAIL PROTECTED] changed: What|Removed |Added Summary|Occasional Acces

DO NOT REPLY [Bug 23908] New: - Occasional Access Violation Exception in the native code of the VM

2003-10-18 Thread bugzilla
gzilla/show_bug.cgi?id=23908 Occasional Access Violation Exception in the native code of the VM Summary: Occasional Access Violation Exception in the native code of the VM Product: Tomcat 5 Version: 5.0.12 Platform: PC OS/Version:

DO NOT REPLY [Bug 23841] New: - More specific error message to "org.apache.jasper.JasperException: Exception thrown by getter for property ..."

2003-10-15 Thread bugzilla
gzilla/show_bug.cgi?id=23841 More specific error message to "org.apache.jasper.JasperException: Exception thrown by getter for property ..." Summary: More specific error message to "org.apache.jasper.JasperException: Exception thrown by

DO NOT REPLY [Bug 23818] - 5.0.13 Startup Exception

2003-10-14 Thread bugzilla
gzilla/show_bug.cgi?id=23818 5.0.13 Startup Exception [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Reso

DO NOT REPLY [Bug 23818] - 5.0.13 Startup Exception

2003-10-14 Thread bugzilla
gzilla/show_bug.cgi?id=23818 5.0.13 Startup Exception --- Additional Comments From [EMAIL PROTECTED] 2003-10-14 16:55 --- If the attached files are insufficient please let mw know what else you need. - To unsubscribe,

DO NOT REPLY [Bug 23818] - 5.0.13 Startup Exception

2003-10-14 Thread bugzilla
gzilla/show_bug.cgi?id=23818 5.0.13 Startup Exception --- Additional Comments From [EMAIL PROTECTED] 2003-10-14 16:55 --- Created an attachment (id=8570) webapp startup file. - To unsubscribe, e-mail: [EMAIL PROTECTE

DO NOT REPLY [Bug 23818] - 5.0.13 Startup Exception

2003-10-14 Thread bugzilla
gzilla/show_bug.cgi?id=23818 5.0.13 Startup Exception --- Additional Comments From [EMAIL PROTECTED] 2003-10-14 16:54 --- Created an attachment (id=8569) Thisnis the tomcat startup file. - To unsubscribe, e-mail: [EMAIL PRO

DO NOT REPLY [Bug 23818] New: - 5.0.13 Startup Exception

2003-10-14 Thread bugzilla
gzilla/show_bug.cgi?id=23818 5.0.13 Startup Exception Summary: 5.0.13 Startup Exception Product: Tomcat 5 Version: 5.0.13 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 22869] - under liveDeploy a webapp may throw an exception on restart. if some files are soft links

2003-10-01 Thread bugzilla
gzilla/show_bug.cgi?id=22869 under liveDeploy a webapp may throw an exception on restart. if some files are soft links --- Additional Comments From [EMAIL PROTECTED] 2003-10-01 10:29 --- I put the updated FileDirContext.class etc under *common*/classes/... etc. since it needs to be u

DO NOT REPLY [Bug 23482] - Sequential stopping and re-starting of web application leads to out of memory exception

2003-09-29 Thread bugzilla
gzilla/show_bug.cgi?id=23482 Sequential stopping and re-starting of web application leads to out of memory exception [EMAIL PROTECTED] changed: What|Removed |Added Severity|Cr

DO NOT REPLY [Bug 23482] New: - Sequential stopping and re-starting of web application leads to out of memory exception

2003-09-29 Thread bugzilla
gzilla/show_bug.cgi?id=23482 Sequential stopping and re-starting of web application leads to out of memory exception Summary: Sequential stopping and re-starting of web application leads to out of memory exception Product: Tomcat 4 Version:

DO NOT REPLY [Bug 22869] - under liveDeploy a webapp may throw an exception on restart. if some files are soft links

2003-09-25 Thread bugzilla
gzilla/show_bug.cgi?id=22869 under liveDeploy a webapp may throw an exception on restart. if some files are soft links --- Additional Comments From [EMAIL PROTECTED] 2003-09-25 18:59 --- I built a standalone FileDirContext.class based on the original java file. In the release method I com

DO NOT REPLY [Bug 22869] - under liveDeploy a webapp may throw an exception on restart. if some files are soft links

2003-09-25 Thread bugzilla
gzilla/show_bug.cgi?id=22869 under liveDeploy a webapp may throw an exception on restart. if some files are soft links --- Additional Comments From [EMAIL PROTECTED] 2003-09-25 15:58 --- I would like to add that I am experiencing this bug as well. In my case I do not have liveDeploy enabl

DO NOT REPLY [Bug 22869] - under liveDeploy a webapp may throw an exception on restart. if some files are soft links

2003-09-25 Thread bugzilla
gzilla/show_bug.cgi?id=22869 under liveDeploy a webapp may throw an exception on restart. if some files are soft links [EMAIL PROTECTED] changed: What|Removed |Added Severity

DO NOT REPLY [Bug 23379] - CoyoteAdapter An exception or error occurred in the container during the request processing

2003-09-24 Thread bugzilla
gzilla/show_bug.cgi?id=23379 CoyoteAdapter An exception or error occurred in the container during the request processing [EMAIL PROTECTED] changed: What|Removed |Added Stat

DO NOT REPLY [Bug 23379] New: - CoyoteAdapter An exception or error occurred in the container during the request processing

2003-09-23 Thread bugzilla
gzilla/show_bug.cgi?id=23379 CoyoteAdapter An exception or error occurred in the container during the request processing Summary: CoyoteAdapter An exception or error occurred in the container during the request processing Product: Tomcat 4 Version:

DO NOT REPLY [Bug 23325] - displaying data source for a context resource results in exception

2003-09-22 Thread bugzilla
gzilla/show_bug.cgi?id=23325 displaying data source for a context resource results in exception [EMAIL PROTECTED] changed: What|Removed |Added Summary|displaying data source

<    1   2   3   4   5   6   7   >