Re: mod_webapp gives Invalid virtual host name
Pier P. Fumagalli wrote: Eryq at [EMAIL PROTECTED] wrote: webapp-module-1.0-tc40b6 SunOS clin5 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-60 Apache 1.3.20 gcc 2.95.2 tomcat 4b6 Ok I built an Apache with dynamic loading, which is definitely working. I build mod_webapp, and try to start Apache. This: LoadModule webapp_module /path/to/mod_webapp.so works, but the following line: AddModule webapp_module AddModule mod_webapp.c Sounds better for me... complains that the module isn't loaded yet. ??? What's the exact message this one gives? If I comment out the AddModule line, then: WebAppConnection myConnection warp localhost:14108 works, That's pretty weird :) but: WebAppInfo /server-status-webapp/ gives me an Invalid virtual host name. I believe you didn't specify the ServerName directive in your httpd.conf What do I do now? Make sure that ServerName is specified _before_ WebAppInfo... And Port or use a virtual host VirtualHost. Should we use default value or Host/Port? Pier
Re: Different approach to TC as a service (was:SeparatingServicecode from Tomcat 4.0)
Pier P. Fumagalli wrote: Andy Armstrong at [EMAIL PROTECTED] wrote: Pier P. Fumagalli wrote: Andy Armstrong at [EMAIL PROTECTED] wrote: I only used JServ briefly before switching to Tomcat and it worked for me(tm). Can you recall any of the specific problems? It was back in 1997, and I remember several patches across 2 months from Ed Korthof just to make it work. But you should get back and see the archives. I remember it was a big pain in the ass (and that for Jserv 1.0 I was always starting Jserv stand alone!) Things improved ApacheJServ-1.1.2 works without problems on our BS2000 EBCDIC mainframes. The idea to have: httpd -- watchdog process -- service -- JVM with Tomcat Sounds Ok for me. I'll do some reading. Do you recall whether the problems where specific to that implementation of the startup code or more generically related to having the servlet container autostart? Oh, I remember it was about invoking the startup script, and also one big hassle was to shut down JServ from Apache, connecting to the port to issue a shutdown command... Good that remains me that I have to patch mod_jserv, that watchdog process holds the listen socket and it should not. (That does Address already in use making apachectl graceful when using mod_jserv). That is the only problem I have with mod_jserv :-) Pier
RE: 2 build suggestions
1) How hard would it be to remove the !(*.bat) files from /bin for .zip builds, and the same for the .gz builds !(*.sh)? Might make it a bit less confusing for people to see less files in there. As we're working with Java here - lots of us out here tend to work on multiple platforms (personally I switch back and forward all day between W2K and Linux) so: a) I'd like to get everything for multiplatform work in one go. b) When offered the same files compressed multiple ways I always just go for the smallest - I don't equate .gz with just UNIX (WinZip handles tar and gz just fine, and I have bzip, bzip2 for windows and unzip for UNIX). completely +1 on keeping it the way it is.. I do the same as you (at least for building tomcat, I switch around a lot..) Mvgr, Martin
RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3
Basically, there just wasn't time in the 3.2.2 release schedule to get this one fixed. Tomcat 3.2.3 was released earlier than planned due to a security problem and this bug hadn't been addressed yet. If someone would like to post a patch I will review and commit it. Marc Saegesser -Original Message- From: Stephen Dittmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 10:34 AM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Cc: Henry Yeh; Irene Pan; Jack Egan; Wayne Tang Subject: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3 I would like to know the status of this bug and what release it is going to be addressed in ? I found another person had filed bug 345 quite awhile back. We need the proper date header response back to browser so it won't reload staic files all the time. We don't want to use the IIS redirect as a way around this. This issue did not seem to get fixed/addressed in tomcat 3.2.3 which we just tried out. Here is a description of bug #345. Their is no date header in the Tomcat generated response, this is critical in case Tomcat is not running behind Apache e.g. According to the HTTP specs (RFC 2616) the Date header MUST be included by the origin server. --- Additional Comments From Marc Saegesser mailto:[EMAIL PROTECTED] 2001-03-21 11:46 --- This won't be addressed for Tomcat 3.2.2 but will be evaluated for a later release.
RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3
I posted one yesterday, for TC 3.2.3 and TC 3.3 !: - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Marc Saegesser [mailto:[EMAIL PROTECTED]] Sent: Friday, July 27, 2001 3:46 PM To: [EMAIL PROTECTED] Subject: RE: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3 Basically, there just wasn't time in the 3.2.2 release schedule to get this one fixed. Tomcat 3.2.3 was released earlier than planned due to a security problem and this bug hadn't been addressed yet. If someone would like to post a patch I will review and commit it. Marc Saegesser -Original Message- From: Stephen Dittmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 26, 2001 10:34 AM To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Cc: Henry Yeh; Irene Pan; Jack Egan; Wayne Tang Subject: I would like to know what tomcat release bug 345 was deferred to, still doesn't seem to be fixed on tomcat 3.2.3 I would like to know the status of this bug and what release it is going to be addressed in ? I found another person had filed bug 345 quite awhile back. We need the proper date header response back to browser so it won't reload staic files all the time. We don't want to use the IIS redirect as a way around this. This issue did not seem to get fixed/addressed in tomcat 3.2.3 which we just tried out. Here is a description of bug #345. Their is no date header in the Tomcat generated response, this is critical in case Tomcat is not running behind Apache e.g. According to the HTTP specs (RFC 2616) the Date header MUST be included by the origin server. --- Additional Comments From Marc Saegesser mailto:[EMAIL PROTECTED] 2001-03-21 11:46 --- This won't be addressed for Tomcat 3.2.2 but will be evaluated for a later release.
RE: BugRat Report #538 - Using an html file as the location in an error-page in web.xml causes a StackOverflowError.
Sorry - I've got no idea if it's been fixed in a later version - I've switched jobs and my new company uses Resin instead of Tomcat. You could try searching the mailing list archives - but your best bet is probably to upgrade (or just work round it and use a jsp page instead...) Good Luck! Catherine -Original Message- From: BugRat Mail System [SMTP:[EMAIL PROTECTED]] Sent: Friday, July 27, 2001 4:16 AM To: Catherine Jung; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: BugRat Report #538 - Using an html file as the location in an error-page in web.xml causes a StackOverflowError. - Sender's Comment - Hey Catherine, I saw this bug report on the website. Is this been fixed yet. I am using tomcat 3.2.1 and running into the same error. Hope you can provide me some pointers. Ashwin B-Bop Associates [EMAIL PROTECTED] - End Of Sender's Comment --- Report URL: http://znutar.cortexity.com/BugRatViewer/ShowReport/538 Report #538 Details Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: medium Severity: non-critical Confidence: public Environment: Release: 3.2 also 3.2b7 JVM Release: Sun 1.3 Operating System: Solaris OS Release: 7 Platform: Java Synopsis: Using an html file as the location in an error-page in web.xml causes a StackOverflowError. Description: Specifying an HTML file as the location of an error-page causes tomcat to go into a loop of webpage requests, until it hits a StackOverflowError. This problem doesn't occur if you specify a jsp page instead of an HTML file. java.lang.StackOverflowError at java.io.FileNotFoundException.(FileNotFoundException.java:62) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:64) at java.io.FileInputStream.(FileInputStream.java:95) at org.apache.tomcat.request.FileHandler.doService(StaticInterceptor.java:365 ) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.handleStatus(ContextManager.java:104 9) at org.apache.tomcat.request.FileHandler.doService(StaticInterceptor.java:387 ) repeat last 4 lines many, many times. tomcat prints this to console many times before throwing this error: 2000-12-06 05:11:16 - Ctx( /Greeting ): 404 R( /Greeting + /index.htm + null) null but nothing occurs in the error logs File: DataSource attachment 'Report-538.html'
[DOC] error in tomcat-4.0-doc build.bat example
Hi, there's a small error in the build.bat example preventing ant from running unless it is already present in the user's CLASSPATH both the html page and the example file are affected: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/source.html#Scripts http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/sample/ code rem Identify the custom class path components we need set CP=%TOMCAT_HOME%\lib\ant.jar;%TOMCAT_HOME%\lib\servlet.jar set CP=%TOMCAT_HOME%\lib\jaxp.jar;%TOMCAT_HOME%\lib\parser.jar set CP=%CP%;%JAVA_HOME%\lib\tools.jar code the third line should read: set CP=%CP%;%TOMCAT_HOME%\lib\jaxp.jar;%TOMCAT_HOME%\lib\parser.jar instead of set CP=%TOMCAT_HOME%\lib\jaxp.jar;%TOMCAT_HOME%\lib\parser.jar I'm also taking this opportunity to thank everyone involved in the project for the outstanding work so far, cheers, nicolas b.
[DOC] Resend of ROOT/index.html
Let's see if this works... Since it's been a while since I sent the last message, I'll paste the body: Here's my take on a new default index.html along with the jakarta banner since I've incorporated that in as well. I'd like it if all of the sample apps retained a somewhat similar look and feel (volunteering if people agree that it should be done). I tried this page under Opera and IE and it works fine. I'm scared to try NS! =) I'd really like the default apps to showcase Tomcat, and they've always been kind of clunky. IIRC, some of the JSP/Servlet example links don't work correctly. I'd also like the default homepage to brag about the features of Tomcat to some degree, e.g. session persistence and whatnot, but I don't know enough about these things yet... Of course, by mentioning this I'm implicitly volunteering to do it ;) - r !doctype html public -//w3c//dtd html 4.0 transitional//en http://www.w3.org/TR/REC-html40/strict.dtd; html head meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 titleJakarta Project - Tomcat Servlet Container (v4.0 - beta 5)/title style type=text/css !-- body { color: #00; background-color: #FF; font-family: Arial, Times New Roman, Times; font-size: 16px; } A:link { color: blue } A:visited { color: blue } td { color: #00; font-family: Arial, Times New Roman, Times; font-size: 16px; } .code { color: #00; font-family: Courier New, Courier; font-size: 16px; } -- /style /head body !-- Header -- table width=100% tr td align=left width=130a href=http://jakarta.apache.org/tomcat/index.html;img src=tomcat.gif height=92 width=130 border=0 alt=The Mighty Tomcat - MEOW!/td td align=left valign=top table trtd align=left valign=topbTomcat Servlet Container/b/td/tr trtd align=left valign=topbVersion 4.0 - Beta 5/b/td/tr /table /td td align=righta href=http://jakarta.apache.org/;img src=jakarta-banner.gif height=100 width=350 border=0 alt=The Jakarta Project/a/td /tr /table br table tr !-- Table of Contents -- td valign=top table width=100% border=1 cellspacing=0 cellpadding=3 bordercolor=#00 tr td bgcolor=#D2A41C bordercolor=#00 align=left nowrap font face=Verdana size=+1iWeb Applications/inbsp;nbsp;nbsp;nbsp;nbsp;nbsp;/font /td /tr tr td bgcolor=#FFDC75 bordercolor=#00 nowrap a href=examples/jsp/JSP Examples/abr a href=examples/servlets/Servlet Examples/abr a href=webdav/WebDAV capabilities/abr nbsp; /td /tr /table br table width=100% border=1 cellspacing=0 cellpadding=3 bordercolor=#00 tr td bgcolor=#D2A41C bordercolor=#00 align=left nowrap font face=Verdana size=+1iDocumentation/inbsp;nbsp;nbsp;nbsp;nbsp;nbsp;/font /td /tr tr td bgcolor=#FFDC75 bordercolor=#00 nowrap a href=docsTomcat User Documentation/abr a href=catalina-javadoc/index.htmlTomcat 4.0 API/abr a href=jasper-javadoc/index.htmlJasper (JSP engine) API/abr a href=servletapi-javadoc/index.htmlServlet 2.3 and JSP 1.2 API/abr nbsp; /td /tr /table br table width=100% border=1 cellspacing=0 cellpadding=3 bordercolor=#00 tr td bgcolor=#D2A41C bordercolor=#00 align=left nowrap font face=Verdana size=+1iMiscellaneous/inbsp;nbsp;nbsp;nbsp;nbsp;nbsp;/font /td /tr tr td bgcolor=#FFDC75 bordercolor=#00 nowrap a href=http://java.sun.com/products/jsp;Sun's Java Server Pages Site/abr a href=http://java.sun.com/products/servlet;Sun's Servlet Site/abr nbsp; /td /tr /table /td tdnbsp;nbsp;nbsp;nbsp;nbsp;/td !-- Body -- td align=left valign=top pcenterbIf you're seeing this page via a web browser, it means you've setup Tomcat successfully. Congratulations!/b/center/p pAs you may have guessed by now, this is the default Tomcat home page.
mod_webapp functionality issues...
I finally have the apache connector compiled and talking to tomcat. Unfortunatley, whenever I try to make use of a deployed webapp, I get a WebApp: Error 500 page. The error in the apache error logs are as follows: [Fri Jul 27 09:50:15 2001] [error] Not yet implemented There is no error message in any of the tomcat logs although the tomcat apache_log does show the connection from apache to tomcat. The webapp I am trying to experiment with is the /examples/ webapp. Is this functionality really not implemented? -- Eric L. Anderson [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/webapps/ROOT jakarta-banner.gif index.html
bip 01/07/27 10:38:17 Modified:webapps/ROOT index.html Added: webapps/ROOT jakarta-banner.gif Log: New design on the default landing page, thanks to Rob S [EMAIL PROTECTED] Submitted by: Rob S [EMAIL PROTECTED] Revision ChangesPath 1.22 +150 -69 jakarta-tomcat-4.0/webapps/ROOT/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/ROOT/index.html,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- index.html2001/07/20 06:14:10 1.21 +++ index.html2001/07/27 17:38:17 1.22 @@ -1,74 +1,155 @@ -!doctype html public -//w3c//dtd html 4.0 transitional//en +!doctype html public -//w3c//dtd html 4.0 transitional//en http://www.w3.org/TR/REC-html40/strict.dtd; html -head -meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 -meta name=GENERATOR content=Mozilla/4.72 [en] (WinNT; U) [Netscape] -meta name=Author content=Anil K. Vijendran -titleTomcat (v4.0-b7-dev)/title +head +meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 +titleJakarta Project - Tomcat (v4.0-b6-dev)/title +style type=text/css + !-- +body { +color: #00; +background-color: #FF; +font-family: Arial, Times New Roman, Times; +font-size: 16px; +} + +A:link { +color: blue +} + +A:visited { +color: blue +} + +td { +color: #00; +font-family: Arial, Times New Roman, Times; +font-size: 16px; +} + +.code { +color: #00; +font-family: Courier New, Courier; +font-size: 16px; +} + -- +/style /head -body bgcolor=#FF -img SRC=tomcat.gif height=92 width=130 align=LEFTbfont face=Arial, Helvetica, sans-seriffont size=+3Tomcat/font/font/b + +body + +!-- Header -- +table width=100% +tr +td align=left width=130a href=http://jakarta.apache.org/tomcat/index.html;img src=tomcat.gif height=92 width=130 border=0 alt=The Mighty Tomcat - MEOW!/td +td align=left valign=top +table +trtd align=left valign=topbTomcat/b/td/tr +trtd align=left valign=topbVersion 4.0-b6-dev/b/td/tr +/table +/td +td align=righta href=http://jakarta.apache.org/;img src=jakarta-banner.gif height=100 width=350 border=0 alt=The Jakarta Project/a/td +/tr +/table + br -bfont face=Arial, Helvetica, sans-seriffont size=-1Version -4.0-b7-dev/font/font/b -pThis is the default Tomcat home page. This page serves as a quick reference -guide to related resources and is located at: -ul -li -font face=Courier New, Courier,mono$TOMCAT_HOME/webapps/ROOT/index.html/font/li -/ul - -pIncluded within this release are functional examples with associated source -code, API documentation for servlets and JSP, a bREADME/b, a technical -bFAQ/b on this release and an assortment of ttjar/tt files which are -pre-requisites for continued development of web technologies including JSP -and Servlets./p - -pExamples:/p -ul -liba href=examples/jsp/JSP Examples/a/b/li -liba href=examples/servlets/Servlet Examples/a/b/li -liba href=webdav/WebDAV capabilities/a/b/li -/ul - -pDocumentation:/p -ul -liba href=catalina-javadoc/index.htmlAPI docs for Catalina -(servlet container)/a/b/li -liba href=jasper-javadoc/index.htmlAPI docs for Jasper -(JSP engine)/a/b/li -liba href=servletapi-javadoc/index.htmlAPI docs for Servlet 2.3 and -JSP 1.2 Packages/a/b/li -liba href=docsGeneral Tomcat User Documentation/a/b/li -/ul - -pYou can find more information about the JSP and Servlet technologies at:/p -ul -liba href=http://java.sun.com/products/jsp;Sun's Java Server Pages Site/a/b/li -liba href=http://java.sun.com/products/servlet;Sun's Servlet Site/a/b/li -/ul - -pand by subscribing to one or more of the following Servlet and JSP related -interest lists:/p -ul -liba href=mailto:[EMAIL PROTECTED]?subject=subscription request: jsp-interestbody=subscribe jsp-interest [Your Full Name][EMAIL PROTECTED]/a/b/li -liba href=mailto:[EMAIL PROTECTED]?subject=subscription request: servlet-interestbody=subscribe servlet-interest [Your Full Name][EMAIL PROTECTED]/a/b/li -/ul - -pIn addition, Tomcat-specific mailing lists are available at the Jakarta -project web site:/p -ul -liba href=mailto:[EMAIL PROTECTED];[EMAIL PROTECTED]/a/b for developers working on Tomcat/li -liba href=mailto:[EMAIL PROTECTED];[EMAIL PROTECTED]/a/b for general questions related to configuring and -using Tomcat/li -/ul - -hr -p align=rightfont
RE: [DOC] Resend of ROOT/index.html
-Original Message- From: Rob S. [mailto:[EMAIL PROTECTED]] [...] Here's my take on a new default index.html along with the jakarta banner since I've incorporated that in as well. I'd like it if all of the sample apps retained a somewhat similar look and feel (volunteering if people agree that it should be done). I tried this page under Opera and IE and it works fine. I'm scared to try NS! =) I've tried it in NS and it works fine. I'd really like the default apps to showcase Tomcat, and they've always been kind of clunky. IIRC, some of the JSP/Servlet example links don't work correctly. I'd also like the default homepage to brag about the features of Tomcat to some degree, e.g. session persistence and whatnot, but I don't know enough about these things yet... Of course, by mentioning this I'm implicitly volunteering to do it ;) Sounds great, If you feel like giving the default apps a more appealing look that goes well with what you just submitted I don't think anyone would disagree with updating them. Bip Thelin
[DOC] TC4 xdocs
Anakia is cool! =) I spent this morning getting familiar with it. The VTL looks kind of PERLish, but the sample vsl's I was looking at seem pretty cool, not too complicated. There isn't a vsl for the entire set of TC4 docs. We could always adopt the jakarta-site2 one, but I'd personally prefer if it looked a little cooler =p - r
Re: mod_webapp functionality issues...
Eric L. Anderson at [EMAIL PROTECTED] wrote: I finally have the apache connector compiled and talking to tomcat. Unfortunatley, whenever I try to make use of a deployed webapp, I get a WebApp: Error 500 page. The error in the apache error logs are as follows: [Fri Jul 27 09:50:15 2001] [error] Not yet implemented There is no error message in any of the tomcat logs although the tomcat apache_log does show the connection from apache to tomcat. The webapp I am trying to experiment with is the /examples/ webapp. Is this functionality really not implemented? You're using a FAR OLD copy of mod_webapp... Please update to the latest CVS version... Thank you :) Pier
Re: [DOC] TC4 xdocs
On Fri, 27 Jul 2001, Rob S. wrote: Anakia is cool! =) I spent this morning getting familiar with it. The VTL looks kind of PERLish, but the sample vsl's I was looking at seem pretty cool, not too complicated. There isn't a vsl for the entire set of TC4 docs. We could always adopt the jakarta-site2 one, but I'd personally prefer if it looked a little cooler =p If we're going to use Anakia, we should share the same stylesheet (which is also used in several other Jakarta projets) so that the docs all have the same look and feel. Additions to the overall stylesheet are welcomed, and can be discussed on the GENERAL@ mailing list (since they would affect all projects that use this). Also, I'm about 95% done with an XSLT stylesheet that behaves equivalent to the current site.vsl macros -- for those of us (like me) who prefer to use standard technologies (yes, Jon, the s word again :-). This XSLT stylesheet runs against the same XML files, and produces essentially equivalent HTML. It's executed using the Ant style tag (requires Xerces+Xalan, or the JAXP/1.1 release that also includes Xalan). I'll be checking this in to jakarat-site2 shortly. The only remaining issue I've got is the way that site.vsl uses the $relativePath variable without defining it anywhere, in creating relative URL references. According to Geir there's nothing in Velocity itself that predefines this, so it must be something magic Anakia is doing. The need for this thing is also questionable (it's an artifact of the way that Jon wanted to create a multi-directory-level document set with one stylesheet, and still having the navigation menu generarted correctly, instead of dealing with each directory level individually). But that can be dealt with in a separate conversation. - r Craig McClanahan
Re: [DOC] TC4 xdocs
On Fri, 27 Jul 2001, Craig R. McClanahan wrote: [snip] Also, I'm about 95% done with an XSLT stylesheet that behaves equivalent to the current site.vsl macros ... I just checked this stylesheet in (xdocs/stylesheets/site.xsl) into the jakarta-site2 repository, and modified the build.xml file there to include an example of using it. The relative paths conundrum is solved by transforming each directory level independently, rather than in a single recursive descent. Craig
cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html
craigmcc01/07/27 12:16:27 Modified:webapps/ROOT index.html Log: Update new web page to reflect b7-dev instead of b6-dev. Revision ChangesPath 1.23 +2 -2 jakarta-tomcat-4.0/webapps/ROOT/index.html Index: index.html === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/ROOT/index.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- index.html2001/07/27 17:38:17 1.22 +++ index.html2001/07/27 19:16:27 1.23 @@ -2,7 +2,7 @@ html head meta http-equiv=Content-Type content=text/html; charset=iso-8859-1 -titleJakarta Project - Tomcat (v4.0-b6-dev)/title +titleJakarta Project - Tomcat (v4.0-b7-dev)/title style type=text/css !-- body { @@ -44,7 +44,7 @@ td align=left valign=top table trtd align=left valign=topbTomcat/b/td/tr -trtd align=left valign=topbVersion 4.0-b6-dev/b/td/tr +trtd align=left valign=topbVersion 4.0-b7-dev/b/td/tr /table /td td align=righta href=http://jakarta.apache.org/;img src=jakarta-banner.gif height=100 width=350 border=0 alt=The Jakarta Project/a/td
Re: mod_webapp functionality issues...
On Fri, Jul 27, 2001 at 07:06:14PM +0100, Pier P. Fumagalli wrote: Eric L. Anderson at [EMAIL PROTECTED] wrote: I finally have the apache connector compiled and talking to tomcat. Unfortunatley, whenever I try to make use of a deployed webapp, I get a WebApp: Error 500 page. The error in the apache error logs are as follows: [Fri Jul 27 09:50:15 2001] [error] Not yet implemented There is no error message in any of the tomcat logs although the tomcat apache_log does show the connection from apache to tomcat. The webapp I am trying to experiment with is the /examples/ webapp. Is this functionality really not implemented? You're using a FAR OLD copy of mod_webapp... Please update to the latest CVS version... Thank you :) Ok. I have updated cvs from jakarta-tomcat-connector and rebuilt the connector. Now I get Invalid packet 255. This error does show up in the apache_log per the following: 2001-07-27 14:02:18 [org.apache.catalina.connector.warp.WarpRequestHandler] Invalid packet 22 On the tomcat side I am using the beta 6 release version. Should I now update Tomcat from cvs also? Thanks -- Eric L. Anderson [EMAIL PROTECTED]
Re: mod_webapp functionality issues...
Silly me. I rebuilt the apache connector from cvs without also rebuilding the included java portion of the connector. Perhaps the file is called README.txt for a reason... On Fri, Jul 27, 2001 at 02:26:15PM -0500, Eric L. Anderson wrote: On Fri, Jul 27, 2001 at 07:06:14PM +0100, Pier P. Fumagalli wrote: Eric L. Anderson at [EMAIL PROTECTED] wrote: I finally have the apache connector compiled and talking to tomcat. Unfortunatley, whenever I try to make use of a deployed webapp, I get a WebApp: Error 500 page. The error in the apache error logs are as follows: [Fri Jul 27 09:50:15 2001] [error] Not yet implemented There is no error message in any of the tomcat logs although the tomcat apache_log does show the connection from apache to tomcat. The webapp I am trying to experiment with is the /examples/ webapp. Is this functionality really not implemented? You're using a FAR OLD copy of mod_webapp... Please update to the latest CVS version... Thank you :) Ok. I have updated cvs from jakarta-tomcat-connector and rebuilt the connector. Now I get Invalid packet 255. This error does show up in the apache_log per the following: 2001-07-27 14:02:18 [org.apache.catalina.connector.warp.WarpRequestHandler] Invalid packet 22 On the tomcat side I am using the beta 6 release version. Should I now update Tomcat from cvs also? Thanks -- Eric L. Anderson [EMAIL PROTECTED] -- Eric L. Anderson [EMAIL PROTECTED]
RE: ehh small problem context/servlet reloading
Me again with some more info on the issue below. The following happens : When I do a specific scenario of servlet access then replace a servlet and start-up our login servlet I get the 503 error. The servlet has status 0 and should have status 3 (according to my debugging. All the other servlets are still working (to a certain point, because most of them depend on the servlet I am calling after the context is reloaded). I've been turning on debugging, added my own logging etc,etc.. But still I cannot find where the actual status of Request is set for that specific servlet, after the reloading that is. Can someone please help me in where to exactly look for this, because I cannot find it anymore. Didn't see anyone complain about this problem yet, so I like to fix it ;-)). I'm using tc33 from cvs btw To bad my debugger is horrible else it would be a little bit easier. Every The problem doesn't occur when : I call servlet A go to B goto C replace B and goto A again. (reloading is ok) The problem occurs when : I call servlet A go to B goto C goto D replace B and goto A again. (these are just my servlets, didn't test another scenario yet, I first wanted to find the problem ;-) Hope you guys can help to help me fix the bug and learn more about the internals of tomcat.. TIA.. Here is some logging of the reloading (the strange logging is mine ;-). 2001-07-27 12:08:38 - ReloadInterceptor: MVDB : after removeing context 2001-07-27 12:08:38 - Ctx() : X CALLING CONTEXT SETSATE XX 0 2001-07-27 12:08:38 - Ctx() : X LEAVING SETCONTEXT X 0 2001-07-27 12:08:38 - ContextManager: MVDB state ; 3 state_NEW 0 2001-07-27 12:08:38 - LogEvents: addContext DEFAULT:/ROOT 2001-07-27 12:08:38 - ReloadInterceptor: ADDCONTEXT in ReloadInterceptorDEFAULT: /ROOT 2001-07-27 12:08:38 - Ctx() : X CALLING CONTEXT SETSATE XX 0 2001-07-27 12:08:38 - Ctx() : X LEAVING SETCONTEXT X 0 2001-07-27 12:08:38 - ContextManager: Adding context DEFAULT:/ROOT 2001-07-27 12:08:38 - ContextManager: after adding context the state is : 1 2001-07-27 12:08:38 - ReloadInterceptor: MVDB: state after adding context..3 2001-07-27 12:08:38 - LogEvents: contextInit DEFAULT:/ROOT 2001-07-27 12:08:38 - SimpleMapper1: SM: extension map /*.jsp Ct (*.jsp ) DependManager: Added /usr/local/tomcat33dev/webapps/cubic/WEB-INF/web.xml web.xm l 2001-07-27 12:08:38 - Ctx() : X CALLING CONTEXT SETSATE XX 1 2001-07-27 12:08:38 - Ctx() : X LEAVING SETCONTEXT X 1 2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0 class : org.apache.tomcat.modules.config.PathSetter 2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0 class : org.apache.tomcat.modules.config.ServerXmlReader 2001-07-27 12:08:38 - LogEvents: contextMap R( + /servlet/cubic.adm.login + nul l) 2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0 class : org.apache.tomcat.modules.loggers.LogEvents 2001-07-27 12:08:38 - ContextManager: Host = swami.mvdb.com 2001-07-27 12:08:38 - ContextManager: SM: Prefix match /servlet/cubic.adm.login - /servlet/cubic.adm.login/* ServletH cubic.adm.login(SW (null CN=cubic.adm.log in)) null 2001-07-27 12:08:38 - SimpleMapper1: Adjust for prefix map /servlet/cubic.adm.lo gin 2001-07-27 12:08:38 - SimpleMapper1: SM: After mapping R( + /servlet/cubic.adm. login + null) ServletH cubic.adm.login(SW (null CN=cubic.adm.login)) 2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0 class : org.apache.tomcat.modules.mappers.SimpleMapper1 2001-07-27 12:08:38 - ContextManager: MVDB : showing servlet error Mvgr, Martin -Original Message- From: Martin van den Bemt [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 25, 2001 7:57 PM To: jakarta-tomcat-dev Subject: ehh small problem context/servlet reloading Hi, I use the latest version from cvs (not commits since my built..). When compiling a new servlet, the system tries to remove the context and add the context again (so far so good). I go the the servlet again and get : Error: 503 Location: /servlet/cubic.adm.login Application not available each time I try to go there it will remove/add the context. I can have a look at it (if you want) or maby someone can point into a direction of where to look for this problem.. Mvgr, Martin
Site Nitpick
Just a heads-up that the Tomcat site's index.html contains the following sentence: Version 3.3 is currently under development and the beta process is expected to begin shortly. Someone with commit access should probably update that so that users know the beta cycle has begun. - Christopher
Anyone has the patch to fixed the 'Date Header' not being sent in tomcat 3.2.3 ??
please forward it to me if you will. thanks! Hen
Re: [DOC] TC4 xdocs (tangent)
Since there is an active discussion about the Tomcat site itself, implying that someone may be about to do a little work on it, I have a simple suggestion. It would be a nice convenience if there were a new section on the download page, maybe under a separate one of those grayish-blue heading bars (entitled Software Prerequisites or something), with a list of links to all of the various external packages that Tomcat requires ... maybe with subsections of Common for packages required by both 3.x and 4.0, Additional for 3.x, Additional for 4.x, and Optional for packages required by the optional components of the either/both containers. It's all in the README files, of course, but it would be incredibly convenient if I could just start slamming downloads from a list of links on a single page. I know this because I just installed 4.0 on a machine for the first time (which me luck, I have almost no experience in the 4.0 branch :-), and I had to keep flipping back and forth between the README and my browser to grab the ~8 additional packages that I needed. I've had much worse inconveniences in my life, to be sure, but it would be a fairly simple add to the site. Just a thought ... Regards, Christopher P.S. You probably already know this (I think I saw a thread on it last week maybe), but someone should really fix the Catalina Configuration page so that either the background is not black or the links are white or something. It took me a minute or two to figure out that it actually contained information. If it is awaiting an Anakia/XSLT/DocBook/HTML/XML/Doxygen/God-Knows-What overhaul, in the meantime someone should at least fix it so that the links show up ... on the Jakarta site at the very least, if not in the distro CVS. I almost just assumed that the doc hadn't been written yet before I checked the page source on a whim. (Granted I have little knowledge of the 4.0 docs at this point, but neither do first-time users.)
Re: [DOC] TC4 xdocs (tangent)
Christopher Cain wrote: [snip] ... someone should really fix the Catalina Configuration page so that either the background is not black or the links are white or something. I'll even tell you the fix. categories.html: bgcolor=sky blue -- bgcolor=skyblue ;-)
cvs commit: jakarta-tomcat-4.0/catalina/docs/config categories.html
craigmcc01/07/27 15:05:43 Modified:catalina/docs/config categories.html Log: Fix the background color for this frame so it does not show up as black on some browsers. Submitted by: Christopher Cain [EMAIL PROTECTED] Revision ChangesPath 1.4 +1 -1 jakarta-tomcat-4.0/catalina/docs/config/categories.html Index: categories.html === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/docs/config/categories.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- categories.html 2001/02/26 03:48:44 1.3 +++ categories.html 2001/07/27 22:05:43 1.4 @@ -2,7 +2,7 @@ head titleCatalina Configuration Categories/title /head -body bgcolor=sky blue link=black vlink=black +body bgcolor=skyblue link=black vlink=black font size=2 h3Home/h3
Re: [DOC] TC4 xdocs (tangent)
On Fri, 27 Jul 2001, Christopher Cain wrote: Christopher Cain wrote: [snip] ... someone should really fix the Catalina Configuration page so that either the background is not black or the links are white or something. I'll even tell you the fix. categories.html: bgcolor=sky blue -- bgcolor=skyblue ;-) Just applied this patch ... will show up in tonight's nightly. Craig
Re: [DOC] TC4 xdocs (tangent)
On Fri, 27 Jul 2001, Christopher Cain wrote: Since there is an active discussion about the Tomcat site itself, implying that someone may be about to do a little work on it, That's a correct supposition. I'm planning on spending quite a bit of time working on the developer docs (while others have volunteered to focus on the user stuff). To that end, I wanted to use Ant's style tag with a global XSLT stylesheet that can be shared across projects (and is now checked in to jakarta-site2). I have a simple suggestion. It would be a nice convenience if there were a new section on the download page, maybe under a separate one of those grayish-blue heading bars (entitled Software Prerequisites or something), with a list of links to all of the various external packages that Tomcat requires ... maybe with subsections of Common for packages required by both 3.x and 4.0, Additional for 3.x, Additional for 4.x, and Optional for packages required by the optional components of the either/both containers. That's a good idea. I'm just about to check in some updates to the instructions for building Tomcat 4 from sources (including all the dependencies). I'll make sure it ends up on the web site as well (eventually). Craig
Sources in Binary Distributions
By habit (since before my time on Tomcat :-), we have shipped the source code (although not in a directly buildable arrangement) inside the binary distributions of Tomcat. This is certainly nice for people that want to look around and see how Tomcat works, but it is somewhat redundant since we make separate source distributions (that *are* directly buildable, because they are snapshots of the CVS repository) available anyway. For Tomcat 4, what do folks think of omitting the sources from the binary distribution? This would knock the size of the binary distributions down by around 2 megabytes (which I'm sure people would also appreciate). Craig McClanahan
cvs commit: jakarta-tomcat-4.0 BUILDING.txt RUNNING.txt README.txt build.xml INSTALL.txt build.bat build.sh
craigmcc01/07/27 15:26:03 Modified:.README.txt build.xml Added: .BUILDING.txt RUNNING.txt Removed: .INSTALL.txt build.bat build.sh Log: Update build and install documentation to current formats, similar to that used on jakarta-servletapi-4 and jakarta-watchdog-4.0. Remove the top level build.bat and build.sh scripts, since they are now unnecessary. TODO: Tweak the build.xml files (and corresponding BUILDING.txt notes) for configurability of the remaining packages that do not have documented property names you can override in build.properties. Revision ChangesPath 1.16 +61 -278 jakarta-tomcat-4.0/README.txt Index: README.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/README.txt,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- README.txt2001/03/30 21:23:24 1.15 +++ README.txt2001/07/27 22:26:03 1.16 @@ -1,281 +1,64 @@ - Apache Tomcat 4.0 - = +$Id: README.txt,v 1.16 2001/07/27 22:26:03 craigmcc Exp $ + The Tomcat 4.0 Servlet/JSP Container + -Introduction - +This subproject contains a server that conforms to the Servlet 2.3 and +JSP 1.2 specifications from Java Software. It includes the following contents: -This CVS module contains the code for Tomcat 4.0, and will also be -used for further development of 4.x versions. It is divided into several -major components, each of which you can build and use separately, that are -combined to create Tomcat. The components are: - -* Catalina - Servlet container conforming to the Servlet API Specification, - version 2.3 (currently in Initial Public Draft). - -* Jasper - JSP compiler and runtime environment conforming to the - JavaServer Pages (JSP) Specification, version 1.2 (currently in - Initial Public Draft). - -* Tester - Unit test web application, with tests that are primarily focused - on Tomcat features rather than spec compliance. - -* Webapps - Example and test web applications, and associated documentation, - that are packaged with Tomcat. - - -Installing Tomcat 4.0 Source Code -= - -In order to successfully build Tomcat 4.0, you will need to do the following. -In the instructions below, $JAKARTA_HOME is assumed to be the directory into -which you are installing all of the required Jakarta distributions. - -* Download and install a version 1.2 or later Java Development Kit - implementation for your operating system platform. Set a JAVA_HOME - environment variable to point at the directory where your JDK is installed, - and add $JAVA_HOME/bin to your PATH. Configure the CLASSPATH environment - variable as well, if required. - -* Download and install the Java Naming and Directory Interface (JNDI) package, - version 1.2.1 or later, from http://java.sun.com/products/jndi. Set an - environment variable JNDI_HOME pointing at the directory to which you - installed the distribution. None of the standard JNDI providers are required - unless you need them in your own applications. - -* If you want to have support for the JavaMail object factories, you must - download the JavaMail (Version 1.2 or later) and Java Activation Framework - (Version 1.0.1 or later), and make sure that the mail.jar and - activation.jar files, respectively, are on your CLASSPATH. - -* If you want to build in support for JNDI JDBC DataSources you need to - download the following packages and put their jar files in your classpath. - - Tyrex http://tyrex.exolab.org/ - - Java Transaction API (JTA) http://java.sun.com/products/jta - - Java JDBC 2.0 Optional Extensions http://java.sun.com/products/jdbc/ - -* If you are running a JDK earlier than 1.3, you will also need to place the - jndi.jar file on your CLASSPATH in order to build Tomcat. - -* Download and install the Java Secure Sockets Extension (JSSE) implementation - (current version number is 1.0.2) from http://java.sun.com/products/jsse. - Set an environment variable JSSE_HOME pointing at the directory to which - you installed this distribution. - -* Download and install the Java Management Extensions (JMX) JMX - Instrumentation and Agent Reference Implementation (current version - number is 1.0) from - http://java.sun.com/products/JavaManagement/download.html. - Set an environment variable JMX_HOME pointing at the directory to which - you installed this distribution. - -* Download and install the Ant distribution (subproject jakarta-ant) into - a directory named $JAKARTA_HOME/jakarta-ant. If you have downloaded the - source distribution, you will
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs - New directory
craigmcc01/07/27 15:46:05 jakarta-tomcat-4.0/webapps/tomcat-docs - New directory
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/WEB-INF - New directory
craigmcc01/07/27 15:46:22 jakarta-tomcat-4.0/webapps/tomcat-docs/WEB-INF - New directory
Re: Sources in Binary Distributions
Craig R. McClanahan wrote: [snip] For Tomcat 4, what do folks think of omitting the sources from the binary distribution? This would knock the size of the binary distributions down by around 2 megabytes (which I'm sure people would also appreciate). FWIW, I completely agree. I actually get a little irritated when I download a package for which I specifically selected binary and find source in my directory tree. It needlessly dragged out out my download time and junks up my hard drive. The only reason I ever download binaries is if I am not at all interested in the source for that particular package, and I will download the source myself should I become so. I find it cheeky to sneak it in there. Not that I ever feel that way about Tomcat, of course ... I love you guys and all your fancy-schmancy code =) On a related topic, I was a little surprised to find a source directory in my dist build. Again, today was my very first forray into 4.0, so I have no historical context for the 4.0 build process. I did read somewhere along the way that build dist was to produce exactly the same layout as something else (the binary distro, perhaps, but I can't remember), so maybe that's the reason it is historically included. But as long as you are considering dropping the source from the binaries, which I think is a good idea, my humble suggestion would also be to drop it from the dist target. Again, it was an very extraneous directory for the production system where I sent it, so I ended up manually deleting it. Anyway, just my experience ... - Christopher
RE: Sources in Binary Distributions
-Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] [...] For Tomcat 4, what do folks think of omitting the sources from the binary distribution? This would knock the size of the binary distributions down by around 2 megabytes (which I'm sure people would also appreciate). +1 And also update the build.xml to omitt the sources when compiling with target dist. ..bip
RE: Sources in Binary Distributions
-Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] [...] Well, ant dist ***is*** how binary distributions (for both the nightly builds and releases) are created, so this should not be too much of a surprise :-). Oups, ignore my last post. ..bip
[FAQ] jGuru FAQ Update
jGuru maintains FAQs and Forums on Servlets, JSP, and Tomcat (as well as many other Java topics). Here is an automated update on recent postings to Tomcat-related FAQs. Please direct flames and feedback to [EMAIL PROTECTED] . - Alex SPONSORED BY developerWorks need it? get it. tools, code and tutorials for open-standards based development. Stay informed with dW's weekly email newsletter http://www.jguru.com/misc/register_devworks.jsp?src=notify - Hi. You asked to be notified weekly when certain jGuru.com items get new entries. You can shut email notification off at the FAQ home page(s) or: http://www.jguru.com/guru/notifyprefs.jsp ++ JavaServer Pages (JSP) FAQ: http://www.jguru.com/faq/JSP I am trying to implement a RMI server that has a static variable. Is there anyway the clients can access this static variable on the server side and modiy it. After modification, is the change visible in other clients. http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=463463 Is there a way to access the HttpSession object of a different web application which is running on the same server? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=463461 Why do Frames suck? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=460110 I am writting an application in javabeans and jsp. When I run the application I have some output and the internal servlet error: attempt to clear a buffer that is already been flushed. My application is running under Tomcat 3.2.2. http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=459355 How do I process gb2312-encoded characters within JSP? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=459354 ++ Servlets FAQ: http://www.jguru.com/faq/Servlets How can I display bar codes in my Java program? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=462245 Why do Frames suck? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=460110 When downloading a file to a client, how can I inform the client of the file size, so it can predict how long it will take? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=460092 How do I download several files at the same time? http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=460087
Apache 1.3.20 hangs when warp-connecting to Tomcat4b6
webapp-module-1.0-tc40b6 SunOS clin5 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-60 Apache 1.3.20 gcc 2.95.2 -- My apache works great; I load mod_webapp, and I even get the info page. My standalone Tomcat4 works great, serving WebAppInfo my webapp and its files. But when I add in a directive to WebAppDeploy a webapp in my httpd.conf, apache starts but then hangs forever on a request. No log file entries are made. Also, libhttpd.ep keeps leaving little core files around. That seems bad. I'm using localhost as the ServerName in both httpd.conf and server.xml. Ideas? TIA, -- Eryq, http://www.zeegee.com/eryq WANTED: Schrodinger's Cat. Dead and/or Alive.
RE: Sources in Binary Distributions
-Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] [...] For Tomcat 4, what do folks think of omitting the sources from the binary distribution? This would knock the size of the binary distributions down by around 2 megabytes (which I'm sure people would also appreciate). +1 And also update the build.xml to omitt the sources when compiling with target dist. ++1
cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs/images tomcat.gif
craigmcc01/07/27 18:35:39 Modified:.build.xml webapps build.xml Added: webapps/tomcat-docs build.xml webapps/tomcat-docs/WEB-INF web.xml webapps/tomcat-docs/images tomcat.gif Log: Initial setup of a new webapp for Tomcat 4.0 documentation that is generated (from XML files) rather than being edited directly in HTML. It is based on the site.xsl stylesheet that I checked in to the jakarta-site2 project earlier, so you will need a site.xsl property in your build.properties file that points at it. The basic thinking is that the tomcat-docs webapp will contain all of the user-oriented and developer-oriented documentation relevant to Tomcat 4.0, all generated in a nice consistent style according to the stylesheet. In addition, we can simply take the tomcat-docs.war file, and unpack it into a convenient directory on the web site, and have the online version of the docs instantly available (and always consistent) as well. Over the weekend, I will be porting over some of the existing documentation (in particular the App Developer's Guide, the server.xml configuration stuff, and some of the developer docs) to ensure that this approach scales well, and to offer an example of how to add new categories of documentation to the overall docs webapp. NOTE: When setting this up, I ran into a nasty bug in the style tag in Ant 1.3 -- it treats the style attribute (identifying the filename of the stylesheet to use) as relative, even if you try to specify an absolute pathname. This was nasty, because I wanted to be able to simply point at my checked-out copy of the jakarta-site2 repository. To work around this, the build.xml file for the tomcat-docs webapp does the following (for the moment): - Copies the XML sources to a temporary directory - Copyies the site.xsl file (pointed at by your property) into the temporary directory - Runs the XSLT transformations from the temporary directory to the usual build directory - Deletes the temporary directory A side effect of this workaround is that the generation of the entire tomcat-docs webapp happens every time, even if nothing has changed. Therefore, creation of this webapp is *not* included in the defaults. If you want to generate it, go to the top-level jakarta-tomcat-4.0 source directory and type ant tomcat-docs or ant dist Revision ChangesPath 1.32 +13 -1 jakarta-tomcat-4.0/build.xml Index: build.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/build.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- build.xml 2001/07/27 22:26:03 1.31 +++ build.xml 2001/07/28 01:35:38 1.32 @@ -61,6 +61,18 @@ /target + !-- === SPECIAL: Tomcat Documentation = -- + target name=tomcat-docs depends=deploy-main +!-- The tomcat-docs webapp is not built by default, because the + workaround to an Ant bug causes the XSLT transformations to be + run every time. Run ant tomcat-docs or ant dist to execute + this target -- +ant dir=./webapps target=tomcat-docs/ +copy todir=${tomcat.build}/webapps/tomcat-docs + fileset dir=webapps/build/tomcat-docs/ +/copy + /target + !-- === COMBO: Test All Components = -- target name=test ant dir=./catalina target=test/ @@ -154,7 +166,7 @@ !-- == DIST: Create Archives === -- - target name=dist depends=deploy-main,dist-static,dist-javadoc,dist-source + target name=dist depends=deploy-main,dist-static,dist-javadoc,dist-source,tomcat-docs !-- Comment out until startup timing issues are resolved jar jarfile=${tomcat.dist}/webapps/ROOT.war basedir=${tomcat.build}/webapps/ROOT includes=**/ 1.15 +11 -1 jakarta-tomcat-4.0/webapps/build.xml Index: build.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/build.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- build.xml 2001/05/22 01:59:05 1.14 +++ build.xml 2001/07/28 01:35:39 1.15 @@ -42,6 +42,10 @@ ant dir=${basedir}/manager target=dist/ /target + target name=tomcat-docs +ant dir=${basedir}/tomcat-docs target=dist/ + /target + target name=webdav ant dir=${basedir}/webdav target=dist/ /target @@ -50,7 +54,13 @@ !-- = BUILD: Compile Server Components = -- !-- Update the depends list for each subproject -- target name=build depends=build-prepare,ROOT,examples,manager,webdav/ - +!-- NOTE: tomcat-docs is excluded
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/config ServerXmlReader.java
costin 01/07/27 20:09:33 Modified:src/share/org/apache/tomcat/modules/config ServerXmlReader.java Log: Added back the addModules - there are different files.. Revision ChangesPath 1.15 +1 -1 jakarta-tomcat/src/share/org/apache/tomcat/modules/config/ServerXmlReader.java Index: ServerXmlReader.java === RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/config/ServerXmlReader.java,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- ServerXmlReader.java 2001/07/27 04:00:18 1.14 +++ ServerXmlReader.java 2001/07/28 03:09:32 1.15 @@ -129,7 +129,7 @@ setPropertiesRules( cm, xh ); setTagRules( xh ); addDefaultTags(cm, xh); - //addTagRules( cm, xh ); + addTagRules( cm, xh ); setBackward( xh ); // load the config file(s)
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/server Http10Interceptor.java
costin 01/07/27 20:09:55 Modified:src/share/org/apache/tomcat/modules/server Http10Interceptor.java Log: Small improvement - delayed eveluation. Revision ChangesPath 1.19 +12 -7 jakarta-tomcat/src/share/org/apache/tomcat/modules/server/Http10Interceptor.java Index: Http10Interceptor.java === RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/server/Http10Interceptor.java,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- Http10Interceptor.java2001/07/26 11:14:11 1.18 +++ Http10Interceptor.java2001/07/28 03:09:55 1.19 @@ -242,8 +242,6 @@ return; } -this.remoteAddr().setString(socket.getInetAddress().getHostAddress()); - // for 0.9, we don't have headers! if (! protoMB.equals()) { // all HTTP versions with protocol also have headers @@ -261,14 +259,21 @@ } // override special methods - -public String getRemoteAddr() { -return socket.getInetAddress().getHostAddress(); +public MessageBytes remoteAddr() { + // WARNING: On some linux configurations, this call may get you in + // trubles... Big trubles... + if( remoteAddrMB.isNull() ) { + remoteAddrMB.setString(socket.getInetAddress().getHostAddress()); + } + return remoteAddrMB; } -public String getRemoteHost() { - return socket.getInetAddress().getHostName(); +public MessageBytes remoteHost() { + if( remoteHostMB.isNull() ) { + remoteHostMB.setString( socket.getInetAddress().getHostName() ); + } + return remoteHostMB; } public String getLocalHost() {
Non-graceful shutdown a problem in 3.2.3?
I am running Tomcat 3.2.3 on NT/IIS with the Jikes compiler, and noticed if the server is reset (i.e. power glitch) without a normal shutdown, Tomcat comes back up non-operational. The symptoms are that the JSPs can't be accessed until the class files from the previous run are deleted from the work directory. The log I get is: 2001-07-26 11:33:06 - Ctx( /admin ): JasperException: R( /admin + /contextAdmin/contextAdmin.jsp + null) Unable to compile class for JSP The beginning of the root cause trace is: java.lang.ArrayIndexOutOfBoundsException at org.apache.jasper.compiler.ClassName.processClassData(ClassName.java:89) at org.apache.jasper.compiler.ClassName.getClassName(ClassName.java:191) at org.apache.jasper.compiler.JspCompiler.getRealClassName(JspCompiler.java:136 ) I was concerned it might be something to do with Jikes, but it works fine if I manually recompile the .java source that Tomcat creates just before the above logs. I can fix this with a startup script that deletes the class files, but I'm hoping there's a proper fix somewhere. I couldn't find any discussion on this problem in the archives or the web, except for the possibly related discussion at: http://www.javaclue.org/tomcat/patch32b6/letspatch.html#step5 I was surprised to see that this patch (against 3.2.1) hadn't been applied to 3.2.3, but it didn't work for me anyway. Does any have any ideas? ...Ken. --- Ken Grigg AmikaNow! Corporation mailto:[EMAIL PROTECTED]
Re: Funny thought about version numbering...
I highly dout your windows machine crashes every 4 hours on average. - Original Message - From: Deacon Marcus [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, July 28, 2001 3:29 AM Subject: Funny thought about version numbering... Hi, I'm using (very ligthly) modified Tomcat 4.0 b5 for almost as long as it was out (b3 before, but I'm not sure), and found it rock-stable so far, not a single failure on neither development or deployment servers. While there're much features I would like Tomcat to have, what's already in is perfectly stable for me. So why have 6th beta in a row, instead of declaring b5 final and naming b6 4.1? That would definitely encourage more people to use it instead of out-dated 3.2/3.3. Hell, I have now Tomcat _beta_ running for about a month now (on RedHat 7.1, if you want to know), while my Windows _final_ with every possible service pack and security patches crashes about every 4 hours on average. I love you guys :) If such programmers would work in M$ since its begging we would had (stable) Windows XP in 1985-1990. Greetings, deacon Marcus
RE: Funny thought about version numbering...
Hi, -Original Message- From: Joshua Anderson [mailto:[EMAIL PROTECTED]] Sent: Friday, July 27, 2001 11:51 PM To: [EMAIL PROTECTED] Subject: Re: Funny thought about version numbering... I highly dout your windows machine crashes every 4 hours on average. Wanna bet ? Before you say yes, let me inform you it's a two-years old installation of 98 SE upgraded from 98. To be more exact, it doesn't always crash, but on average after 4 hours it either crash or is almost dead from memory / resources leaks. Greetings, deacon Marcus - Original Message - From: Deacon Marcus [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, July 28, 2001 3:29 AM Subject: Funny thought about version numbering... Hi, I'm using (very ligthly) modified Tomcat 4.0 b5 for almost as long as it was out (b3 before, but I'm not sure), and found it rock-stable so far, not a single failure on neither development or deployment servers. While there're much features I would like Tomcat to have, what's already in is perfectly stable for me. So why have 6th beta in a row, instead of declaring b5 final and naming b6 4.1? That would definitely encourage more people to use it instead of out-dated 3.2/3.3. Hell, I have now Tomcat _beta_ running for about a month now (on RedHat 7.1, if you want to know), while my Windows _final_ with every possible service pack and security patches crashes about every 4 hours on average. I love you guys :) If such programmers would work in M$ since its begging we would had (stable) Windows XP in 1985-1990. Greetings, deacon Marcus
Re: Funny thought about version numbering...
On Sat, 28 Jul 2001, Deacon Marcus wrote: Hi, I'm using (very ligthly) modified Tomcat 4.0 b5 for almost as long as it was out (b3 before, but I'm not sure), and found it rock-stable so far, not a single failure on neither development or deployment servers. While there're much features I would like Tomcat to have, what's already in is perfectly stable for me. So why have 6th beta in a row, instead of declaring b5 final and naming b6 4.1? That would definitely encourage more people to use it instead of out-dated 3.2/3.3. Hell, I have now Tomcat _beta_ running for about a month now (on RedHat 7.1, if you want to know), while my Windows _final_ with every possible service pack and security patches crashes about every 4 hours on average. I love you guys :) If such programmers would work in M$ since its begging we would had (stable) Windows XP in 1985-1990. The main reason for not going final, IMHO, has been the fact that the underlying specifications (Servlet 2.3, JSP 1.2) are not final. Indeed, I'm going to be spending time this weekend implementing a fairly recent clarification to the servlet spec's handling of single sign on. It doesn't make much sense to create a final release that claims conformance to specifications that are not themselves final yet. We're down to weeks now ... I personally consider Tomcat 4.0 to be in maintenance mode (with a need to improve the documentation that there are already volunteers working on, and continued work on the web connectors which are vital to many users). We'll open a way to begin development for 4.1 shortly. Greetings, deacon Marcus Craig PS: I hear you about Linux :-). A while back, I had the pleasure of running an uptime command on a server (running Apache+JServ+other stuff) that had been up for over a *year* with no reboots. We finally had to take it down because the ISP was remodelling their facility. And RedHat Linux 7.1 is my personal primary development environment for both Tomcat and Struts. PPS: What modifications to Tomcat 4.0-beta-5 did you find necessary? Anything that would be useful to the general community?