Re: [4.1.17] Tag soon ?
M wrote: Remy Maucherat wrote: I don't see any major issues with 4.1.16, so I plan to tag 4.1.17 (which hopefully would be the next stable build) tomorrow after a few more minor tweaks. There was a report made against JK 2 immediately after 4.1.16 Beta was announced. Can someone confirm there's no major issue with JK ? I made the report and I can confirm that it still isn't working. I'm using exacly the same configuration as for 4.1.12 and 4.1.14 both of which work. The workaround in Bug 15258 fixes our problem. We were indeed using the external ip address of the machine to connect and not the loopback address. (Multiple load balanced servers) Sorry I should have spotted the bind problem when I did a netstat... Many thanks. -- Regards, M Martin Sillence PR Newswire DL +44 (0)1865 78 5065 F +44 (0)1865 78 5100 W www.prnewswire.eu.com --- Any views or opinions are solely those of the author and do not necessarily represent those of PR Newswire Europe. The e-mail contents are intended only for addressee and may contain confidential and/or privileged material. If you are not the intended recipient, please do not read, copy, use or disclose this communication and notify the sender. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Thursday, December 12, 2002 12:38 AM Subject: Re: [VOTE] minimal JSR 154 only distribution Jon Scott Stevens wrote: on 2002/12/11 5:06 PM, Glenn Nielsen [EMAIL PROTECTED] wrote: Looking at the original vote I realize that what you ask can't be done. Tomcat 4 is the RI of Servlet 2.3, JSR 154 is for Servlet 2.4. So it isn't possible to create a JSR 154 only dist of Tomcat 4. Glenn Very good point. I withdrawal my vote. A new vote will need to be made for Tomcat 5. I will re-submit when I can also submit a patch for it. =) As soon as I'm over a Scarab deadline (Dec 20th), I'm going to work on this and it is going to turn into another similar Anakia-style deal. If you remember correctly, people -1'd Anakia all over the place until I went and actually built the website using it. Now, to this day, Anakia is still used for the Jakarta site (as well as the main www.apache.org site). So, for something that people said sucks so badly and is such a terrible idea, it has worked very well for quite a while now. =) The same will be true for my minimal distribution idea. This is not getting anywhere. Actually, what you want is not a distribution for end users, but rather a distribution for people embedding Tomcat (like, say, for Cocoon, Slide, Scarab). If this packaging is clearly labelled as such, then I could live with it, as it will not confuse users (except those who can't read). Urm, err, the users that can't read may include you ;-). Jon withdrew the vote above. This means that this is officially 'not getting anywhere', at least until Jon re-submits his re-worked proposal. Other than that, I think having one and only one user oriented distribution (the implementation I favor for that one is with jboss-like profiles) should be a requirement. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Bill Barker wrote: Urm, err, the users that can't read may include you ;-). Jon withdrew the vote above. This means that this is officially 'not getting anywhere', at least until Jon re-submits his re-worked proposal. I know (and I can usually read, thanks), but since he's going to resubmit it later, I don't see any harm with talking about it. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Bug in IIS JK2 connector? Can't upload multipart-forms...
Thnx, I will check this out! -Andris I'm having problems with JK2 connector and Microsoft IIS. I can't... Sounds like you might have come across the same problem I did. If so, this patch might solve your case too: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15278 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
using manager web application
dear all; i'm new in using Tomcat server, and i'm trying to deploy my applications on it. i tried to use manager web application through its web interface at http://myserver/manager/ i ftp my war file on server and try to install it but i couldn't it gives me connection time out i use it as follows: path: /var/tomcat4/webapps/prom config url:http://myserver/myfirsttrial war url: jar:file:/home/webdevtest/SourceWar/promo1.war!/ note that the war file exists on the server just in the location specified in war url field, and the folder i nedd the application to be unpacked to is prom and already created on server. i don't know what is the error in all what i mentioned above. please help me as soon as possible. Regards Eman
Re: [VOTE] minimal JSR 154 only distribution
Remy Maucherat wrote: Jon Scott Stevens wrote: on 2002/12/11 5:06 PM, Glenn Nielsen [EMAIL PROTECTED] wrote: Looking at the original vote I realize that what you ask can't be done. Tomcat 4 is the RI of Servlet 2.3, JSR 154 is for Servlet 2.4. So it isn't possible to create a JSR 154 only dist of Tomcat 4. Glenn Very good point. I withdrawal my vote. A new vote will need to be made for Tomcat 5. I will re-submit when I can also submit a patch for it. =) As soon as I'm over a Scarab deadline (Dec 20th), I'm going to work on this and it is going to turn into another similar Anakia-style deal. If you remember correctly, people -1'd Anakia all over the place until I went and actually built the website using it. Now, to this day, Anakia is still used for the Jakarta site (as well as the main www.apache.org site). So, for something that people said sucks so badly and is such a terrible idea, it has worked very well for quite a while now. =) The same will be true for my minimal distribution idea. This is not getting anywhere. Actually, what you want is not a distribution for end users, but rather a distribution for people embedding Tomcat (like, say, for Cocoon, Slide, Scarab). If this packaging is clearly labelled as such, then I could live with it, as it will not confuse users (except those who can't read). If the idea is creating more ant task like dist (the actual), distmin (a minimal Servlet Engine) distjon (the minimal + Jon's requirement). Then I will be +1 ;-) Other than that, I think having one and only one user oriented distribution (the implementation I favor for that one is with jboss-like profiles) should be a requirement. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15306] New: - Tomcat does not startup SSL
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=15306. 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=15306 Tomcat does not startup SSL Summary: Tomcat does not startup SSL Product: Tomcat 4 Version: 4.1.12 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] I've been trying to set up my tomcat 4.1.12 installation as said in the documentation. Here are the steps I've followed: First of all, we delete any anoyance entries: keytool -delete -v -alias tomcat -storepass MYPASSWORD keytool -delete -v -alias root -storepass MYPASSWORD Later on, let's generate the local certificate: keytool -genkey -v -alias tomcat -storepass MYPASSWORD -keyalg RSA -keysize 2048 -validity 365 -keypass MYPASSWORD - dname CN=es.burke.arturo.garcia.martin, OU=Departamento de Desarrollo, O=BURKE, L=Madrid, S=MADRID, C=ES The Certificate Signing Request: keytool -certreq -v -alias tomcat -storepass MYPASSWORD -keyalg RSA -file certreq.csr Gone to Verisign site and requested the new certificate. It came by e-mail. Saved the generated certificate from Verisign in a file named: vstomcat.cer and saved the Root certificate from Verisign in a file named: verisign.cer. Let's import them: keytool -import -v -alias root -storepass MYPASSWORD -trustcacerts -file verisign.cer keytool -import -v -alias tomcat -storepass MYPASSWORD -trustcacerts -file vstomcat.cer Print out the contents of the store: keytool -list-v -storepass MYPASSWORD The entry in the server.xml file: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=9443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=99 scheme=https secure=true useURIValidationHack=false Factory className=org.apache.coyote.tomcat4.CoyoteServerSocketFactory keystoreFile=MY_.keystore keystorePass=MYPASSWORD clientAuth=true protocol=TLS / /Connector The startup: Bootstrap: Create Catalina server ERROR [main] (Http11Protocol.java:152) - Error initializing endpoint java.io.IOException: Cannot recover key at org.apache.tomcat.util.net.JSSESocketFactory.initProxy (JSSESocketFactory.java:231) at org.apache.tomcat.util.net.JSSESocketFactory.createSocket (JSSESocketFactory.java:127) at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint (PoolTcpEndpoint.java:263) at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150) at org.apache.coyote.tomcat4.CoyoteConnector.initialize (CoyoteConnector.java:1002) at org.apache.catalina.core.StandardService.initialize (StandardService.java:579) at org.apache.catalina.core.StandardServer.initialize (StandardServer.java:2245) at org.apache.catalina.startup.CatalinaService.load (CatalinaService.java:234) at org.apache.catalina.startup.CatalinaService.load (CatalinaService.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.BootstrapService.init (BootstrapService.java:231) at org.apache.catalina.startup.BootstrapService.main (BootstrapService.java:297) Catalina.start: LifecycleException: Protocol handler initialization failed: java.io.IOException: Cannot recover key LifecycleException: Protocol handler initialization failed: java.io.IOException: Cannot recover key at org.apache.coyote.tomcat4.CoyoteConnector.initialize (CoyoteConnector.java:1004) at org.apache.catalina.core.StandardService.initialize (StandardService.java:579) at org.apache.catalina.core.StandardServer.initialize (StandardServer.java:2245) at org.apache.catalina.startup.CatalinaService.load (CatalinaService.java:234) at org.apache.catalina.startup.CatalinaService.load (CatalinaService.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at
DO NOT REPLY [Bug 15307] New: - Bad encoding for the part of pages included with %@ include file...
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=15307.
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=15307
Bad encoding for the part of pages included with %@ include file...
Summary: Bad encoding for the part of pages included with %@
include file...
Product: Tomcat 4
Version: 4.1.16
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
If the top level page is in other encoding as ISO-8859-1 eg. UTF-8 the included
page doesn't get the encoding of higher level, but have only ISO-8859-1.
I think, that the bug is in the method
org.apache.jasper.compiler.ParserController.figureOutJspDocument()
I repair at home this bug with changing this block:
if (newEncoding == null) {
newEncoding = ISO8859-1;
}
to the:
if (newEncoding == null) {
newEncoding = topFileEncoding;
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Inputs from a Tomcat user.
On 12/12/02 5:28 Sriram N [EMAIL PROTECTED] wrote: Also, I've always respected Pier's views on a number of topics, but I do feel that crap is a very flexible adjective. The users I help out with Tomcat are very pleased with the admin tool. Bunch of loosers who're not able to see a server.xml or web.xml in a text editor? Maybe, or maybe I'm one of those old farts who grew up with a command line instead that a nice GUI (yes, I started off with those nifty green phospores 8008s). The admin tool might be a good addition. It is not _required_. And following Byron's law: give too much power to lusers and they're going to screw up your system. Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: using manager web application
The tomcat-dev list is for development questions/bugs please ask this question on the user list. Martin -Original Message- From: Eman Fattouh [mailto:[EMAIL PROTECTED]] Sent: 12 December 2002 10:16 To: [EMAIL PROTECTED] Subject: using manager web application dear all; i'm new in using Tomcat server, and i'm trying to deploy my applications on it. i tried to use manager web application through its web interface at http://myserver/manager/ i ftp my war file on server and try to install it but i couldn't it gives me connection time out i use it as follows: path: /var/tomcat4/webapps/prom config url:http://myserver/myfirsttrial war url: jar:file:/home/webdevtest/SourceWar/promo1.war!/ note that the war file exists on the server just in the location specified in war url field, and the folder i nedd the application to be unpacked to is prom and already created on server. i don't know what is the error in all what i mentioned above. please help me as soon as possible. Regards Eman -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Problem with Socket closing
Hi, Tomcat 4.1.12 OS: W2K JRE: Sun 1.4.1_01 (Originally found using 1.4.0) I am seeing a problem with Tomcat closing a socket connection and having a write error. This happens with both SSL and regular sockets (the log example that is at the end show an SSL example.) I can reproduce the problem at times but sometimes that test case works (and the page renders as it should.) Our website sits on top of a data warehouse and I mostly experience the problem with the pages that have the longer queries. Does anybody know why this happens? Is there a fix? What can I do to try figure out what is causing the problem? I have turned up the debugging level on Tomcat (to 1) and that didn't produce much more information. I have added (println) statements to my code to see if there is a problem in it. It appears that my code always completes even when the socket connection is broken. Basically, I am at a point where I don't know what to try next. Here is the log output: 2002-12-11 17:07:28 ApplicationDispatcher[] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 48) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:100) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:116) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2 46) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at
RE: Problem with Socket closing
I'm seeing something very similar on my system where we are running Tomcat 3.3. We basically got a URL object connection to our own server, and for some reason the URL class seems to do an unclean shutdown of the socket which results in socket write errors on the server. I don't understand why these errors gets reported to the logs, I would assume that a web server must expect clients to behave badly and disconnect without warning. I've learned to live with it rather than trying to fix it, but then again I'm on 3.3 you are on 4.1 and we might see different problems. Martin -Original Message- From: Greg Strobl [mailto:[EMAIL PROTECTED]] Sent: 12 December 2002 14:38 To: '[EMAIL PROTECTED]' Subject: Problem with Socket closing Hi, Tomcat 4.1.12 OS: W2K JRE: Sun 1.4.1_01 (Originally found using 1.4.0) I am seeing a problem with Tomcat closing a socket connection and having a write error. This happens with both SSL and regular sockets (the log example that is at the end show an SSL example.) I can reproduce the problem at times but sometimes that test case works (and the page renders as it should.) Our website sits on top of a data warehouse and I mostly experience the problem with the pages that have the longer queries. Does anybody know why this happens? Is there a fix? What can I do to try figure out what is causing the problem? I have turned up the debugging level on Tomcat (to 1) and that didn't produce much more information. I have added (println) statements to my code to see if there is a problem in it. It appears that my code always completes even when the socket connection is broken. Basically, I am at a point where I don't know what to try next. Here is the log output: 2002-12-11 17:07:28 ApplicationDispatcher[] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 48) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat ionDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(Appli cationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(Applica tionDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:100) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat ionDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(Appli cationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(Applica tionDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:116) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilt er(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli cationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardW rapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardC ontextValve.ja va:191) at
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session PersistentManagerBase.java StandardSession.java
jfclere 2002/12/12 07:11:53
Modified:catalina/src/share/org/apache/catalina/session
PersistentManagerBase.java StandardSession.java
Log:
Calling session.setId() was removing the session from the store.
Revision ChangesPath
1.6 +6 -5
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java
Index: PersistentManagerBase.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- PersistentManagerBase.java9 Dec 2002 15:57:43 - 1.5
+++ PersistentManagerBase.java12 Dec 2002 15:11:53 - 1.6
@@ -853,7 +853,8 @@
log(sm.getString(persistentManager.swapIn, id));
session.setManager(this);
-session.setId(id); // To make sure the listener knows about it.
+// make sure the listeners know about it.
+((StandardSession)session).tellNew();
add(session);
((StandardSession)session).activate();
1.8 +13 -4
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/StandardSession.java
Index: StandardSession.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/StandardSession.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- StandardSession.java 5 Dec 2002 13:52:51 - 1.7
+++ StandardSession.java 12 Dec 2002 15:11:53 - 1.8
@@ -373,6 +373,15 @@
if (manager != null)
manager.add(this);
+tellNew();
+}
+
+
+/**
+ * Inform the listeners about the new session.
+ *
+ */
+public void tellNew() {
// Notify interested session event listeners
fireSessionEvent(Session.SESSION_CREATED_EVENT, null);
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Bill Barker wrote: Urm, err, the users that can't read may include you ;-). Jon withdrew the vote above. This means that this is officially 'not getting anywhere', at least until Jon re-submits his re-worked proposal. The fact that Jon withdrew the vote doesn't change any of the arguments and opinions that were expressed about profiles and minimal. IMO we are very close to consensus on profiles, and I think we can rich a consensus on an embeded. I think we should just change the subject line - and have another vote to make sure we're all on the same page. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Costin Manolache wrote: Bill Barker wrote: I think we should just change the subject line - and have another vote to make sure we're all on the same page. Sure, go ahead :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] minimal JSR 154 only distribution
Costin Manolache wrote: Bill Barker wrote: Urm, err, the users that can't read may include you ;-). Jon withdrew the vote above. This means that this is officially 'not getting anywhere', at least until Jon re-submits his re-worked proposal. The fact that Jon withdrew the vote doesn't change any of the arguments and opinions that were expressed about profiles and minimal. IMO we are very close to consensus on profiles, and I think we can rich a consensus on an embeded. I think we should just change the subject line - and have another vote to make sure we're all on the same page. Agreed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt
remm2002/12/12 07:47:29 Modified:.RELEASE-NOTES-4.1.txt Log: - An entry wasn't in the right category. Revision ChangesPath 1.38 +5 -5 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt Index: RELEASE-NOTES-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt,v retrieving revision 1.37 retrieving revision 1.38 diff -u -r1.37 -r1.38 --- RELEASE-NOTES-4.1.txt 11 Dec 2002 07:51:48 - 1.37 +++ RELEASE-NOTES-4.1.txt 12 Dec 2002 15:47:29 - 1.38 @@ -563,6 +563,10 @@ [4.1.17] CGIServlet, SSIServlet: Fix for SSI normal configuration which invokes a CGI script. +[4.1.17] #15239 + NamingResourcesMBean: + Fix resource link creation. + Coyote Bug Fixes: @@ -699,10 +703,6 @@ [4.1.17] ThreadPool: Reduce synchronization by using an array of threads instead of a Vector. - -[4.1.17] #15239 - NamingResourcesMBean: - Fix resource link creation. [4.1.17] #15258 JK 2 ChannelSocket: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Problem with Socket closing
See bug 12810 -Original Message- From: Greg Strobl [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 9:38 AM To: '[EMAIL PROTECTED]' Subject: Problem with Socket closing Hi, Tomcat 4.1.12 OS: W2K JRE: Sun 1.4.1_01 (Originally found using 1.4.0) I am seeing a problem with Tomcat closing a socket connection and having a write error. This happens with both SSL and regular sockets (the log example that is at the end show an SSL example.) I can reproduce the problem at times but sometimes that test case works (and the page renders as it should.) Our website sits on top of a data warehouse and I mostly experience the problem with the pages that have the longer queries. Does anybody know why this happens? Is there a fix? What can I do to try figure out what is causing the problem? I have turned up the debugging level on Tomcat (to 1) and that didn't produce much more information. I have added (println) statements to my code to see if there is a problem in it. It appears that my code always completes even when the socket connection is broken. Basically, I am at a point where I don't know what to try next. Here is the log output: 2002-12-11 17:07:28 ApplicationDispatcher[] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 48) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat ionDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(Appli cationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(Applica tionDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:100) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat ionDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(Appli cationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(Applica tionDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:116) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilt er(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli cationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardW rapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardC ontextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(Certificat esValve.java:2 46) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at
DO NOT REPLY [Bug 15314] New: - Apache realm treated differently on Win32 and *NIX
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=15314. 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=15314 Apache realm treated differently on Win32 and *NIX Summary: Apache realm treated differently on Win32 and *NIX Product: Tomcat 4 Version: 4.1.12 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Scenario: A directory served by Apache (and tomcat for JSP/servlets) is protected by htaccess - Apache handles auth and sets RemoteUser and AuthType. The authType is basic (using crypt'd passwords in a file). When a user is challenged, upon authenticating successfully (ie Apache asks Tomcat to serve page via connector) On Win32: - request.getRemoteUser() shows the user auth'd by Apache correctly - request.getAuthType() shows 'null' whereas on *NIX (seen on Linux and Solaris): - request.getRemoteUser() shows 'null' - request.getAuthType() shows 'Basic' -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15315] New: - Error in catalina.sh for cygwin/XP
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=15315. 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=15315 Error in catalina.sh for cygwin/XP Summary: Error in catalina.sh for cygwin/XP Product: Tomcat 4 Version: 4.1.9 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I tried deploying a JAR file in the WEB-INF/lib/ directory, I got an exception similar to that described in http://www.mail-archive.com/tomcat- [EMAIL PROTECTED]/msg75929.html. I found a solution: changing the catalina.sh script as follows worked for me: 102a103 CATALINA_TMPDIR=`cygpath --path --windows $CATALINA_TMPDIR` The problem was that the TMPDIR was specified in a Cygwin way, which did not work. All the other paths were changed to Windows-style, but I guess you forgot about the TMPDIR. Note that I am actually on 4.1.12, but that version is not listed in Bugzilla, so I couldn't select that. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Problem with Socket closing
My problem is similar but different. First, the client/user is not disconnecting - knowingly anyway. (Unless the browser is disconnecting on it's own for some reason.) When I am able to reproduce this, the browser gets back some of the output, but not all . I am not manually disconnecting - once again it would be the browser. Second, I have been able to reproduce this using Netscape 7.0 as the client. Therefore, it is not isolated to IE. Maybe the problem is the same, but is not restricted to just IE? -Original Message- From: John Trollinger [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 9:52 AM To: 'Tomcat Developers List' Subject: RE: Problem with Socket closing See bug 12810 -Original Message- From: Greg Strobl [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 9:38 AM To: '[EMAIL PROTECTED]' Subject: Problem with Socket closing Hi, Tomcat 4.1.12 OS: W2K JRE: Sun 1.4.1_01 (Originally found using 1.4.0) I am seeing a problem with Tomcat closing a socket connection and having a write error. This happens with both SSL and regular sockets (the log example that is at the end show an SSL example.) I can reproduce the problem at times but sometimes that test case works (and the page renders as it should.) Our website sits on top of a data warehouse and I mostly experience the problem with the pages that have the longer queries. Does anybody know why this happens? Is there a fix? What can I do to try figure out what is causing the problem? I have turned up the debugging level on Tomcat (to 1) and that didn't produce much more information. I have added (println) statements to my code to see if there is a problem in it. It appears that my code always completes even when the socket connection is broken. Basically, I am at a point where I don't know what to try next. Here is the log output: 2002-12-11 17:07:28 ApplicationDispatcher[] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 48) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat ionDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(Appli cationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(Applica tionDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:100) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat ionDispatcher. java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward(Appli cationDispatch er.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward(Applica tionDispatcher .java:356) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:427) at org.apache.jsp.page_jsp._jspService(page_jsp.java:116) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServlet Wrapper.java:2 04) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet .java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilt er(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli cationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardW rapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValv eContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipel ine.java:480) at
RE: DO NOT REPLY [Bug 15315] New: - Error in catalina.sh for cygwin/XP
This is fixed in 4.1.17 alpha. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 5:01 PM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 15315] New: - Error in catalina.sh for cygwin/XP 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.cg i?id=15315. 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=15315 Error in catalina.sh for cygwin/XP Summary: Error in catalina.sh for cygwin/XP Product: Tomcat 4 Version: 4.1.9 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I tried deploying a JAR file in the WEB-INF/lib/ directory, I got an exception similar to that described in http://www.mail-archive.com/tomcat- [EMAIL PROTECTED]/msg75929.html. I found a solution: changing the catalina.sh script as follows worked for me: 102a103 CATALINA_TMPDIR=`cygpath --path --windows $CATALINA_TMPDIR` The problem was that the TMPDIR was specified in a Cygwin way, which did not work. All the other paths were changed to Windows-style, but I guess you forgot about the TMPDIR. Note that I am actually on 4.1.12, but that version is not listed in Bugzilla, so I couldn't select that. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PATCH] mod_jk - chroot and user issues
Henri Gomez wrote:
I'm fine with the makefile updates but there is a problem with change in
apache-1.3/mod_jk.c since there is no ap_server_strip_chroot call
available on my Linux box.
Is it an OpenBSD specific call ?
Yes. My bad here. I mistakenly assumed that the chroot feature in OpenBSD's
Apache was not specific to OpenBSD. I thought they just changed the default
setting of an existing feature.
If so we'll have to add some #ifdef OPEN_BSD and I'd like to
have others jk commiters opinion. (I allready put too much
#ifdef AS400 ;)
I'll be to use a #ifdef CHROOTED_APACHE :
FWIW, I like the feature based define. If other OS's or Apache incorporate
OpenBSD's chroot option, then it wouldn't need to be changed. On the other
hand, if the consensus is not to commit the patch into mod_jk to keep the
cruft down, the OpenBSD port can apply the patch (assuming my port is
committed).
@@ -1742,7 +1746,7 @@ static void jk_init(server_rec *s, ap_po
/* Open up log file */
if(conf-log_file conf-log_level = 0) {
if(!jk_open_file_logger((conf-log), conf-log_file,
conf-log_level)) {
#ifdef CHROOTED_APACHE
conf-log = main_log;
#else
conf-log = NULL;
#endif
} else {
main_log = conf-log;
}
I'm thinking the jk_init change is not OpenBSD chroot specific. If someone
configures Apache's ServerType as standalone combined with the User/Group
directives, I think the problem I described with the log file would occur.
Isn't the conf-log = main_log behavior more generally more desirable?
Regards,
-Kurt
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties
luehe 2002/12/12 09:44:38
Modified:jasper2/src/share/org/apache/jasper/compiler
TagLibraryInfoImpl.java
jasper2/src/share/org/apache/jasper/resources
messages.properties
Log:
Removed support for tag file paths relative to TLD, until they are
supported by the spec.
Tag file paths must start with /WEB-INF/tags or /META-INF/tags.
Revision ChangesPath
1.28 +6 -13
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/TagLibraryInfoImpl.java
Index: TagLibraryInfoImpl.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/TagLibraryInfoImpl.java,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- TagLibraryInfoImpl.java 28 Nov 2002 04:18:08 - 1.27
+++ TagLibraryInfoImpl.java 12 Dec 2002 17:44:38 - 1.28
@@ -436,18 +436,11 @@
}
}
-path = path.replace('\\', '/');
- if (!path.startsWith(/)) {
- // Tag file path is relative to uri of TLD file
-path = uri.substring(0, uri.lastIndexOf(/) + 1) + path;
- try {
- path = new File(path).getCanonicalPath();
- } catch (IOException ioe) {
- throw new JasperException(ioe);
- }
- } else if (path.startsWith(/META-INF/tags)) {
+ if (path.startsWith(/META-INF/tags)) {
// Tag file packaged in JAR
ctxt.getTagFileJars().put(path, jarFile);
+ } else if (!path.startsWith(/WEB-INF/tags)) {
+ err.jspError(jsp.error.tagfile.illegalPath, path);
}
TagInfo tagInfo = TagFileProcessor.parseTagFile(parserController,
1.68 +2 -2
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties
Index: messages.properties
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -r1.67 -r1.68
--- messages.properties 10 Dec 2002 21:33:36 - 1.67
+++ messages.properties 12 Dec 2002 17:44:38 - 1.68
@@ -339,6 +339,6 @@
jsp.error.multiple.jspoutput = Cannot have multiple occurrences of
lt;jsp:outputgt;
jsp.error.attributes.not.allowed = {0} must not have any attributes
jsp.error.tagfile.badSuffix=Missing \.tag\ suffix in tag file path {0}
-jsp.error.tagfile.illegalPath=Missing \/WEB-INF/tags\ or \/META-INF/tags\ in
tag file path {0}
+jsp.error.tagfile.illegalPath=Illegal tag file path: {0}, must start with
\/WEB-INF/tags\ or \/META-INF/tags\
jsp.error.plugin.wrongRootElement=Name of root element in {0} different from {1}
jsp.error.attribute.invalidPrefix=The attribute prefix {0} does not correspond to
any imported tag library
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 14973] - wildcards using mod_jk
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=14973. 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=14973 wildcards using mod_jk --- Additional Comments From [EMAIL PROTECTED] 2002-12-12 18:29 --- I tried it with mod_jk-1.3.27.dll and it works fine. I won't find the time to install Apache 2.0 at the moment, but if this stays open I will try it after christmess (though I don't doubt it will run as well). Thank you very much for your effort anyway, Olivier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 14973] - wildcards using mod_jk
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=14973. 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=14973 wildcards using mod_jk --- Additional Comments From [EMAIL PROTECTED] 2002-12-12 18:55 --- Zut! I made a stupid mistake in my testing environment. It does NOT work with mod_jk-1.3.27.dll, though the behaviour has changed. Before, a leading * (asterisk) made apache forward everything to tomcat, now the statement will rather be ignored. I will test with apache 2.0 and mod_jk-2.0.43.dll after christmas. Ahoy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
mod_jk2 2.0.2 Linux build
Dear JK2 developers, Could you please upload linux-i386 build of mod_jk2 2.0.2 to apache web site Thank you very much Alex Roytman -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [newbie] where do I get TagFileInfo, etc.?
Sorry for not responding earlier. When checking out files from jakarta-tomcat-jasper, make sure to use the tag tomcat_4_branch. The head branch is an implementation of JSP 2.0, and is used for building TC5.0. Good luck! Date: Sat, 07 Dec 2002 14:57:24 -0800 From: Michael [EMAIL PROTECTED] Subject: Re: [newbie] where do I get TagFileInfo, etc.? To: Tomcat Developers List [EMAIL PROTECTED] Kin-Man Chung wrote: It's in jakarta-servletapi-4, which IS mentioned in BUILDING_txt. Make sure that you have servlet.home defined correctly in build.properties. I'm trying to build jakarta-tomcat-4.0, but it wanted jakarta-tomcat-jasper (not mentioned in BUILDING.txt). I checked that out, but it's build fails with undefined symbols. Where can I find these? I was relying on Debian's libservlet2.3-java package. But it's not in jakarta-servletapi-4, either. I built that, and pointed jakarta-tomcat-4.0/build.properties to it, but get the same errors. I grepped the tree, too, and couldn't find 'package.*javax\.servlet\.jsp\.el', for example. So far, I've got the CVS from jakarta-servletapi-4 jakarta-tomcat-connectors jakarta-tomcat-4.0 jakarta-tomcat-jasper Thanks. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15337] New: - ArrayIndexOutOfBoundException thrown when bad JSP provided to Jasper parser
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=15337. 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=15337 ArrayIndexOutOfBoundException thrown when bad JSP provided to Jasper parser Summary: ArrayIndexOutOfBoundException thrown when bad JSP provided to Jasper parser Product: Tomcat 5 Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Given the following invalid JSP page: --- Invalid.jsp jsp:plugin code=foo.class codebase=/ The following exception is raised: [java] /pre/ppbroot cause/b prejava.lang.ArrayIndexOutOfBoundsException: 329 [java] at org.apache.jasper.compiler.JspReader.peekChar(JspReader.java:222) [java] at org.apache.jasper.compiler.JspReader.isSpace(JspReader.java:412) [java] at org.apache.jasper.compiler.JspReader.skipSpaces(JspReader.java:320) [java] at org.apache.jasper.compiler.JspReader.matchesOptionalSpacesFollowedBy(JspReader.java:309) I think Jasper could report this a bit better stating the action isn't closed vs. what is currently returned. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 15338] New: - jsp:params action used outside of the expected context yields misleading error message.
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=15338. 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=15338 jsp:params action used outside of the expected context yields misleading error message. Summary: jsp:params action used outside of the expected context yields misleading error message. Product: Tomcat 5 Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Given the following JSP: InvalidUsage.jsp --- jsp:params jsp:param name=param1 value=value1 / /jsp:params - The following error is returned: org.apache.jasper.JasperException: /JspParamsUsageContextTest.jsp(10,5) The action is not a recognizable standard action. This is misleading as jsp:params is a standard action. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties messages_es.properties messages_fr.properties messages_ja.properties
luehe 2002/12/12 14:30:30
Modified:jasper2/src/share/org/apache/jasper/resources
messages.properties messages_es.properties
messages_fr.properties messages_ja.properties
Log:
Added error message for jsp.error.plugin.badtype error code
Revision ChangesPath
1.69 +2 -2
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties
Index: messages.properties
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -r1.68 -r1.69
--- messages.properties 12 Dec 2002 17:44:38 - 1.68
+++ messages.properties 12 Dec 2002 22:30:30 - 1.69
@@ -107,8 +107,8 @@
jsp.error.closeindividualparam=param tag needs to be closed with \/\
jsp.error.closeparams=param tag needs to be closed with /params
jsp.error.plugin.notype=type not declared in jsp:plugin
+jsp.error.plugin.badtype=Illegal value for 'type' attribute in jsp:plugin: must be
'bean' or 'applet'
jsp.error.plugin.nocode=code not declared in jsp:plugin
-jsp.error.plugin.notclosed=jsp:plugin not closed
jsp.error.ise_on_clear=Illegal to clear() when buffer size == 0
jsp.error.setproperty.beanNotFound=setProperty: Bean {0} not found
jsp.error.getproperty.beanNotFound=getProperty: Bean {0} not found
1.26 +1 -2
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_es.properties
Index: messages_es.properties
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_es.properties,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- messages_es.properties9 Dec 2002 23:27:03 - 1.25
+++ messages_es.properties12 Dec 2002 22:30:30 - 1.26
@@ -86,7 +86,6 @@
jsp.error.closeparams=el tag param necesita ser cerrado con /params
jsp.error.plugin.notype=tipo no declarado en jsp:plugin
jsp.error.plugin.nocode=codigo no declarado en jsp:plugin
-jsp.error.plugin.notclosed=jsp:plugin no cerrado
jsp.error.ise_on_clear=Es ilegal usar clear() cuando el tamaño del buffer es 0
jsp.error.setproperty.beanNotFound=setProperty: Bean {0} no encontrado
jsp.error.getproperty.beanNotFound=getProperty: Bean {0} no encontrado
1.9 +1 -2
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_fr.properties
Index: messages_fr.properties
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_fr.properties,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- messages_fr.properties9 Dec 2002 23:27:03 - 1.8
+++ messages_fr.properties12 Dec 2002 22:30:30 - 1.9
@@ -107,7 +107,6 @@
jsp.error.closeparams=Le tag param tag doit être fermé avec /params
jsp.error.plugin.notype=type non déclaré dans jsp:plugin
jsp.error.plugin.nocode=code non déclaré dans jsp:plugin
-jsp.error.plugin.notclosed=jsp:plugin non fermé
jsp.error.ise_on_clear=Il est interdit d''utiliser clear() quand la taille de
tampon== 0
jsp.error.setproperty.beanNotFound=setProperty: le Bean {0} est introuvable
jsp.error.getproperty.beanNotFound=getProperty: le Bean {0} est introuvable
1.26 +1 -2
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_ja.properties
Index: messages_ja.properties
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages_ja.properties,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- messages_ja.properties9 Dec 2002 23:27:03 - 1.25
+++ messages_ja.properties12 Dec 2002 22:30:30 - 1.26
@@ -98,7 +98,6 @@
jsp.error.closeparams=param\u30bf\u30b0\u306f/params\u3067\u9589\u3058\u306a\u3051\u308c\u3070\u3044\u3051\u307e\u305b\u3093
jsp.error.plugin.notype=jsp:plugin\u3067type\u5c5e\u6027\u304c\u5ba3\u8a00\u3055\u308c\u3066\u3044\u307e\u305b\u3093
jsp.error.plugin.nocode=jsp:plugin\u3067code\u5c5e\u6027\u304c\u5ba3\u8a00\u3055\u308c\u3066\u3044\u307e\u305b\u3093
-jsp.error.plugin.notclosed=jsp:plugin\u304c\u9589\u3058\u3066\u3044\u307e\u305b\u3093
jsp.error.ise_on_clear=\u30d0\u30c3\u30d5\u30a1\u30b5\u30a4\u30ba\u304c0\u306e\u6642\u306bclear()\u3092\u5b9f\u884c\u3057\u3066\u3082\u7121\u52b9\u3067\u3059
jsp.error.setproperty.beanNotFound=setProperty: Bean {0}
\u304c\u898b\u3064\u304b\u308a\u307e\u305b\u3093
DO NOT REPLY [Bug 15338] - jsp:params action used outside of the expected context yields misleading error message.
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=15338. 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=15338 jsp:params action used outside of the expected context yields misleading error message. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources messages.properties
luehe 2002/12/12 14:57:43
Modified:jasper2/src/share/org/apache/jasper/compiler Parser.java
jasper2/src/share/org/apache/jasper/resources
messages.properties
Log:
Fixed 15338: jsp:params action used outside of the expected context yields
misleading error message.
Revision ChangesPath
1.45 +5 -3
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Parser.java
Index: Parser.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Parser.java,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- Parser.java 12 Dec 2002 03:30:58 - 1.44
+++ Parser.java 12 Dec 2002 22:57:43 - 1.45
@@ -1196,6 +1196,8 @@
parsePlugin(parent);
} else if (reader.matches(element)) {
parseElement(parent);
+ } else if (reader.matches(params)) {
+ err.jspError(start, jsp.error.params.invalidUse);
} else if (reader.matches(param)) {
err.jspError(start, jsp.error.param.invalidUse);
} else {
1.70 +2 -1
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties
Index: messages.properties
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/resources/messages.properties,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- messages.properties 12 Dec 2002 22:30:30 - 1.69
+++ messages.properties 12 Dec 2002 22:57:43 - 1.70
@@ -104,6 +104,7 @@
jsp.error.overflow=Error: JSP Buffer overflow
jsp.error.paramexpected=Expected \param\ tag with \name\ and \value\
attributes
jsp.error.param.invalidUse=The jsp:param action must not be used outside the
jsp:include, jsp:forward, or jsp:params elements
+jsp.error.params.invalidUse=The jsp:params action must be a direct child of
jsp:plugin
jsp.error.closeindividualparam=param tag needs to be closed with \/\
jsp.error.closeparams=param tag needs to be closed with /params
jsp.error.plugin.notype=type not declared in jsp:plugin
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java
luehe 2002/12/12 15:31:52
Modified:jasper2/src/share/org/apache/jasper/runtime
JspRuntimeLibrary.java
jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
Added support for named attributes whose associated attributes are of primitive type
Revision ChangesPath
1.12 +10 -3
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/JspRuntimeLibrary.java
Index: JspRuntimeLibrary.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/JspRuntimeLibrary.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- JspRuntimeLibrary.java11 Dec 2002 22:34:06 - 1.11
+++ JspRuntimeLibrary.java12 Dec 2002 23:31:51 - 1.12
@@ -142,6 +142,13 @@
return new Character(s.charAt(0));
}
+public static char getChar(String s) throws JasperException {
+ if (s.length() == 0) {
+ err.jspError(jsp.error.bad_string_Character);
+ }
+ return s.charAt(0);
+}
+
// __begin convertMethod
public static Object convert(String propertyName, String s, Class t,
Class propertyEditorClass)
1.141 +38 -16
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
Index: Generator.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
retrieving revision 1.140
retrieving revision 1.141
diff -u -r1.140 -r1.141
--- Generator.java12 Dec 2002 03:30:58 - 1.140
+++ Generator.java12 Dec 2002 23:31:51 - 1.141
@@ -2537,7 +2537,10 @@
} else if (c == String.class) {
return quoted;
} else if (c == boolean.class) {
- return Boolean.valueOf(s).toString();
+ if (isNamedAttribute)
+ return Boolean.valueOf( + s + ).booleanValue();
+ else
+ return Boolean.valueOf(s).toString();
} else if (c == Boolean.class) {
if (isNamedAttribute)
return new Boolean( + s + );
@@ -2553,14 +2556,18 @@
// Detect format error at translation time
return new Byte((byte) + Byte.valueOf(s).toString() + );
} else if (c == char.class) {
- // non-normative (normative method would fail to compile)
- if (s.length() 0) {
- char ch = s.charAt(0);
- // this trick avoids escaping issues
- return ((char) + (int) ch + );
+ if (isNamedAttribute) {
+ return org.apache.jasper.runtime.JspRuntimeLibrary.getChar( + s
+ );
} else {
- throw new NumberFormatException(
-err.getString(jsp.error.bad_string_char));
+ // non-normative (normative method would fail to compile)
+ if (s.length() 0) {
+ char ch = s.charAt(0);
+ // this trick avoids escaping issues
+ return ((char) + (int) ch + );
+ } else {
+ throw new NumberFormatException(
+err.getString(jsp.error.bad_string_char));
+ }
}
} else if (c == Character.class) {
if (isNamedAttribute) {
@@ -2577,7 +2584,10 @@
}
}
} else if (c == double.class) {
- return Double.valueOf(s).toString();
+ if (isNamedAttribute)
+ return Double.valueOf( + s + ).doubleValue();
+ else
+ return Double.valueOf(s).toString();
} else if (c == Double.class) {
if (isNamedAttribute)
return new Double( + s + );
@@ -2585,7 +2595,10 @@
// Detect format error at translation time
return new Double( + Double.valueOf(s).toString() + );
} else if (c == float.class) {
- return Float.valueOf(s).toString() + f;
+ if (isNamedAttribute)
+ return Float.valueOf( + s + ).floatValue();
+ else
+ return Float.valueOf(s).toString() + f;
} else if (c == Float.class) {
if (isNamedAttribute)
return new Float( + s + );
@@ -2593,7 +2606,10 @@
// Detect format error at translation time
return new Float( + Float.valueOf(s).toString() + f);
} else if (c == int.class) {
- return
[PATCH] jakarta-tomcat-jasper (ImplicitTagLibraryInfo)
ImplicitTagLibraryInfo incorrectly returned null from getFunctions(). The spec requires a FunctionInfo[0] instead. Returning null also caused Generator.generateELFunctionMap to throw a NPE in some circumstances. Modified files: * jasper2/src/share/org/apache/jasper/compiler/ImplicitTagLibraryInfo.java --- Mark Roth JSP 2.0 Specification Co-Lead Sun Microsystems, Inc. Index: jasper2/src/share/org/apache/jasper/compiler/ImplicitTagLibraryInfo.java === RCS file: /home/cvspublic/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ImplicitTagLibraryInfo.java,v retrieving revision 1.15 diff -u -r1.15 ImplicitTagLibraryInfo.java --- jasper2/src/share/org/apache/jasper/compiler/ImplicitTagLibraryInfo.java28 Nov 2002 04:18:08 - 1.15 +++ jasper2/src/share/org/apache/jasper/compiler/ImplicitTagLibraryInfo.java13 Dec +2002 05:57:59 - @@ -61,6 +61,7 @@ package org.apache.jasper.compiler; import java.util.*; +import javax.servlet.jsp.tagext.FunctionInfo; import javax.servlet.jsp.tagext.TagLibraryInfo; import javax.servlet.jsp.tagext.TagInfo; import javax.servlet.jsp.tagext.TagFileInfo; @@ -100,6 +101,9 @@ this.pc = pc; this.tagFileMap = new Hashtable(); this.vec = new Vector(); + +// Implicit tag libraries have no functions: +this.functions = new FunctionInfo[0]; tlibversion = TLIB_VERSION; jspversion = JSP_VERSION; -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: DefaultServlet#getResources()
Yokota Takehiko wrote: Hi, all. I have a question about specification of org.apache.catalina.servlets.DefaultServlet#getResources() method. The comment for the method in the source code saids that This method will try to retrieve the resources through JNDI first, then in the servlet context if JNDI has failed, so I think the resources should be retrieved through JNDI first. However, actual implementation seems to retrieve the servlet context first, then retrieve JNDI. Could anyone answer this question? Using JNDI is slower. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] New committer: Filip Hanik
+1 -- Jeanfrancois Remy Maucherat wrote: I'd like to nominate Filip Hanik filip at filip.net as a committer on the Tomcat project. Filip has written the clustering code that was committed recently in the Tomcat 5 CVS, and is willing to maintain it, as well as continuing to improve it (including supporting large clusters). Filip is one of the authors of JavaGroups, the Java based clustering framework used in the new Tomcat clustering code. He has my +1. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[ANN] Apache Tomcat 4.1.17 Alpha released
Apache Tomcat 4.1.17 Alpha has just been released. Please help improve upcoming Tomcat releases by testing it. Note: This release is intended only for testing purposes, not for production use. Significant changes over 4.1.16 Beta include fixing socket binding in Coyote JK 2 (where only the loopback interface would be bound), administration webapp fixes for resource link handling, minor performance tweaks in the TCP endpoint, as well as other minor fixes. Downloads: http://www.apache.org/dist/jakarta/jakarta-tomcat-4.0/release/v4.1.17-alpha/ The full list of changes is available in the release notes. http://www.apache.org/dist/jakarta/jakarta-tomcat-4.0/release/v4.1.17-alpha/RELEASE-NOTES Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
