BodyContentImpl performance proposal
I've been looking at the code for this class and noticed that the scheme for growing the buffer size is pretty inefficient. Basically it has an 8K buffer and when that buffer is exceeded, it allocates a new buffer 8K bigger and arraycopy's the old buffer into it. In a tag with a large body (say half a meg or so) this results in a lot of unnecessary heap growth, garbage collection, and waaay too many arraycopies. In some version I've seen code which double's the buffer size with each growth, which is more efficient, but potentially more wasteful of memory as well. This seems like a perfect job for an object pool of pages which can be allocated to the buffer and then returned to the pool when no longer needed. The number of buffers needed can be quite high, but they are very transient. In most cases, the lifetime of the tag is much less than a second, so pages would get returned to the pool quickly. This would eliminate all the garbage collection and arraycopies. I think it would then be reasonable to make the buffer size quite a lot smaller, say 512 bytes, or 1K, which would cover the case of tags with very short body content more efficiently as well. The only thing I'm not sure about is knowing when it's safe to return the pages to the pool - it seems like it could be done at the end of writeOut(), but I'm not sure if there are any wierd situations where writeOut could get called more than once. If nobody sees any obvious problems with this scheme, I'll undertake to try it out and provide a patch for it. This code hasn't changed signifigantly since Tomcat 3.2, so it could be refitted in all the versions quite easily. -- Rob -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet JasperLoader.java
luehe 2002/10/21 11:44:01
Modified:jasper2/src/share/org/apache/jasper JspC.java
JspCompilationContext.java
jasper2/src/share/org/apache/jasper/servlet
JasperLoader.java
Log:
Reduced visibility of fields/methods where appropriate
Revision ChangesPath
1.16 +3 -4
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- JspC.java 10 Oct 2002 00:49:21 - 1.15
+++ JspC.java 21 Oct 2002 18:44:00 - 1.16
-69,7 +69,6
import org.apache.jasper.compiler.Compiler;
import org.apache.jasper.compiler.TldLocationsCache;
-import org.apache.jasper.servlet.JasperLoader;
import org.apache.jasper.servlet.JspCServletContext;
import org.apache.jasper.logging.Logger;
1.23 +38 -36
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspCompilationContext.java
Index: JspCompilationContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspCompilationContext.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- JspCompilationContext.java10 Oct 2002 00:49:21 - 1.22
+++ JspCompilationContext.java21 Oct 2002 18:44:00 - 1.23
-91,38 +91,38
private Hashtable tagFileJars;
private boolean isPackagedTagFile;
-protected String servletClassName;
-protected String jspUri;
+private String servletClassName;
+private String jspUri;
private boolean isErrPage;
-protected String servletPackageName = Constants.JSP_PACKAGE_NAME;
-protected String servletJavaFileName;
-protected String jspPath;
-protected String classFileName;
-protected String contentType;
-protected ServletWriter writer;
-protected Options options;
-protected JspServletWrapper jsw;
-protected Compiler jspCompiler;
-protected String classPath;
-
-protected String baseURI;
-protected String outputDir;
-protected ServletContext context;
-protected URLClassLoader loader;
+private String servletPackageName;
+private String servletJavaFileName;
+private String jspPath;
+private String classFileName;
+private String contentType;
+private ServletWriter writer;
+private Options options;
+private JspServletWrapper jsw;
+private Compiler jspCompiler;
+private String classPath;
+
+private String baseURI;
+private String outputDir;
+private ServletContext context;
+private URLClassLoader loader;
-protected JspRuntimeContext rctxt;
+private JspRuntimeContext rctxt;
-protected int removed = 0;
-protected boolean reload = true;
+private int removed = 0;
+private boolean reload = true;
-protected URLClassLoader jspLoader;
-protected URL[] outUrls = new URL[2];
-protected Class servletClass;
-
-protected boolean isTagFile;
-protected boolean protoTypeMode;
-protected TagInfo tagInfo;
-protected TagData tagData;
+private URLClassLoader jspLoader;
+private URL[] outUrls;
+private Class servletClass;
+
+private boolean isTagFile;
+private boolean protoTypeMode;
+private TagInfo tagInfo;
+private TagData tagData;
// jspURI _must_ be relative to the context
public JspCompilationContext(String jspUri,
-134,10 +134,10
this.jspUri = canonicalURI(jspUri);
this.isErrPage = isErrPage;
-this.options=options;
-this.jsw=jsw;
-this.context=context;
-
+this.options = options;
+this.jsw = jsw;
+this.context = context;
+
this.baseURI = jspUri.substring(0, jspUri.lastIndexOf('/') + 1);
// hack fix for resolveRelativeURI
if (baseURI == null) {
-150,9 +150,11
if (baseURI.charAt(baseURI.length() - 1) != '/') {
baseURI += '/';
}
-this.rctxt=rctxt;
+this.rctxt = rctxt;
this.tagFileJars = new Hashtable();
+this.servletPackageName = Constants.JSP_PACKAGE_NAME;
+ this.outUrls = new URL[2];
}
public JspCompilationContext(String tagfile,
1.5 +28 -40
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet/JasperLoader.java
Index: JasperLoader.java
===
RCS file:
RE: Bug 13658
IMHO, the 1.1 requirement is by virtue of Tomcat 3.3 being a reference implementation for the Servlet 2.2/JSP 1.1 specs. I don't think all of Tomcat 3.3's features have to run under 1.1. Especially new features that come after 3 major JVM versions and almost two Servlet spec versions. I'm not in favor of removing the 1.1 requirement entirely, but I have no problem with any Coyote based connector requiring J2SE. I doubt this will actually cause anybody any hardship. Cheers, Larry -Original Message- From: Remy Maucherat [mailto:remm;apache.org] Sent: Monday, October 21, 2002 6:48 AM To: Tomcat Developers List Subject: Re: Bug 13658 Costin Manolache wrote: I think it is perfectly fine for Coyote to require Java2. HashMap is available in GCJ/Kaffe and AFAIK in J2ME ( one of the profiles). I'll double check the last part. I would also +1 removing the JDK1.1 requirement for an eventual tomcat3.4. It's important to not confuse cause and effect - the 1.1 requirement is just a way to achieve the 'run anywhere' goal. At this moment Kaffe and GCJ support the collection and JNDI features - and they cover almost any platform/OS I ever heard of. If anyone can find an OS/platform that has a JDK1.1 but is not supported by kaffe/gcj - then we still have tomcat3.3 that can be used to provide servlet/jsp support for that platform. ( as any requirement - the 1.1 is set and removed by a majority vote, so if Larry would propose taking all the current fixes, plus coyote and have a release - he can include a proposal to drop 1.1 and the majority can decide ) Great ! I'll vote +1. Right now, there are still places in the critical path of 5.0 that need to be optimized (mostly the mapper), but after that, removing those useless syncing operations will be useful. Remy -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13723] - Bootstrap: Class loader creation threw exception
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=13723. 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=13723 Bootstrap: Class loader creation threw exception [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|CLOSED |REOPENED OS/Version|Windows NT/2K |Windows 9x Resolution|WORKSFORME | --- Additional Comments From [EMAIL PROTECTED] 2002-10-21 16:04 --- I got exactly same error. I am using win98. D:\D:\jakarta-tomcat-4.1.12\bin\startup start Using CATALINA_BASE: D:\jakarta-tomcat-4.1.12 Using CATALINA_HOME: D:\jakarta-tomcat-4.1.12 Using CATALINA_TMPDIR: D:\jakarta-tomcat-4.1.12\temp Using JAVA_HOME: D:\jdk1.2.2 1 D:\jdk1.2.2\bin\java-Djava.endorsed.dirs=D:\jakarta-tomcat-4.1.12\bin; D:\jakarta-tomcat-4.1.12\common\endorsed -classpath D:\jdk1.2.2\lib\tools.jar; D:\jakarta-tomcat-4.1.12\bin\bootstrap.jar -Dcatalina.base=D:\jakarta-tomcat-4 .1.12 -Dcatalina.home=D:\jakarta-tomcat-4.1.12 -Djava.io.tmpdir=D:\jakarta-t omcat-4.1.12\temp org.apache.catalina.startup.Bootstrap Bootstrap: Class loader creation threw exception java.lang.IllegalMonitorStateException: current thread not owner at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal( StandardClassLoader.java, Compiled Code) at org.apache.catalina.loader.StandardClassLoader.init(StandardClassLo ader.java, Compiled Code) at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(Clas sLoaderFactory.java, Compiled Code) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java, Compiled C ode) D:\ -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13827] New: - mod_jk load balancing does not set proper JSESSIONID with tomcat 4.x
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=13827.
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=13827
mod_jk load balancing does not set proper JSESSIONID with tomcat 4.x
Summary: mod_jk load balancing does not set proper JSESSIONID
with tomcat 4.x
Product: Tomcat 4
Version: 4.1.12
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Critical
Priority: Other
Component: Connector:Other
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
If I use tomcat 3.3.1 I end up with a JSESSIONID of zewmdq9u51.intlic1 where
intlic1 is the name of one of my load balanced workers. However, if I use
tomcat 4.1.12 or 4.0.6 I end up with a JSESSIONID of
021F58EA1591E5AEADF594A74431E83E which has no .workername appended to it and
thus never routes my session to the correct server. The configs appended to the
end of this bug report are using the RPM paths, but I've also tried with the
standard tarballs of 4.0.6 and 4.1.12 and duplicated the problem. Here are the
configs I'm using:
-
mod_jk.conf:
JkWorkersFile /etc/httpd/conf/workers.properties
JkLogFile /var/log/httpd/mod_jk.log
JkLogLevel debug
JkMount /*.jsp loadbalancer
JkMount /*.do loadbalancer
JkMount /licensemanager/* loadbalancer
-
workers.properties
(using the RPM layout just change /var/tomcat4 to /var/tomcat3 and this file
works with tomcat 3.3.1)
workers.tomcat_home=/var/tomcat4
workers.java_home=/usr/java/j2sdk1.4.0_02
ps=/
worker.list=loadbalancer
worker.intlic1.port=8009
worker.intlic1.host=10.4.4.10
worker.intlic1.type=ajp13
worker.intlic1.lbfactor=1
worker.intlic1.local_worker=1
worker.intlic2.port=8009
worker.intlic2.host=10.4.4.11
worker.intlic2.type=ajp13
worker.intlic2.lbfactor=1
worker.intlic2.local_worker=0
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=intlic1,intlic2
worker.loadbalancer.local_worker_only=1
-
server.xml for tomcat 4.1.12
(I've also tried using the coyote jk2 connector and still had the same results)
Server port=8005 shutdown=SHUTDOWN debug=0
Service name=Tomcat-Standalone
Connector className=org.apache.catalina.connector.http.HttpConnector
port=8080 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=10 debug=0 connectionTimeout=6/
Connector className=org.apache.ajp.tomcat4.Ajp13Connector
port=8009 minProcessors=5 maxProcessors=75
acceptCount=10 debug=0/
Engine name=Standalone defaultHost=intlic.togethersoft.net debug=0
Logger className=org.apache.catalina.logger.FileLogger
prefix=catalina_log. suffix=.txt
timestamp=true/
Realm className=org.apache.catalina.realm.MemoryRealm /
Host name=intlic.togethersoft.net debug=0 appBase=webapps
unpackWARs=true autoDeploy=true
Valve className=org.apache.catalina.valves.AccessLogValve
directory=logs prefix=intlic.togethersoft.net_access_log.
suffix=.txt
pattern=common/
Logger className=org.apache.catalina.logger.FileLogger
directory=logs prefix=intlic.togethersoft.net_log.
suffix=.txt
timestamp=true/
/Host
/Engine
/Service
/Server
-
server.xml for tomcat 3.3.1
?xml version=1.0 encoding=ISO-8859-1?
Server
ContextManager workDir=/var/spool/tomcat3
LoaderInterceptor11 useApplicationLoader=true /
TrustedLoader /
LogSetter name=tc_log timestamps=true
verbosityLevel=INFORMATION /
LogEvents enabled=false /
ContextXmlReader config=conf/server.xml /
ContextXmlReader config=conf/apps.xml /
AutoDeploy source=/var/tomcat3/modules target=/var/tomcat3/modules
redeploy=true /
AutoWebApp dir=/var/tomcat3/modules host=DEFAULT trusted=true/
AutoDeploy source=/var/tomcat3/webapps target=/var/tomcat3/webapps /
AutoWebApp dir=/var/tomcat3/webapps host=DEFAULT /
PolicyLoader securityManagerClass=java.lang.SecurityManager
policyFile=conf/tomcat.policy /
SimpleMapper1 /
SessionExpirer checkInterval=60 /
SessionIdGenerator randomClass=java.security.SecureRandom
randomFile=/dev/urandom /
LogSetter name=servlet_log
timestamps=true
verbosityLevel = INFORMATION
path=/var/log/tomcat3/servlet-${MMdd}.log
/
LogSetter name=JASPER_LOG
timestamps=true
path=/var/log/tomcat3/jasper-${MMdd}.log
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime JspFactoryImpl.java
luehe 2002/10/21 12:10:55
Modified:jasper2/src/share/org/apache/jasper/runtime
JspFactoryImpl.java
Log:
Reduced visibility of fields/methods where appropriate
Revision ChangesPath
1.2 +99 -96
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/JspFactoryImpl.java
Index: JspFactoryImpl.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/JspFactoryImpl.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- JspFactoryImpl.java 28 Mar 2002 18:46:19 - 1.1
+++ JspFactoryImpl.java 21 Oct 2002 19:10:54 - 1.2
-75,96 +75,69
import org.apache.jasper.logging.Logger;
/**
- * Implementation of JspFactory from the spec. Helps create
- * PageContext and other animals.
+ * Implementation of JspFactory.
*
* author Anil K. Vijendran
*/
public class JspFactoryImpl extends JspFactory {
-protected class PrivilegedGetPageContext implements PrivilegedAction {
- private JspFactoryImpl factory;
- private Servlet servlet;
- private ServletRequest request;
- private ServletResponse response;
- private String errorPageURL;
- private boolean needsSession;
- private int bufferSize;
- private boolean autoflush;
-
- PrivilegedGetPageContext(JspFactoryImpl factory,
- Servlet servlet,
- ServletRequest request,
- ServletResponse response,
- String errorPageURL,
- boolean needsSession, int bufferSize,
- boolean autoflush)
- {
- this.factory = factory;
- this.servlet = servlet;
- this.request = request;
- this.response = response;
- this.errorPageURL = errorPageURL;
- this.needsSession = needsSession;
- this.bufferSize = bufferSize;
- this.autoflush = autoflush;
- }
-
- public Object run() {
- return factory.internalGetPageContext(servlet,request,
- response,errorPageURL,
- needsSession,bufferSize,autoflush);
- }
-}
-
-protected class PrivilegedReleasePageContext implements PrivilegedAction {
-private JspFactoryImpl factory;
- private PageContext pageContext;
+private static final String SPEC_VERSION = 2.0;
+private static final boolean USE_POOL = true;
-PrivilegedReleasePageContext(JspFactoryImpl factory,
-PageContext pageContext)
-{
-this.factory = factory;
-this.pageContext = pageContext;
-}
-
-public Object run() {
-factory.internalReleasePageContext(pageContext);
- return null;
-}
-}
-
-private SimplePool pool=new SimplePool( 100 );
-private static final boolean usePool=true;
-
-Logger.Helper loghelper = new Logger.Helper(JASPER_LOG, JspFactoryImpl);
+private SimplePool pool = new SimplePool( 100 );
+private Logger.Helper loghelper = new Logger.Helper(JASPER_LOG,
+ JspFactoryImpl);
-public PageContext getPageContext(Servlet servlet, ServletRequest request,
+public PageContext getPageContext(Servlet servlet,
+ ServletRequest request,
ServletResponse response,
String errorPageURL,
- boolean needsSession, int bufferSize,
- boolean autoflush)
-{
+ boolean needsSession,
+ int bufferSize,
+ boolean autoflush) {
+
if( System.getSecurityManager() != null ) {
PrivilegedGetPageContext dp = new PrivilegedGetPageContext(
- (JspFactoryImpl)this,servlet,request,response,errorPageURL,
-needsSession,bufferSize,autoflush);
+ (JspFactoryImpl)this, servlet, request, response, errorPageURL,
+needsSession, bufferSize, autoflush);
return (PageContext)AccessController.doPrivileged(dp);
+ } else {
+ return internalGetPageContext(servlet, request, response,
+ errorPageURL, needsSession,
+ bufferSize, autoflush);
}
- return internalGetPageContext(servlet,request,response,errorPageURL,
- needsSession,bufferSize,autoflush);
+}
+public void releasePageContext(PageContext pc) {
+ if( pc == null )
+ return;
+if(
[Off-topic] FYI Xerces 2.2
HI, just a quick update with Xerces 2.2. Two weeks ago, I tough I've found the problem Tomcat was having with Xerces 2,2 (by replacing struts.jar file with the 1.1 beta version, the bug did not show up again). I did some tests last week and the bug starts to re-appear, but not all the time (sometimes 10 runs works fine). First I was under the impression it was a bug in Digester, but that was a wrong assumption. I have discussed the issue with the Xerces team and sent a small test case to them that reproduce consistently the bug. They have changed the threading model in Xerces 2.2 and, IMO, seems to be the cause (thread race). The bug doesn't occurs all the time, but the struts-config.xml is the perfect candidate to reproduce the problem. More news to come :-) -- Jeanfrancois -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: Bugzilla bug # 11501...
I'm not sure if this is the appropriate alias for this question. If not, please point me to the correct forum and I'll ask my question there. I'd really really really appreciate it if someone got back to me either way... Matthew Hamre wrote: I'm running into the problem outlined in bug # 11501. After searching quite a bit, I'm still confused as to how this symlink issue can be worked around. I'm trying to upgrade to 4.1.12, but this error has been a big problem. Any assistance would be greatly appreciated... Is the allowLinking option supposed to enable me to turn on symlinking, thus resolving this issue of having jars/tld's outside of the webapps dir? If so, where specifically is the appropriate place to add this option? Thanks in advance, - Matt -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: [VOTE] New Committer John Turner
Mladen Turk wrote: Hi, I'd like to propose John Turner [Jturner at AAS.com] as a new Tomcat committer. He does a great job in helping people on tomcat-users list, and he is willing to help us writing docs, testing, etc. +1. Much needed help in those areas :) Remy -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
RE: [PROPOSAL] JK2 uriMap using native regex
Mladen Turk wrote: -Original Message- From: Henri Gomez I would rather pick one and use it, and deal with the build problems. Probably we should just use what apache uses, it seems like a reusable piece of code. Other opinions ? We should use a regexp implementation which use a synthax similar to the one in Apache 1.3/2.0. And as for APR/SHM, make it build/run conditional if possible. We can use the regex that comes with Apache2, but I've been said that this is a modified pcre-3.9. Think that only modifications are about performance for small size matches (already in the pcre-3.92 test release), so that shouldn't be such a problem. The implementation will be conditional having bean name 'urix' (negotiable ;), using the same 'uri' factory. That way all the configuration will still work, but the urix will be favored over the normal uri directives. +1 BTW, I have a feeling this already works for httpd.conf-based configuration ( i.e JkSet in Location ). And it is the best solution to use the same regexp package that apache is using and make this behavior portable across servers and consistent for 'native' and workers.conf-style config. -- Costin -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
RE: [PROPOSAL] JK2 uriMap using native regex
-Original Message- From: Henri Gomez I would rather pick one and use it, and deal with the build problems. Probably we should just use what apache uses, it seems like a reusable piece of code. Other opinions ? We should use a regexp implementation which use a synthax similar to the one in Apache 1.3/2.0. And as for APR/SHM, make it build/run conditional if possible. We can use the regex that comes with Apache2, but I've been said that this is a modified pcre-3.9. Think that only modifications are about performance for small size matches (already in the pcre-3.92 test release), so that shouldn't be such a problem. The implementation will be conditional having bean name 'urix' (negotiable ;), using the same 'uri' factory. That way all the configuration will still work, but the urix will be favored over the normal uri directives. MT. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: mime settings for SVG in TC4/5 ?
I didn't see the mime settings for SVG format in TC 4/5 (and didn't see it also on Apache 1.3/2.0). I added the following : image/svg+xml svg image/svg+xml svgz More info from new http list : http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12241 Regards -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: mime settings for SVG in TC4/5 ?
- Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Monday, October 21, 2002 1:46 AM Subject: Re: mime settings for SVG in TC4/5 ? Henri Gomez wrote: I didn't see the mime settings for SVG format in TC 4/5 (and didn't see it also on Apache 1.3/2.0). I added the following : image/svg+xml svg image/svg+xml svgz I'll send a mail to new httpd team. Regards BTW, did the same should be added in TC 3.3.2-dev in j2ee web.xml ? Pretty harmless, seeing as how the j2ee in jakarta-tomcat hasn't been buildable for a long time. ;-) The place to make the change for TC 3.3 is o.a.t.u.http.MimeMap in j-t-c/util. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: [PROPOSAL] JK2 uriMap using native regex
Costin Manolache wrote: Something like that was discussed on commons ( I think ). The problem seems to be that different regex packages use different rules ( Perl-like, etc ), there is not standard syntax for regexp. That means the behavior would be dependent on which regexp engine is used. I would rather pick one and use it, and deal with the build problems. Probably we should just use what apache uses, it seems like a reusable piece of code. Other opinions ? We should use a regexp implementation which use a synthax similar to the one in Apache 1.3/2.0. And as for APR/SHM, make it build/run conditional if possible. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped
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=3888. 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=3888 WebappClassLoader: Lifecycle error : CL stopped --- Additional Comments From [EMAIL PROTECTED] 2002-10-21 08:33 --- Mark's message does not include source code for Log4jApplicationWatch and Log4jInit classes. Moreover, Mark reported that he could not reproduce the static-reference-jar-locking problem. I need a simple test case, with source code, capabable of reproducing the problem. Is that too much to ask for? Ceki ps: Mark CCed for reference. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-4.0/catalina/src/conf web.xml
hgomez 2002/10/21 01:32:51 Modified:catalina/src/conf web.xml Log: Add SVG mime type Revision ChangesPath 1.45 +8 -0 jakarta-tomcat-4.0/catalina/src/conf/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/web.xml,v retrieving revision 1.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- web.xml 21 Sep 2002 16:23:28 - 1.44 +++ web.xml 21 Oct 2002 08:32:51 - 1.45 -805,6 +805,14 mime-typeaudio/x-wav/mime-type /mime-mapping mime-mapping +extensionsvg/extension +mime-typeimage/svg+xml/mime-type +/mime-mapping +mime-mapping +extensionsvgz/extension +mime-typeimage/svg+xml/mime-type +/mime-mapping +mime-mapping !-- Wireless Bitmap -- extensionwbmp/extension mime-typeimage/vnd.wap.wbmp/mime-type -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
mime settings for SVG in TC4/5 ?
I didn't see the mime settings for SVG format in TC 4/5 (and didn't see it also on Apache 1.3/2.0). I added the following : image/svg+xml svg image/svg+xml svgz I'll send a mail to new httpd team. Regards -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
IIS JK Connector.
I have run in to a problem using the JK (version 1) connector for IIS in conjunction with an ISAPI filter put out in closed source. Basically, this other filter randomly deletes request headers for some reason and that interrupts the communication between the filter and the extension that implement the JK connector. I was planning on working around this problem by passing request information from the filter to the extension using shared memory (using a lookup table and passing the index in the query string). However, I was wondering if the patch would be more likely to be accepted if the new mechanism was enabled via a configuration option (or compile setting) or if I could just go ahead make that the communication mechanism. Also, is there a place I can go to read the coding standards for Jakarta, C-language projects? Thanks Steven B. Velez Software Engineer alventive [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/conf web.xml
hgomez 2002/10/21 01:40:37 Modified:catalina/src/conf web.xml Log: Add SVG mime type Revision ChangesPath 1.6 +8 -0 jakarta-tomcat-catalina/catalina/src/conf/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/web.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- web.xml 16 Oct 2002 11:44:16 - 1.5 +++ web.xml 21 Oct 2002 08:40:37 - 1.6 -787,6 +787,14 mime-typeaudio/x-wav/mime-type /mime-mapping mime-mapping +extensionsvg/extension +mime-typeimage/svg+xml/mime-type +/mime-mapping +mime-mapping +extensionsvgz/extension +mime-typeimage/svg+xml/mime-type +/mime-mapping +mime-mapping !-- Wireless Bitmap -- extensionwbmp/extension mime-typeimage/vnd.wap.wbmp/mime-type -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
The JNDIRealm
Hi! On the 27th Sep I posted a patch regarding JNDIRealm and SSL (http://www.mail-archive.com/tomcat-dev;jakarta.apache.org/msg34121.html). When I didn't get any feedback on the patch for a couple of weeks I sent a followup to try to remaind the tomcat developer community of the existance of the patch. Since that message also seems to have been overlooked I then both Craig (who is the origninal author) and Remy about it (yes, I realize you guys are busy). So far without any response. :( Whats the meaning of using an OSS development model if the users/non-commiters work is not considered? -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servlet ServletEngine.java TomcatServletEngine.java
luehe 2002/10/21 11:09:43 Removed: jasper2/src/share/org/apache/jasper/servlet ServletEngine.java TomcatServletEngine.java Log: Removed redundant files -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13533] - JSPs compiled inconsistently
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=13533.
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=13533
JSPs compiled inconsistently
--- Additional Comments From [EMAIL PROTECTED] 2002-10-21 08:59 ---
The OS (Linux 4.2) has been reinstalled and the problem remains. Here's an
example of the beginning of the generated servlet source for a JSP, taken from
our /work directory:
package org.apache.jsp;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import org.apache.jasper.runtime.*;
import com.ananova.catalogue.*;
import java.io.*;
import java.util.*;
import java.sql.SQLException;
public class alertCatalogue_jsp extends HttpJspBase {
package org.apache.jsp;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import org.apache.jasper.runtime.*;
import com.ananova.catalogue.*;
import java.io.*;
import java.util.*;
import java.sql.SQLException;
public class alertCatalogue_jsp extends HttpJspBase {
private static java.util.Vector _jspx_includes;
public java.util.List getIncludes() {
return _jspx_includes;
}
public void _jspService(HttpServletRequest request, HttpServletResponse
response)
throws java.io.IOException, ServletException {
JspFactory _jspxFactory = null;
javax.servlet.jsp.PageContext pageContext = null;
HttpSession session = null;
ServletContext application = null;
ServletConfig config = null;
JspWriter out = null;
Object page = this;
JspWriter _jspx_out = null;
After deleting this servlet source file, the recompilation returned the
following errors caused by incorrect package/class names, even though this time
the generated servlet source was correct:
HTTP Status 500 - Internal Server Error
type Exception report
message Internal Server Error
description The server encountered an internal error (Internal Server Error)
that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 2 in the jsp file: /indexCatalogue.jsp
Generated servlet error:
[javac] Compiling 1 source file
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:3:
package t.servlet does not exist
import javax.servlet.*;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:7:
package ort.ananova.catalogue does not exist
import com.ananova.catalogue.*;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:9:
package java. does not exist
import java.util.*;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:10:
cannot resolve symbol
symbol : class
location: package art
import java.net.URLEncoder;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:16:
cannot access .Object
file /Object.class not found
private static java.util.Vector _jspx_includes;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:18:
cannot access
file io/Serializable.class not found
public java.util.List getIncludes() {
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:23:
cannot resolve symbol
symbol : class IOException
location: package io
throws java.io.IOException, ServletException {
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:23:
cannot resolve symbol
symbol : class ServletException
location: class org.apache.jsp.indexCatalogue_jsp
throws java.io.IOException, ServletException {
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:28:
cannot resolve symbol
symbol : class ServletContext
location: class org.apache.jsp.indexCatalogue_jsp
ServletContext application = null;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:29:
cannot resolve symbol
symbol : class ServletConfig
location: class org.apache.jsp.indexCatalogue_jsp
ServletConfig config = null;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:31:
cannot resolve symbol
symbol : class Object
location: class org.apache.jsp.indexCatalogue_jsp
Object page = this;
^
/usr/local/jakarta-tomcat-
4.1.12/work/Apache/goyt.ananova.net/catalogue/indexCatalogue_jsp.java:37:
cannot access .String
file /String.class not found
response.setContentType(text/html;charset=ISO-8859-1);
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime HttpJspBase.java
luehe 2002/10/21 15:50:05
Modified:jasper2/src/share/org/apache/jasper/runtime HttpJspBase.java
Log:
Removed 'pageContext' field (already gets declared by the generated servlet)
Revision ChangesPath
1.5 +1 -2
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/HttpJspBase.java
Index: HttpJspBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/HttpJspBase.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- HttpJspBase.java 28 Aug 2002 23:00:19 - 1.4
+++ HttpJspBase.java 21 Oct 2002 22:50:05 - 1.5
-72,7 +72,7
import org.apache.jasper.Constants;
/**
- * This is the subclass of all JSP-generated servlets.
+ * This is the super class of all JSP-generated servlets.
*
* author Anil K. Vijendran
*/
-80,7 +80,6
extends HttpServlet
implements HttpJspPage
{
-protected PageContext pageContext;
static {
if( JspFactory.getDefaultFactory() == null ) {
JspFactoryImpl factory = new JspFactoryImpl();
--
To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 10138] - pageContext declaration should be removed from HttpJspBase
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=10138. 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=10138 pageContext declaration should be removed from HttpJspBase [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-10-21 22:54 --- Fixed. Removed 'pageContext' field, as it already gets declared by the generated servlet class. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13832] New: - handshake security error when user accessing http://localhost:8443
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=13832. 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=13832 handshake security error when user accessing http://localhost:8443 Summary: handshake security error when user accessing http://localhost:8443 Product: Tomcat 4 Version: Nightly Build Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When accessing http://localhost:8443, (Not https://localhost:8443) tomcat generates SSL handshaking error and hangs. For http://localhost:8443, tomcat should give Not Found error in the browser rather than trying to use SSL connection, since it is not a SSL protocol. Oct 21, 2002 3:58:31 PM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Handshake failed javax.net.ssl.SSLException: Unrecognized SSL handshake. at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA6275) at java.io.OutputStream.write(OutputStream.java:58) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocke tFactory.java:290) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :513) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:533) at java.lang.Thread.run(Thread.java:536) Oct 21, 2002 3:58:31 PM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Caught exception executing org.apache.tomcat.util.net.TcpWorkerThread@5c 3987, terminating thread java.lang.NullPointerException at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java :532) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:533) at java.lang.Thread.run(Thread.java:536) -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13833] New: - Webapp install/start failures not reported by Deployer install operation
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=13833. 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=13833 Webapp install/start failures not reported by Deployer install operation Summary: Webapp install/start failures not reported by Deployer install operation Product: Tomcat 4 Version: 4.0.4 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] To programmatically install a webapp at runtime, the Deployer interface is used. StandardHost implements this interface. According to its install() documentation, if this application is successfully installed, a ContainerEvent of type INSTALL_EVENT will be sent to all registered listeners. If a webapp tries to get installed/started that is invalid (e.g., contains a malformed web.xml file), during the StandardContext Lifecycle start() operation, Tomcat knows that it cannot configure the context. In such a case, it automatically tries to stop the context and marks it unavailable. However, the problem is that StandardContext start() fails to alert the caller that the operation failed. Thus, the install operation succeeds and the caller is notified with a [successful] INSTALL_EVENT. Furthermore, the unavailable/invalid context object gets added to the container hierarchy leading to invalid state if/when it tries to get uninstalled. To fix this problem, StandardContext start() should throw a LifecycleException when it marks the context as unavailable. (I haven't checked whether or not this bug also exists in Tomcat 4.1.x.) -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13834] New: - JSP pages under Tomcat 4.1.12 fail to find class files in jar
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=13834. 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=13834 JSP pages under Tomcat 4.1.12 fail to find class files in jar Summary: JSP pages under Tomcat 4.1.12 fail to find class files in jar Product: Tomcat 4 Version: 4.1.12 Platform: Sun OS/Version: Solaris Status: NEW Severity: Blocker Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I am having problems with a JSP page that reads a bean from the application environment. The bean is part of a jar file deployed under WEB-INF/lib directory. The same web page/application will not generate this error if I was using Tomcat 4.0.6. I have a different problem if I was using 4.0.6! The error reported as is: /opt/jakarta/tomcat4.1.12/work/Standalone/localhost/comet/jsp/stat_jsp.java:7: '.' expected import SettingsBean; The class file is part of the beans.jar library stored under comet/WEB- INF/lib/beans.jar. Here is a listing of the library contents: /opt/jakarta/tomcat/webapps/comet/WEB-INF/lib lf app.jar beans.jar servletUtils.jar /opt/jakarta/tomcat/webapps/comet/WEB-INF/lib jar tvf beans.jar 2859 Fri Oct 18 17:43:00 CDT 2002 SettingsBean.class /opt/jakarta/tomcat/webapps/comet/WEB-INF/lib jar tvf app.jar 1433 Fri Oct 18 17:18:48 CDT 2002 ActiveCall.class 3422 Fri Oct 18 17:18:48 CDT 2002 ConfigFile.class 977 Fri Oct 18 17:18:48 CDT 2002 Facility.class 636 Thu Sep 26 14:45:32 CDT 2002 LinkStates.class 1938 Fri Oct 18 17:18:48 CDT 2002 MyFileNameFilter.class 1195 Fri Oct 18 17:18:48 CDT 2002 Sdl.class 6459 Fri Oct 18 17:18:48 CDT 2002 Syslog.class 1500 Fri Oct 18 17:18:48 CDT 2002 UnixCmd.class 560 Fri Oct 18 17:18:48 CDT 2002 UnixSignals.class 1495 Fri Oct 18 17:18:48 CDT 2002 Link.class 1207 Fri Oct 18 17:18:48 CDT 2002 DataEvent.class 2507 Fri Oct 11 12:28:32 CDT 2002 ExceptionDialog.class 651 Fri Oct 11 12:28:32 CDT 2002 ExceptionDialog$CloseDialog.class 989 Fri Oct 11 12:28:32 CDT 2002 ExceptionDialog$CloseWindow.class 615 Wed Oct 16 08:59:26 CDT 2002 DialogBox$CloseDialog.class 959 Wed Oct 16 08:59:26 CDT 2002 DialogBox$CloseWindow.class 2459 Wed Oct 16 08:59:26 CDT 2002 DialogBox.class 552 Fri Oct 18 17:18:48 CDT 2002 DataFile.class /opt/jakarta/tomcat/webapps/comet/WEB-INF/lib jar tvf servletUtils.jar 1358 Fri Oct 18 17:18:56 CDT 2002 FacilityFile.class 3884 Mon Oct 21 10:40:02 CDT 2002 SettingsFile.class The jar files are loaded as can be seen from the contents of the application logger, comet_log.2002-10-21.txt. The following are the lines showing that the jar files were loaded at init time. = StandardContext[/comet]: Starting StandardContext[/comet]: Processing start(), current available=false StandardContext[/comet]: Configuring default Resources StandardContext[/comet]: Configuring non-privileged default Loader StandardContext[/comet]: Configuring default Manager StandardContext[/comet]: Processing standard container startup WebappLoader[/comet]: Deploying class repositories to work directory /opt/jakarta/tomcat-4 .0.6/work/Standalone/localhost/comet WebappLoader[/comet]: Deploy JAR /WEB-INF/lib/app.jar to /opt/jakarta/tomcat- 4.0.6/webapps /comet/WEB-INF/lib/app.jar WebappLoader[/comet]: Deploy JAR /WEB-INF/lib/beans.jar to /opt/jakarta/tomcat- 4.0.6/webap ps/comet/WEB-INF/lib/beans.jar WebappLoader[/comet]: Deploy JAR /WEB-INF/lib/servletUtils.jar to /opt/jakarta/tomcat-4.0.6/webapps/comet/WEB-INF/lib/servletUtils.jar StandardManager[/comet]: Seeding random number generator class java.security.SecureRandom StandardManager[/comet]: Seeding of random number generator has been completed ContextConfig[/comet]: ContextConfig: Processing START StandardContext[/comet]: Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' StandardContext[/comet]: Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' ContextConfig[/comet]: Scanning web.xml tag libraries ContextConfig[/comet]: Scanning TLD files in /WEB-INF ContextConfig[/comet]: Scanning library JAR files ContextConfig[/comet]: Added certificates - request attribute Valve ContextConfig[/comet]: Pipline Configuration: ContextConfig[/comet]: org.apache.catalina.valves.CertificatesValve/1.0 ContextConfig[/comet]: org.apache.catalina.core.StandardContextValve/1.0 ContextConfig[/comet]: == StandardContext[/comet]: Configuring application event listeners StandardContext[/comet]: Sending application start
DO NOT REPLY [Bug 13834] - JSP pages under Tomcat 4.1.12 fail to find class files in jar
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=13834. 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=13834 JSP pages under Tomcat 4.1.12 fail to find class files in jar --- Additional Comments From [EMAIL PROTECTED] 2002-10-21 23:31 --- Sorry, I mistakenly added the contents of the log files for Tomcat 4.0.6 instead of Tomcat 4.1.12 to the original bug description. Below is the correct log file output. == StandardContext[/comet]: Starting StandardContext[/comet]: Processing start(), current available=false StandardContext[/comet]: Configuring default Resources StandardContext[/comet]: Configuring privileged default Loader StandardContext[/comet]: Configuring default Manager StandardContext[/comet]: Processing standard container startup WebappLoader[/comet]: Deploying class repositories to work directory /opt/jakarta/tomcat-4 .1.12/work/Standalone/localhost/comet WebappLoader[/comet]: Deploy class files /WEB-INF/classes to /opt/jakarta/tomcat-4.1.12/we bapps/comet/WEB-INF/classes WebappLoader[/comet]: Deploy JAR /WEB-INF/lib/app.jar to /opt/jakarta/tomcat4.1.12/webapps/comet/WEB-INF/lib/app.jar WebappLoader[/comet]: Deploy JAR /WEB-INF/lib/beans.jar to /opt/jakarta/tomcat- 4.1.12/webapps/comet/WEB-INF/lib/beans.jar WebappLoader[/comet]: Deploy JAR /WEB-INF/lib/servletUtils.jar to /opt/jakarta/tomcat-4.1.12/webapps/comet/WEB-INF/lib/servletUtils.jar ContextConfig[/comet]: ContextConfig: Processing START StandardContext[/comet]: Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' StandardContext[/comet]: Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' ContextConfig[/comet]: Accumulating TLD resource paths ContextConfig[/comet]: Scanning taglib elements in web.xml ContextConfig[/comet]: Scanning TLDs in /WEB-INF subdirectory ContextConfig[/comet]: Scanning JARs in /WEB-INF/lib subdirectory ContextConfig[/comet]:Adding path '/WEB-INF/lib/app.jar' ContextConfig[/comet]:Adding path '/WEB-INF/lib/beans.jar' ContextConfig[/comet]:Adding path '/WEB-INF/lib/servletUtils.jar' ContextConfig[/comet]: Scanning JAR at resource path '/WEB-INF/lib/app.jar' ContextConfig[/comet]: Scanning JAR at resource path '/WEBINF/lib/servletUtils.jar' ContextConfig[/comet]: Scanning JAR at resource path '/WEB-INF/lib/beans.jar' ContextConfig[/comet]: Pipline Configuration: ContextConfig[/comet]: org.apache.catalina.core.StandardContextValve/1.0 ContextConfig[/comet]: == NamingContextListener[/Standalone/localhost/comet]: Creating JNDI naming context NamingContextListener[/Standalone/localhost/comet]: Resource parameters for UserTransact ion = null StandardManager[/comet]: Seeding random number generator class java.security.SecureRandom StandardManager[/comet]: Seeding of random number generator has been completed StandardContext[/comet]: Posting standard context attributes StandardContext[/comet]: Configuring application event listeners StandardContext[/comet]: Sending application start events StandardContext[/comet]: Starting filters Settings: Settings: Read 8 lines of site settings Settings: Initial Bean Status Facility[0] Name = Lower State = OOS Facility[1] Name = Upper State = ACT Facility[2] Name = Unknown State = STBY Facility[3] Name = Unknown State = INIT Facility[4] Name = Unknown State = UNKN Facility[5] Name = Unknown State = UNAV StandardWrapper[/comet:default]: Loading container servlet default StandardWrapper[/comet:invoker]: Loading container servlet invoker StandardContext[/comet]: Starting completed StandardContext[/comet]: Mapping contextPath='/comet' with requestURI='/comet/jsp/stat.jsp ' and relativeURI='/jsp/stat.jsp' StandardContext[/comet]: Trying exact match StandardContext[/comet]: Trying prefix match StandardContext[/comet]: Trying extension match StandardContext[/comet]: Mapped to servlet 'jsp' with servlet path '/jsp/stat.jsp' and path info 'null' and update=true Error compiling file: /opt/jakarta/tomcat4.1.12/work/Standalone/localhost/comet/jsp/stat_jsp.jav a [javac] Compiling 1 source file /opt/jakarta/tomcat4.1.12/work/Standalone/localhost/comet/jsp/stat_jsp.java:7: ' .' expected import SettingsBean; ^ /opt/jakarta/tomcat4.1.12/work/Standalone/localhost/comet/jsp/stat_jsp.java:50: cannot resolve symbol symbol : class SettingsBean location: class org.apache.jsp.stat_jsp SettingsBean settings = null; ^ /opt/jakarta/tomcat4.1.12/work/Standalone/localhost/comet/jsp/stat_jsp.java:52: cannot resolve symbol symbol : class SettingsBean location: class org.apache.jsp.stat_jsp settings = (SettingsBean)
DO NOT REPLY [Bug 13834] - JSP pages under Tomcat 4.1.12 fail to find class files in jar
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=13834. 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=13834 JSP pages under Tomcat 4.1.12 fail to find class files in jar [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-10-22 00:15 --- From the log in 4.1.12, looks like the problem is that you are importing a class from the unamed package, which is illegal in JDK 1.4. See #10036. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: The JNDIRealm
Hi! On this subject already wrote Fredrik Westermarck. I concerning JNDIRealm. Unfortunately I am not yet commiter, therefore of powerful contribution bring I can not. Usage SSL in JNDIRealm is a urgent subject - we use it for authentification of the users registered in Novell NDS - and the base mechanism does not suffice. It is necessary to work with LDAP not only as with the database (realm) but also as with the mechanism of identification of the users. For this purpose JNDIRealm tries to incorporate to the server through the mechanism of a login name - password indicated by the user. It is desirable that JNDIRealm was connected even with a minimum level of privacy. I offer to expand JNDIRealm so, that it could solve all these tasks. Best regards - Max Parygin -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped
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=3888. 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=3888 WebappClassLoader: Lifecycle error : CL stopped --- Additional Comments From [EMAIL PROTECTED] 2002-10-22 02:53 --- Created an attachment (id=3561) sample webapp to test log4j jar being locked even after Tomcat manager remove -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler JspDocumentParser.java Node.java SmapUtil.java
luehe 2002/10/21 20:00:20
Modified:jasper2/src/share/org/apache/jasper/compiler
JspDocumentParser.java Node.java SmapUtil.java
Log:
Added support for prelude and coda to JSP documents
Revision ChangesPath
1.20 +79 -31
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java
Index: JspDocumentParser.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- JspDocumentParser.java17 Oct 2002 20:43:06 - 1.19
+++ JspDocumentParser.java22 Oct 2002 03:00:20 - 1.20
-61,7 +61,7
package org.apache.jasper.compiler;
import java.io.*;
-import java.util.Hashtable;
+import java.util.*;
import javax.servlet.jsp.tagext.*;
import javax.xml.parsers.SAXParserFactory;
import javax.xml.parsers.ParserConfigurationException;
-92,19 +92,26
private ParserController parserController;
private JspCompilationContext ctxt;
+private PageInfo pageInfo;
+
// XML document source
private InputSource inputSource;
+
private String path;
+
// Node representing the XML element currently being parsed
private Node current;
+
// Document locator
private Locator locator;
+
private Hashtable taglibs;
+
// Flag indicating whether we are inside DTD declarations
private boolean inDTD;
+
private ErrorDispatcher err;
private boolean isTagFile;
-private boolean rootSeen;
/*
* Constructor
-115,7 +122,8
boolean isTagFile) {
this.parserController = pc;
this.ctxt = pc.getJspCompilationContext();
- this.taglibs = pc.getCompiler().getPageInfo().getTagLibraries();
+ this.pageInfo = pc.getCompiler().getPageInfo();
+ this.taglibs = this.pageInfo.getTagLibraries();
this.err = pc.getCompiler().getErrorDispatcher();
this.path = path;
this.inputSource = new InputSource(reader);
-125,19 +133,32
/*
* Parses a JSP document by responding to SAX events.
*
- * throws JasperException XXX
+ * throws JasperException
*/
public static Node.Nodes parse(ParserController pc,
String path,
InputStreamReader reader,
Node parent,
boolean isTagFile) throws JasperException {
+
JspDocumentParser handler = new JspDocumentParser(pc, path, reader,
isTagFile);
- handler.current = parent;
Node.Nodes pageNodes = null;
+ Node.JspRoot jspRoot = null;
try {
+ if (parent == null) {
+ // create dummy jsp:root element
+ AttributesImpl rootAttrs = new AttributesImpl();
+ rootAttrs.addAttribute(, , version, CDATA, 2.0);
+ jspRoot = new Node.JspRoot(rootAttrs, null, null);
+ handler.current = jspRoot;
+ handler.addInclude(jspRoot,
+handler.pageInfo.getIncludePrelude());
+ } else {
+ handler.current = parent;
+ }
+
// Use the default (non-validating) parser
SAXParserFactory factory = SAXParserFactory.newInstance();
-151,8 +172,9
saxParser.parse(handler.inputSource, handler);
if (parent == null) {
- // Add the jsp:root element to the parse result
- pageNodes = new Node.Nodes((Node.JspRoot) handler.current);
+ handler.addInclude(jspRoot, handler.pageInfo.getIncludeCoda());
+ // Create Node.Nodes from dummy (top-level) jsp:root
+ pageNodes = new Node.Nodes(jspRoot);
} else {
pageNodes = parent.getBody();
}
-179,15 +201,6
Node node = null;
- if (!qName.equals(JSP_ROOT) !rootSeen) {
- // create dummy jsp:root element
- AttributesImpl rootAttrs = new AttributesImpl();
- rootAttrs.addAttribute(, , version, CDATA, 2.0);
- node = new Node.JspRoot(rootAttrs, null, current, true);
- current = node;
-rootSeen = true;
- }
-
// XXX - As of JSP 2.0, xmlns: can appear in any node (not just
// jsp:root). The spec still needs clarification here.
// What we implement is that it can appear in any node and
-205,8 +218,7
// give the jsp:root element the original attributes set
// (attrs) instead of the copy without the xmlns: elements
DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped
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=3888. 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=3888 WebappClassLoader: Lifecycle error : CL stopped --- Additional Comments From [EMAIL PROTECTED] 2002-10-22 03:05 --- The testcase I just uploaded provides Mark's testcase and includes a simplified version of my Log4jInit servlet. Logging is done via both a console appender and a FileAppender. The file appender is set up with a dynamic variable which points to where to write the file. As long as you install the app with the path /locktest, you will find the file main.log in WEB-INF/logs of this webapp. No need to configure anything. It is all set up and ready to run. All source code including the classes that Mark didn't provide source to are provided (I decompiled his classes. I'm sure he doesn't mind). All source resides in the root of the webapp as well as the .jsp files which are what you need to run to see logging output. There is also a running.txt file which describes the URL to use to install/remove the webapp. Modify those example URL's to point to the log4j_locktest directory, which is the root of the webapp, on your system. Make sure this is installed *outside* of Tomcat's webapps directory. Any other place on your file system is appropriate. Any questions, let me know. Jake -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped
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=3888. 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=3888 WebappClassLoader: Lifecycle error : CL stopped --- Additional Comments From [EMAIL PROTECTED] 2002-10-22 03:09 --- Sorry for the spam, Forgot to mention to put a recent version of log4j.jar in WEB-INF/lib before installing this in Tomcat. You should notice after the removal of the webapp that the log file is able to be deleted and the static_test.jar is able to be deleted. However the log4j.jar is locked until you shutdown Tomcat. That is the problem we are trying to solve. Jake -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: [Off-topic] FYI Xerces 2.2
Jean-Francois Arcand wrote: HI, just a quick update with Xerces 2.2. Two weeks ago, I tough I've found the problem Tomcat was having with Xerces 2,2 (by replacing struts.jar file with the 1.1 beta version, the bug did not show up again). I did some tests last week and the bug starts to re-appear, but not all the time (sometimes 10 runs works fine). First I was under the impression it was a bug in Digester, but that was a wrong assumption. I have discussed the issue with the Xerces team and sent a small test case to them that reproduce consistently the bug. They have changed the threading model in Xerces 2.2 and, IMO, seems to be the cause (thread race). The bug doesn't occurs all the time, but the struts-config.xml is the perfect candidate to reproduce the problem. More news to come :-) Thanks for the feed back ;) -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: IIS JK Connector.
Steven Velez wrote: I have run in to a problem using the JK (version 1) connector for IIS in conjunction with an ISAPI filter put out in closed source. Basically, this other filter randomly deletes request headers for some reason and that interrupts the communication between the filter and the extension that implement the JK connector. I was planning on working around this problem by passing request information from the filter to the extension using shared memory (using a lookup table and passing the index in the query string). However, I was wondering if the patch would be more likely to be accepted if the new mechanism was enabled via a configuration option (or compile setting) or if I could just go ahead make that the communication mechanism. Also, is there a place I can go to read the coding standards for Jakarta, C-language projects? The place is on apache.org, coding standards. http://www.apache.org/dev/styleguide.html -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
DO NOT REPLY [Bug 13827] - mod_jk load balancing does not set proper JSESSIONID with tomcat 4.x
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=13827. 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=13827 mod_jk load balancing does not set proper JSESSIONID with tomcat 4.x --- Additional Comments From [EMAIL PROTECTED] 2002-10-22 06:16 --- Hi Jason, Did you use the same mod_jk (ie the JK 1.2.0) against TC 3.3.1 and 4.x or did you use the old mod_jk 1.1 which came from TC 3.3 ? -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
RE: IIS JK Connector.
-Original Message- From: Henri Gomez The place is on apache.org, coding standards. http://www.apache.org/dev/styleguide.html So why don't we follow that ;). MT. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http MimeMap.java
hgomez 2002/10/21 23:25:01 Modified:util/java/org/apache/tomcat/util/http MimeMap.java Log: Add more MIME type, xml/xsl/wml/svg related Revision ChangesPath 1.2 +13 -1 jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/MimeMap.java Index: MimeMap.java === RCS file: /home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/MimeMap.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- MimeMap.java 16 May 2001 23:18:12 - 1.1 +++ MimeMap.java 22 Oct 2002 06:25:01 - 1.2 -82,7 +82,7 defaultMap.put(jpg, image/jpeg); defaultMap.put(jpe, image/jpeg); defaultMap.put(jpeg, image/jpeg); - defaultMap.put(java, text/plain); + defaultMap.put(java, text/plain); defaultMap.put(body, text/html); defaultMap.put(rtx, text/richtext); defaultMap.put(tsv, text/tab-separated-values); -158,6 +158,18 defaultMap.put(avx, video/x-rad-screenplay); defaultMap.put(wrl, x-world/x-vrml); defaultMap.put(mpv2, video/mpeg2); + +/* Add XML related MIMEs */ + +defaultMap.put(xml, text/xml); +defaultMap.put(xsl, text/xml); +defaultMap.put(svg, image/svg+xml); +defaultMap.put(svgz, image/svg+xml); +defaultMap.put(wbmp, image/vnd.wap.wbmp); +defaultMap.put(wml, text/vnd.wap.wml); +defaultMap.put(wmlc, application/vnd.wap.wmlc); +defaultMap.put(wmls, text/vnd.wap.wmlscript); +defaultMap.put(wmlscriptc, application/vnd.wap.wmlscriptc); } -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
