DO NOT REPLY [Bug 24478] - Incorrect usage of perl
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24478. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24478 Incorrect usage of perl [EMAIL PROTECTED] changed: What|Removed |Added Severity|Normal |Enhancement --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 11:23 --- I am no Unix or Linux expert but as far as I know the use of double quotes to overcome the possible use of spaces in paths and filenames is valid. I checked this with tomcat-dev list as well as some quick google research eg http://catless.ncl.ac.uk/Risks/21.79.html#subj3 The issue of always using perl is a valid one but extending support to include non-perl scipts is an enhancement. I am therefore changing the severity of this issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24510] - Odd back button behavior in a multi-frame environment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24510 Odd back button behavior in a multi-frame environment [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 11:33 --- This is a browser issue rather than a tomcat issue, therefore I am resolving this bug. If you still have some queries, the tomcat-user list is the best place to get the answers you need. If, after further research, you believe a tomcat bug (eg non-spec compliant behaviour) is the root cause please feel free to re-open this bug. In this case please provide the simpliet test case (ideally as a .war) that reproduces the error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bug report for Tomcat 3 [2003/11/09]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 258|Unc|Nor|2000-11-27|response.SendRedirect() resets/destroys Cookies th| | 2350|Ver|Nor|2001-06-27|ServletConfig.getInitParameter() requires url-patt| | 2478|Opn|Cri|2001-07-06|Passing Session variables between JSP's and Servle| | 4551|Opn|Nor|2001-10-31|Ctx( /tt01 ): IOException in: R( /tt01 + /com/abc/| | 4980|New|Min|2001-11-20|Startup message indicates incorrect log file | | 4994|New|Nor|2001-11-21|Tomcat needs a mechanism for clean and certain shu| | 5064|New|Cri|2001-11-25|Socket write error when include files is more than| | 5108|New|Maj|2001-11-26|Docs for Tomcat 3.2.x appear to be for Tomcat 3.3 | | 5137|New|Nor|2001-11-27|Null pointer in class loader after attempting to r| | 5160|Unc|Maj|2001-11-28|'IllegalStateException' | | 5331|New|Nor|2001-12-09|getPathInfo vs URL normalization | | 5510|New|Blk|2001-12-19|How to call ejb deployed in JBoss from Tomcat serv| | 5756|New|Nor|2002-01-08|jspc.bat exits with wrong ERRORLEVEL | | 5797|New|Nor|2002-01-10|UnCatched ? StringIndexOutOfBoundsException: Strin| | 6027|New|Maj|2002-01-25|Tomcat Automatically shuts down as service | | 6168|New|Blk|2002-02-01|IllegalStateException | | 6451|New|Cri|2002-02-14|Stackoverflow | | 6478|New|Enh|2002-02-14|Default Tomcat Encoding | | 6488|Ver|Maj|2002-02-15|Error: 304. Apparent bug in default ErrorHandler c| | 6648|New|Nor|2002-02-25|jakarta-servletapi build with java 1.4 javadoc err| | 6702|New|Cri|2002-02-27|win 2k services not working | | 6796|New|Cri|2002-03-01|Tomcat dies periodically | | 6989|New|Maj|2002-03-08|Unable to read tld file during parallel JSP compil| | 7008|Opn|Maj|2002-03-10|facade.HttpServletRequestFacade.getParameter(HttpS| | 7013|New|Cri|2002-03-10|Entering a servlet path with non-ISO8859-1 charact| | 7227|New|Nor|2002-03-19|error-code directive don't work | | 7236|New|Blk|2002-03-19|Permission denied to do thread.stop | | 7626|New|Nor|2002-03-29|classloader not working properly | | 7652|New|Cri|2002-04-01|Tomcat stalls periodically| | 7762|New|Enh|2002-04-05|stdout logfile handling | | 7785|New|Blk|2002-04-06|tomcat bug in context reloading | | 7789|New|Maj|2002-04-06|JSP Cookie Read/Write Fails With DNS Names| | 7863|New|Maj|2002-04-09|I have a problem when running Tomcat with IIS | | 8154|New|Nor|2002-04-16|logrotate script in RPM rotates non-existing file | | 8187|New|Cri|2002-04-17|Errors when Tomcat used with MS Access database | | 8239|New|Cri|2002-04-18|Resource temporary unavailable| | 8263|New|Cri|2002-04-18|url-pattern easy to circumvent| | 8634|New|Nor|2002-04-30|no way to specify different modules.xml file | | 8992|New|Blk|2002-05-10|IE6/XP: Limitation of POST Area within HTTP reques| | 9086|New|Enh|2002-05-14|NPE org.apache.tomcat.core.ServerSession.setAttrib| | 9250|New|Maj|2002-05-20|outOfMemoryError | | 9367|New|Maj|2002-05-23|HttpSessionBindingEvent not thrown for HttpSession| | 9390|New|Nor|2002-05-24|jasper compilation error in tomcat| | 9480|New|Nor|2002-05-29|Data connection pooling | | 9607|New|Maj|2002-06-04|precompile JSP| | 9737|New|Nor|2002-06-10|ArrayIndexOutOfBoundsException when sending just p| |1|New|Cri|2002-06-19|IOException Broken Pipe when authenticating JDBCRe| |10039|New|Nor|2002-06-20|TimeStamp will not work correctly.| |10047|New|Cri|2002-06-20|IllegalStateException | |10202|New|Maj|2002-06-25|Tomcat is not responding in time | |10357|Unc|Blk|2002-06-30|java.lang.IllegalArgumentException: Short Read|
Bug report for Tomcat 4 [2003/11/09]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 218|Unc|Nor|2000-11-02|IIS in-process tomcat BugRat Report#333 | | 3098|Opn|Maj|2001-08-11|RequestDispatcher on relative (to request path) | | 3614|Opn|Nor|2001-09-14|bug in manager webapp | | 3755|Opn|Nor|2001-09-20|freezes at shutdown | | 3888|Opn|Blk|2001-09-30|WebappClassLoader: Lifecycle error : CL stopped | | 4091|Opn|Nor|2001-10-11|custom host with unpackWARs=true don't expand wa| | 4138|Opn|Nor|2001-10-12|Processor threads have inconsistent ClassLoader st| | 4350|Ass|Nor|2001-10-22|SSLAuthenticator did not associate SSO session| | 4352|Ass|Nor|2001-10-22|JDBCRealm does not work with CLIENT-CERT auth-meth| | 5329|New|Nor|2001-12-08|NT Service exits startup before Tomcat is finished| | 5598|Opn|Maj|2001-12-27|(JSP Problem) RequestDispatcher doesn't include HT| | 5704|Ass|Maj|2002-01-05|CgiServlet corrupting images? | | 5715|Opn|Nor|2002-01-07|response.setContentType() in Filter.doFilter not c| | 5759|Opn|Maj|2002-01-09|CGI servlet mapping by extension *.cgi does not wo| | 5762|Opn|Maj|2002-01-09|CGI servlet misses to include port number in HTTP_| | 5795|New|Enh|2002-01-10|Catalina Shutdown relies on localhost causing prob| | 5829|New|Enh|2002-01-13|StandardManager needs to cope with sessions throwi| | 5858|New|Enh|2002-01-15|Add tomcat dir to java.library.path | | 5952|Opn|Nor|2002-01-22|Refence to $JAVACMD in tomcat.conf incorrect in R| | 5985|New|Enh|2002-01-23|Tomcat should perform a more restrictive validatio| | 6218|Opn|Nor|2002-02-04|Relative links broken for servlets| | 6229|New|Enh|2002-02-04|Need way to specify where to write catalina.out | | 6399|New|Nor|2002-02-12|unknown protocol: https | | 6408|New|Enh|2002-02-12|Starting tomcat from a cygwin bash shell using 'st| | 6582|New|Min|2002-02-20|Sample code does not match behavior | | 6600|Opn|Enh|2002-02-20|enodeURL adds 'jsession' when 'isRequestedSessionI| | 6614|New|Enh|2002-02-21|Have Bootstrap and StandardClassLoader use the sam| | 6649|New|Nor|2002-02-25|jakarta-servletapi-4 build using java 1.4 javadoc | | 6659|New|Nor|2002-02-25|HttpUtils.getRequestURL gives incorrect URL with w| | 6671|New|Enh|2002-02-25|Simple custom tag example uses old declaration sty| | 7043|New|Enh|2002-03-12|database user and password for JDBC Based Store | | 7080|New|Maj|2002-03-13|Interbase JDBCRealm - Bug # 5564 - Have a safe fix| | 7190|New|Nor|2002-03-18|GenericServlet spurious log's in init(), destroy()| | 7207|New|Nor|2002-03-18|Redeployment Problem under Tomcat 4.0.2 | | 7360|New|Nor|2002-03-22|res-sharing-scope not supported | | 7366|New|Enh|2002-03-22|ISAPI Redirector Replacement | | 7374|New|Enh|2002-03-22|Apache Tomcat/4.0.1 message on standard output| | 7506|New|Nor|2002-03-27|Reading InputStream returned in the following sena| | 7571|New|Nor|2002-03-28|DataInputStream readLong() Problem| | 7588|New|Nor|2002-03-28|Session cannot be established if there are multipl| | 7676|New|Enh|2002-04-02|Allow name property to use match experssions in h| | 7689|New|Min|2002-04-02|Performance problem with Xerces parser| | 7702|New|Enh|2002-04-03|[PATCH] Speed up Tomcat a tiny bit| | 7723|New|Enh|2002-04-03|[patch] additional factory for org.apache.naming.f| | 7831|New|Nor|2002-04-08|[PATCH] JNDIRealm does not work with CLIENT-CERT a| | 7880|Ver|Cri|2002-04-09|If a TLV flags flags an error during the translati| | 8026|New|Enh|2002-04-12|Exceptions in StandardHostDeployer.addChild are lo| | 8079|New|Enh|2002-04-15|Tomcat cannot start if appBase directory is access| | 8100|New|Maj|2002-04-15|Session Tracking and HttpURLConnection| | 8200|New|Nor|2002-04-17|include (PageContext) does not throw IOException i| | 8217|New|Maj|2002-04-17|Documentation references workers. prefix| |
Bug report for Watchdog [2003/11/09]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=CriticalMAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | | 278|Unc|Nor|2000-12-04|Bug in GetParameterValuesTestServlet.java file Bug| | 279|Unc|Nor|2000-12-04|Logical Error in GetParameterValuesTestServlet Bug| | 469|Unc|Nor|2001-01-17|in example-taglib.tld urn should be uri BugRat| | 470|Unc|Nor|2001-01-17|FAIL positiveForward.jsp and positiveInclude.jsp B| | 9634|New|Enh|2002-06-05|No tests exist for ServletContext.getResourcePaths| |10703|New|Enh|2002-07-11|Need to test getRequestURI after RequestDispatcher| |11336|New|Enh|2002-07-31|Test wrapped path methods with RD.foward()| |11663|New|Maj|2002-08-13|JSP precompile tests rely on Jasper specific behav| |11664|New|Maj|2002-08-13|A sweep is needed of all Watchdog 4.0 tag librarie| |11665|New|Maj|2002-08-13|ServletToJSPErrorPageTest and ServletToServletErro| |11666|New|Maj|2002-08-13|SetBufferSize_1TestServlet is invalid.| |14004|New|Maj|2002-10-28|Incorrent behaviour of all attribute-related lifec| |15504|New|Nor|2002-12-18|JSP positiveGetValues test relies on order preserv| +-+---+---+--+--+ | Total 13 bugs | +---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why is mod_jk distributed both as 2.0.2 and 2.0.4?
Hi! How come this confusion about the latest version of mod_jk2? With the jakarta-tomcat-connectors-4.1.2X, a mod_jk2 version 2.0.4 is distributed. With http://www.apache.org/dist/jakarta/tomcat-connectors/jk2/source/jakarta-tom cat-connectors-jk2-src-current.tar.gz, the version is 2.0.2. Which one is really current? Why this confusion? Regards, Palle Girgensohn FreeBSD mod_jk port maintainer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why is mod_jk distributed both as 2.0.2 and 2.0.4?
-Original Message- From: Palle Girgensohn Hi! How come this confusion about the latest version of mod_jk2? With the jakarta-tomcat-connectors-4.1.2X, a mod_jk2 version 2.0.4 is distributed. With http://www.apache.org/dist/jakarta/tomcat-connectors/jk2/source/jakarta-tom cat-connectors-jk2-src-current.tar.gz, the version is 2.0.2. Which one is really current? Why this confusion? I've bumped the version to 2.0.4, (perhaps better would be 2.1.0). The jk2 that is in the cvs is highly experimental, cause we are using apr/apr-util as mandatory. Since 2.0.3 was never released (or will be), stay with 2.0.2 for a while. MT. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24538] New: - JasperException: file.jsp(x,y) equal symbol expected refers to incorrect location
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24538. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24538 JasperException: file.jsp(x,y) equal symbol expected refers to incorrect location Summary: JasperException: file.jsp(x,y) equal symbol expected refers to incorrect location Product: Tomcat 4 Version: 4.1.27 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] With a jsp file containing an unknown error, the following exception is thrown: org.apache.jasper.JasperException: /WEB-INF/jsp/policy/policydetail.jsp(451,34) equal symbol expected at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:428) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:126) at org.apache.jasper.compiler.Parser.parseAttribute(Parser.java:169) at org.apache.jasper.compiler.Parser.parseAttributes(Parser.java:136) at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:718) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:804) at org.apache.jasper.compiler.Parser.parseBody(Parser.java:833) at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:753) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:804) at org.apache.jasper.compiler.Parser.parseBody(Parser.java:833) at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:753) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:804) at org.apache.jasper.compiler.Parser.parseBody(Parser.java:833) at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:753) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:804) at org.apache.jasper.compiler.Parser.parseBody(Parser.java:833) at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:753) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:804) at org.apache.jasper.compiler.Parser.parse(Parser.java:122) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:199) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:153) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:227) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:369) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) In the original jsp, the line and column 451, 34 points at: 451: TR 452: TD style=white-space: nowrap; text-align: leftbean:message key=policy.text.reinsureadmin /nbsp;/TD 453: TD style=white-space: nowrap; text-align: left colspan=1 454: bean:write name=form property=%=\reinsureAdmins[\ + index + \]\% filter=true /% 455: /TD As can be seen, line 451 column 34 is not part of a JSP tag. In addition, the error message equals symbol expected is so short as to be meaningless (it would only make sense if 451/34 pointed at as JSP tag without an =, which in this case it does not). Adding some context to the exception error message will go a long way to assist a devloper track down jsp errors. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24385] - text conversion fails with jsp:forward/param on linux server
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24385. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24385 text conversion fails with jsp:forward/param on linux server [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 19:33 --- I have tested TC4-Head and TC5-Head on windows and your test case passes. Given the lack of clarity in the JSP1.2 spec and that setting the request encoding works for you in TC4 I am closing this bug as worksforme. Please re- open it if you find the problem still exists in TC5 on the linux/windows combination. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24368] - Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager thread
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24368. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/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 logic between the classes is slightly different. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PATCH Bug24368
Please find below patches to catch an unhandled exception as reported in bug
24368. I have included patches for TC4 and TC5. The TC4 patch also includes
removing some unused imports (thanks to Eclipse :) )
Grateful if one of the committers could apply them.
Thanks,
Mark
TC4 patch follows:
Index:
catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/se
ssion/PersistentManagerBase.java,v
retrieving revision 1.13
diff -u -r1.13 PersistentManagerBase.java
---
catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java 11
Feb 2003 11:54:12 - 1.13
+++ catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java 9
Nov 2003 20:07:49 -
@@ -66,30 +66,12 @@
import java.beans.PropertyChangeEvent;
import java.beans.PropertyChangeListener;
-import java.beans.PropertyChangeSupport;
-import java.io.BufferedInputStream;
-import java.io.BufferedOutputStream;
-import java.io.File;
-import java.io.FileInputStream;
-import java.io.FileNotFoundException;
-import java.io.FileOutputStream;
-import java.io.InputStream;
import java.io.IOException;
-import java.io.ObjectInputStream;
-import java.io.ObjectOutputStream;
-import java.io.ObjectStreamClass;
-import java.util.ArrayList;
-import java.util.Iterator;
-import javax.servlet.ServletContext;
import org.apache.catalina.Container;
import org.apache.catalina.Context;
-import org.apache.catalina.Globals;
import org.apache.catalina.Lifecycle;
-import org.apache.catalina.LifecycleEvent;
import org.apache.catalina.LifecycleException;
import org.apache.catalina.LifecycleListener;
-import org.apache.catalina.Loader;
-import org.apache.catalina.Manager;
import org.apache.catalina.Session;
import org.apache.catalina.Store;
import org.apache.catalina.util.LifecycleSupport;
@@ -897,7 +879,11 @@
StandardSession session = (StandardSession) sessions[i];
if (!session.isValid())
continue;
-session.expire();
+try {
+session.expire();
+} catch (Throwable t) {
+;
+}
}
}
TC5 patch follows:
Index:
catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/catali
na/session/PersistentManagerBase.java,v
retrieving revision 1.11
diff -u -r1.11 PersistentManagerBase.java
--- catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java 8
Sep 2003 15:25:18 - 1.11
+++ catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java 9
Nov 2003 20:02:31 -
@@ -996,7 +996,11 @@
StandardSession session = (StandardSession) sessions[i];
if (!session.isValid())
continue;
-session.expire();
+try {
+session.expire();
+} catch (Throwable t) {
+;
+}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.0.14 Welcome File Broken?
I set up 5.0.14 w/ a welcome file that is a mapped servlet, and the mapped resource is not returned as expected. I think this is a bug: servlet servlet-nameViewCal/servlet-name servlet-classcom.mhsoftware.cdaily.servlet.ViewCal/servlet-class /servlet servlet-mapping servlet-nameViewCal/servlet-name url-pattern/ViewCal.html/url-pattern /servlet-mapping welcome-file-list welcome-fileViewCal.html/welcome-file /welcome-file-list From the specification: SRV 9.10 If a web container receives a valid partial request, the web container must examine the welcome file list defined in the deployment descriptor. The welcome file list is an ordered list of partial URLs with no trailing or leading /. The web server must append each welcome file in the order specified in the deployment descriptor to the partial request and check whether a resource in the WAR is mapped to that request URI. George Sexton MH Software, Inc. Voice: 303 438 9585 http://www.mhsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.0.14 Welcome File Broken? - NOT
Oops. That was really dumb of me. The welcome file list was commented out. I have really got to stop using VI to edit files... -Original Message- From: George Sexton [mailto:[EMAIL PROTECTED] Sent: Sunday, November 09, 2003 2:58 PM To: [EMAIL PROTECTED] Subject: Tomcat 5.0.14 Welcome File Broken? I set up 5.0.14 w/ a welcome file that is a mapped servlet, and the mapped resource is not returned as expected. I think this is a bug: servlet servlet-nameViewCal/servlet-name servlet-classcom.mhsoftware.cdaily.servlet.ViewCal/servlet-class /servlet servlet-mapping servlet-nameViewCal/servlet-name url-pattern/ViewCal.html/url-pattern /servlet-mapping welcome-file-list welcome-fileViewCal.html/welcome-file /welcome-file-list From the specification: SRV 9.10 If a web container receives a valid partial request, the web container must examine the welcome file list defined in the deployment descriptor. The welcome file list is an ordered list of partial URLs with no trailing or leading /. The web server must append each welcome file in the order specified in the deployment descriptor to the partial request and check whether a resource in the WAR is mapped to that request URI. George Sexton MH Software, Inc. Voice: 303 438 9585 http://www.mhsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23853] - No MBean description for DatasourceRealm presented in org.apache.catalina.mbeans.mbeans-descriptor.xml.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23853. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23853 No MBean description for DatasourceRealm presented in org.apache.catalina.mbeans.mbeans-descriptor.xml. --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 22:16 --- Bug also exists in 4.1.29. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24283] - Wrong result in request.getPathInfo() using 2-byte Unicode characters
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24283. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24283 Wrong result in request.getPathInfo() using 2-byte Unicode characters [EMAIL PROTECTED] changed: What|Removed |Added Version|4.1.27 |4.1.29 --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 23:00 --- Checked with latest TC4-HEAD and issue is still present. NB This issue is not present in TC5. Can't promise that a fix will be viable in TC4. Non US-ascii characters in URLs (and quite a few other places :( ) causes all sorts of problems. Fixing this may cause a number of regression issues. I'll update the bug report when I have an answer. Your best bet may be a move to TC5 if this bug is a major issue for you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23853] - No MBean description for DatasourceRealm presented in org.apache.catalina.mbeans.mbeans-descriptor.xml.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23853. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23853 No MBean description for DatasourceRealm presented in org.apache.catalina.mbeans.mbeans-descriptor.xml. --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 23:13 --- Created an attachment (id=9012) Patch against 4.1.29 version of mbean-descriptors.xml (catalina.jar) to add DataSourceRealm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24545] New: - DataSourceRealm cannot see JNDI DataSource defined within a Context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545 DataSourceRealm cannot see JNDI DataSource defined within a Context Summary: DataSourceRealm cannot see JNDI DataSource defined within a Context Product: Tomcat 4 Version: 4.1.29 Platform: PC URL: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/realm- howto.html#DataSourceRealm OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Catalina:Modules AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When defining a Realm withing a Context (in an xml fragment in the webapps directory), I can only seem to use a JNDI DataSource defined in the GlobalNamingResources section of server.xml. If a Resource and ResourceParams section are defined withing the Context where I use the DataSourceRealm, JNDI lookups fail. DataSourceRealm cannot find them. I believe this to be a defect in the way that DataSourceRealms.open() is written. It uses ServerFactory.getServer() to get the Server object and it's global naming context. It seems like there should be a way to get a more local JNDI naming context where the webapp-Context-defined Resource will be visible. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24545] - DataSourceRealm cannot see JNDI DataSource defined within a Context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545 DataSourceRealm cannot see JNDI DataSource defined within a Context --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 05:41 --- Created an attachment (id=9015) Proposed patch to use an actual InitialContext to look up the JNDI DataSource - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24545] - DataSourceRealm cannot see JNDI DataSource defined within a Context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545 DataSourceRealm cannot see JNDI DataSource defined within a Context [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 05:42 --- Sorry, but this is 100% normal. This will not be fixed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24545] - DataSourceRealm cannot see JNDI DataSource defined within a Context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545 DataSourceRealm cannot see JNDI DataSource defined within a Context --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 05:49 --- IMHO, DataSourceRealm should use an InitialContext to look up its JNDI DataSource (see patch). Current implementation jumps directly to the server's global naming context (via call to server.getGlobalNamingContext()). If you still want to, you can use a globally defined DS via a ResourceLink element. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24545] - DataSourceRealm cannot see JNDI DataSource defined within a Context
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24545 DataSourceRealm cannot see JNDI DataSource defined within a Context --- Additional Comments From [EMAIL PROTECTED] 2003-11-10 05:53 --- No, the realm is a container component (which is usually not defined at the context level), and as such should only see container specific datasources. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24554] New: - RequestDispatcher.include() operation erratic
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24554.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24554
RequestDispatcher.include() operation erratic
Summary: RequestDispatcher.include() operation erratic
Product: Tomcat 5
Version: 5.0.14
Platform: Other
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Servlet JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I have a web application that performs:
RequestDispatcher rd=req.getRequestDispatcher(OutputCurrentWeek.html);
if (rd==null) {
WebApp.log(Error getting RequestDispatcher for Include in
ViewCal!,new Exception());
} else {
rd.include(req,res);
}
When the context is not root (i.e. /calendar) the code executes normally and the
included servlet is displayed.
When the context is a ROOT context, the output of the included servlet is not
created, even though the RequestDispatcher returned is not null.
When testing under Tomcat 4.1.29, the code worked with ROOT and non-ROOT contexts.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
