You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Serge Knystautas <se...@lokitech.com> on 2000/07/15 20:33:26 UTC
Work directories getting cleaned
Is there any reason the work directories are preserved across server
restarts? We're using Tomcat 3.1 here, and after a month or so of
development by 2 web developers, the work directory is 126 megs in 6,056
files. Seems like it would be easy to patch that when the work
directories are created, everything in there already is deleted. (I can
find and make a patch if someone tells me which branch I should work
on... is 3.2 branched yet?)
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
Re: Consistent exception on GET
Posted by Alex Chaffee <gu...@edamame.stinky.com>.
No it shouldn't have. That file didn't change. Ant can't track
dependencies (( MimeHeaderField.java depends on DateTool.java) that it
hasn't been told about explicitly. This is why you should always do a
build clean after a large update. Build "unclean" is just for use
during a quick change-compile-run-repeat cycle.
- Alex "Best Practices" Chaffee
On Sun, Jul 16, 2000 at 04:11:47PM -0400, Brill Pappin wrote:
> Yes... after going through the tomcat code, I discovered that I shouldn't be
> getting that exception at all (as the code was all there) so I tried a build
> clean and as you said... there it went :)
>
> I guess my problem was with ant, as it should have detected the changed
> file...
>
> Thanks for your help,
> - Brill Pappin
>
> > -----Original Message-----
> > From: Alex Chaffee [mailto:guru@edamame.stinky.com]
> > Sent: July 16, 2000 4:36 AM
> > To: tomcat-dev@jakarta.apache.org
> > Subject: Re: Consistent exception on GET
> >
> >
> > Do a "build clean" to get rid of this one.
> >
> > (I changed the type of the rfc1123format from "SimpleDateFormat" to
> > "DateFormat" so the old class was compiled to look for the old type,
> > which isn't there any more.)
> >
> > - Alex
> >
> > > java.lang.NoSuchFieldError: rfc1123Format
> > > at
> > >
> > org.apache.tomcat.util.MimeHeaderField.formatDate(MimeHeaderField.
> > java:330)
> > > at
> >
> > --
> > Alex Chaffee mailto:alex@jguru.com
> > jGuru - Java News and FAQs http://www.jguru.com/alex/
> > Creator of Gamelan http://www.gamelan.com/
> > Founder of Purple Technology http://www.purpletech.com/
> > Curator of Stinky Art Collective http://www.stinky.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
--
Alex Chaffee mailto:alex@jguru.com
jGuru - Java News and FAQs http://www.jguru.com/alex/
Creator of Gamelan http://www.gamelan.com/
Founder of Purple Technology http://www.purpletech.com/
Curator of Stinky Art Collective http://www.stinky.com/
RE: Consistent exception on GET
Posted by Brill Pappin <jo...@jmonkey.com>.
Yes... after going through the tomcat code, I discovered that I shouldn't be
getting that exception at all (as the code was all there) so I tried a build
clean and as you said... there it went :)
I guess my problem was with ant, as it should have detected the changed
file...
Thanks for your help,
- Brill Pappin
> -----Original Message-----
> From: Alex Chaffee [mailto:guru@edamame.stinky.com]
> Sent: July 16, 2000 4:36 AM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: Consistent exception on GET
>
>
> Do a "build clean" to get rid of this one.
>
> (I changed the type of the rfc1123format from "SimpleDateFormat" to
> "DateFormat" so the old class was compiled to look for the old type,
> which isn't there any more.)
>
> - Alex
>
> > java.lang.NoSuchFieldError: rfc1123Format
> > at
> >
> org.apache.tomcat.util.MimeHeaderField.formatDate(MimeHeaderField.
> java:330)
> > at
>
> --
> Alex Chaffee mailto:alex@jguru.com
> jGuru - Java News and FAQs http://www.jguru.com/alex/
> Creator of Gamelan http://www.gamelan.com/
> Founder of Purple Technology http://www.purpletech.com/
> Curator of Stinky Art Collective http://www.stinky.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: Consistent exception on GET
Posted by Alex Chaffee <gu...@edamame.stinky.com>.
Do a "build clean" to get rid of this one.
(I changed the type of the rfc1123format from "SimpleDateFormat" to
"DateFormat" so the old class was compiled to look for the old type,
which isn't there any more.)
- Alex
> java.lang.NoSuchFieldError: rfc1123Format
> at
> org.apache.tomcat.util.MimeHeaderField.formatDate(MimeHeaderField.java:330)
> at
--
Alex Chaffee mailto:alex@jguru.com
jGuru - Java News and FAQs http://www.jguru.com/alex/
Creator of Gamelan http://www.gamelan.com/
Founder of Purple Technology http://www.purpletech.com/
Curator of Stinky Art Collective http://www.stinky.com/
Consistent exception on GET
Posted by Brill Pappin <jo...@jmonkey.com>.
I'm not sure what has changed in Tomcat over the last few months, but I am
now getting an exception when I first try a get from the HTTP service.
Its happening in release 3.1 and in the most recent CVS source (I checked it
out last night and tried it).
I'm running it from the console in Window 2000 and JDK 1.3 (and yes, I have
checked for classpath conflicts, etc.).
I suspect is a local problem as I'm sure it wouldn't be there at all if
everyone else was having the same trouble... So... I suspect I must have an
out of date library or extension... anyone have any idea which one?
The exception follows:
Tomcat: Loading config file D:\working\dist\tomcat\conf\server.xml
2000-07-16 11:34:11 - ContextManager: Adding context Ctx(/examples)
2000-07-16 11:34:11 - ContextManager: Adding context Ctx(/admin)
2000-07-16 11:34:11 - Tomcat: Loaded config file
D:\working\dist\tomcat\conf\server.xml
Tomcat started. Check console for error and log messages.
2000-07-16 11:34:11 - ContextManager: Adding context Ctx()
2000-07-16 11:34:11 - ContextManager: Adding context Ctx(/test)
2000-07-16 11:34:12 - Tomcat: Tomcat Web Server 3.3 dev
2000-07-16 11:34:12 - PoolTcpConnector: Starting HttpConnectionHandler on
8080
2000-07-16 11:34:12 - PoolTcpConnector: Starting Ajp12ConnectionHandler on
8007
2000-07-16 11:34:16 - Context: Status code:302 request:R( + / + /)
msg:/index.html
2000-07-16 11:34:16 - Context: Exception in R( + / + /index.html) -
java.lang.NoSuchFieldError: rfc1123Format
at
org.apache.tomcat.util.MimeHeaderField.formatDate(MimeHeaderField.java:330)
at
org.apache.tomcat.util.MimeHeaderField.getValue(MimeHeaderField.java:261)
at
org.apache.tomcat.service.http.HttpResponseAdapter.endHeaders(HttpResponseAd
apter.java:120)
at
org.apache.tomcat.core.BufferedServletOutputStream.sendHeaders(BufferedServl
etOutputStream.java:126)
at
org.apache.tomcat.core.BufferedServletOutputStream.reallyFlush(BufferedServl
etOutputStream.java:235)
at
org.apache.tomcat.core.BufferedServletOutputStream.flush(BufferedServletOutp
utStream.java:229)
at org.apache.tomcat.core.ResponseImpl.finish(ResponseImpl.java:197)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:668)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:195)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:393)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Unknown Source)
- Brill Pappin
Re: Work directories getting cleaned
Posted by Costin Manolache <cm...@yahoo.com>.
Serge Knystautas wrote:
> Costin Manolache wrote:
> > I think the right solution is to fix jasper, so it removes old files.
>
> I got it now about keeping work directories, and I agree the right
> solution is probably to fix jasper. Who is actively working on jasper
> right now? It feels like Jasper does not have features that other open
> source JSP parsers had/have (like GNU JSP back in the day). Several
> features I'd like to have in jasper would include:
> - dependency checking! if you inline include another JSP and then
> change the included one, the jsp that did the including should recompile
> as well. (this can be optional)
> - control over how directories (with source code) are created (right now
> some directories are created, but then never used). this should be a
> controllable parameter
> - whether the source code is left (another parameter)
> - controlling whether to check JSP file timestamps (optionally prevents
> recompilation... good for production environments)
Check the JspInterceptor, has some of this. For dependency - it just uses
the
servlet class loader, it does use the directories, etc.
It still needs work. ( did I mentioned it's have a far smaller overhead than
JspServlet
and after the compile the jsp behave just like any exact-mapped servlet,
with
no intermediate servlet ?)
Costin
>
> Seems like a reasonable list... I don't have much time because of JAMES,
> but how can I help?
>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Work directories getting cleaned
Posted by Serge Knystautas <se...@lokitech.com>.
Costin Manolache wrote:
> I think the right solution is to fix jasper, so it removes old files.
I got it now about keeping work directories, and I agree the right
solution is probably to fix jasper. Who is actively working on jasper
right now? It feels like Jasper does not have features that other open
source JSP parsers had/have (like GNU JSP back in the day). Several
features I'd like to have in jasper would include:
- dependency checking! if you inline include another JSP and then
change the included one, the jsp that did the including should recompile
as well. (this can be optional)
- control over how directories (with source code) are created (right now
some directories are created, but then never used). this should be a
controllable parameter
- whether the source code is left (another parameter)
- controlling whether to check JSP file timestamps (optionally prevents
recompilation... good for production environments)
Seems like a reasonable list... I don't have much time because of JAMES,
but how can I help?
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
Re: Work directories getting cleaned
Posted by Costin Manolache <cm...@yahoo.com>.
> Is there any reason the work directories are preserved across server
> restarts?
Yes, few. We want to avoid recompiling the JSPs at server restart.
And in "secure" mode the work dir is the only place where a servlet
can write. File access is an important feature - caching, etc.
There are quite a few servlets that need a file system ( jCVS is one
good example ). Yes, it's not portable - but I don't think there is good
a replacement for file system.
> We're using Tomcat 3.1 here, and after a month or so of
> development by 2 web developers, the work directory is 126 megs in 6,056
> files. Seems like it would be easy to patch that when the work
> directories are created, everything in there already is deleted. (I can
> find and make a patch if someone tells me which branch I should work
> on... is 3.2 branched yet?)
Just create an interceptor, add it to the config file. Or make
a configurable option in WorkDirInterceptor.
I think the right solution is to fix jasper, so it removes old files.
Costin