You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Remy Maucherat <re...@apache.org> on 2002/06/28 21:10:47 UTC
[4.1.6] Milestone available for testing
Hightlights in this test release include:
- fix for a memory leak in the request dispatcher
- many fixes and refactorings in Jasper 2
- admin webapp improvements
- other misc fixes
See the release notes for the list of changes.
Downloads:
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.6/
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 2 Jul 2002, Chad Johnson wrote:
> Date: Tue, 2 Jul 2002 10:53:32 -0500
> From: Chad Johnson <ch...@netnet.net>
> Reply-To: Tomcat Developers List <to...@jakarta.apache.org>
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: [4.1.6] Milestone available for testing
>
> Hey,
> I may have missed something obvious, but if I didn't, are there plans to
> add context reset/stop/start to the new administration webapp?
>
Those facilities are all available in the Manager webapp. Because manager
is accessed via HTTP, it is very easy to integrate these capabilities into
your development environment -- for example, 4.1.x includes custom Ant
tasks that install/reload/remove apps directly from your build.xml file,
and the deploytool that ships with the Java Web Services Developer Pack
(JWSDP) <http://java.sun.com/webservices/> uses them behind the scenes to
provide a GUI experience people packaging and deploying web applications.
> -Chad Johnson
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by Chad Johnson <ch...@netnet.net>.
Hey,
I may have missed something obvious, but if I didn't, are there plans to
add context reset/stop/start to the new administration webapp?
-Chad Johnson
----- Original Message -----
From: "Remy Maucherat" <re...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Cc: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Friday, June 28, 2002 2:10 PM
Subject: [4.1.6] Milestone available for testing
> Hightlights in this test release include:
> - fix for a memory leak in the request dispatcher
> - many fixes and refactorings in Jasper 2
> - admin webapp improvements
> - other misc fixes
>
> See the release notes for the list of changes.
>
> Downloads:
> http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.6/
>
> Remy
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [4.1.6] Milestone available for testing
Posted by Mladen Turk <mt...@mappingsoft.com>.
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: 1. srpanj 2002 9:45
>
> The easiest is probably to update tools.jar in common/lib
That was the killer, thx.
MT.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by Remy Maucherat <re...@apache.org>.
Mladen Turk wrote:
>
>>>Doesn't work :(
>>>
>>>Direct conf and dir replacement for working 4.1.5.
>>>JSDK 1.4.0_01/WIN XP
>>>Standalone.
>>>
>>>http://localhost:8080/examples/jsp/dates/date.jsp
>>
>>The same configuration (XP Home / JDK 1.4.0_01) works very
>>well for me.
>>
>>Remy
>>
>
>
> If started through shortcut (well, I left the one from 4.15
> installation) then it doesn't work, but if started clicking on the
> startup.bat directly then it works.
When you install Tomcat, it copies javac to the Tomcat common/lib
(otherwise, there could be problems with path lengths in the shortcuts).
So if you install with JDK 1.3, and then swicth later to JDK 1.4, the
rt.lib from JDK 1.4 will be used by the javac from JDK 1.3, and that
will cause an error.
The easiest is probably to update tools.jar in common/lib, or to avoid
switching JDKs.
The error massage I get is:
Generated servlet error:
[javac] Compiling 1 source file
C:\Program Files\Apache Group\Tomcat
4.1\work\Standalone\localhost\examples\jsp\dates\date$jsp.java:11:
cannot access java.lang.Object
bad class file: C:\java\j2sdk1.4.0_01\jre\lib\rt.jar(java/lang/Object.class)
class file has wrong version 48.0, should be 47.0
Please remove or make sure it appears in the correct subdirectory of the
classpath.
private static java.util.Vector _jspx_includes;
^
1 error
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [4.1.6] Milestone available for testing
Posted by Mladen Turk <mt...@mappingsoft.com>.
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: 1. srpanj 2002 8:44
> To: Tomcat Users List
> Subject: Re: [4.1.6] Milestone available for testing
>
>
> Mladen Turk wrote:
> > Doesn't work :(
> >
> > Direct conf and dir replacement for working 4.1.5.
> > JSDK 1.4.0_01/WIN XP
> > Standalone.
> >
> > http://localhost:8080/examples/jsp/dates/date.jsp
>
> The same configuration (XP Home / JDK 1.4.0_01) works very
> well for me.
>
> Remy
>
If started through shortcut (well, I left the one from 4.15
installation) then it doesn't work, but if started clicking on the
startup.bat directly then it works.
MT.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by Remy Maucherat <re...@apache.org>.
Mladen Turk wrote:
> Doesn't work :(
>
> Direct conf and dir replacement for working 4.1.5.
> JSDK 1.4.0_01/WIN XP
> Standalone.
>
> http://localhost:8080/examples/jsp/dates/date.jsp
The same configuration (XP Home / JDK 1.4.0_01) works very well for me.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [4.1.6] Milestone available for testing
Posted by Mladen Turk <mt...@mappingsoft.com>.
Doesn't work :(
Direct conf and dir replacement for working 4.1.5.
JSDK 1.4.0_01/WIN XP
Standalone.
http://localhost:8080/examples/jsp/dates/date.jsp
HTTP Status 500 -
------------------------------------------------------------------------
--------
type Exception report
message
description The server encountered an internal error () that prevented
it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.ja
va:481)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:182)
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(Applica
tionFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator
Base.java:471)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:235
0)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:40
5)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:380)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:50
8)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:518)
at java.lang.Thread.run(Thread.java:536)
root cause
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Compiling 1 source file
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHa
ndler.java:120)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.ja
va:293)
at
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:311)
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:322)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.ja
va:478)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:182)
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(Applica
tionFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator
Base.java:471)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:235
0)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:40
5)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:380)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:50
8)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:518)
at java.lang.Thread.run(Thread.java:536)
------------------------------------------------------------------------
--------
Apache Tomcat/4.1.6
> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: 28. lipanj 2002 21:11
> To: Tomcat Developers List
> Cc: Tomcat Users List
> Subject: [4.1.6] Milestone available for testing
>
>
> Hightlights in this test release include:
> - fix for a memory leak in the request dispatcher
> - many fixes and refactorings in Jasper 2
> - admin webapp improvements
> - other misc fixes
>
> See the release notes for the list of changes.
>
> Downloads:
> http://jakarta.apache.org/builds/jakarta-> tomcat-4.0/test/v4.1.6/
>
> Remy
>
>
> --
> To unsubscribe, e-mail:
> <mailto:tomcat-user-> unsubscribe@jakarta.apache.org>
> For
> additional commands,
> e-mail: <ma...@jakarta.apache.org>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by Peter Lin <tc...@yahoo.com>.
> Did you set the "development" flag to false while
> testing ? I think
> you're supposed to use that in production systems
> now (I suppose we need
> a doc page on Jasper 2, as there are quite a few new
> configuration
> parameters which are actually useful now).
>
Nope, I didn't set the flag to false. I finally gave
up on JProbe and decided it simply won't work with
Jasper2. It looks like when JProbe launches a new
shell it wipes out the environment settings, since I
have java_home, java, classpath and path all set to
the location of my jdk1.3.1.
I'm running benchmarks with OptimizeIt now on my home
system. Even though my goal is to profile the
performance of JSTL, it does provide useful comparison
between tomcat 4.0.3 and 4.1.6.
I do notice GC intervals are longer with tag pooling
and no where near jasper1. As well, it gives the VM
more time to increase the heap size gradually compared
to jasper1. Jasper1 compiled tag pages under 16
concurrent connections tended to spike the heap
setting dramatically, leading to unusually high
variance/deviation. In some cases the variance in
response time in JMeter was greater than the mean.
peter
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by Remy Maucherat <re...@apache.org>.
Peter Lin wrote:
> I just ran some benchmarks with 4.1.6 and noticed a
> couple of things.
>
> 1. 4.1.6 is showing less of an impact once the
> connector reaches the max processors. With 4.0.3, I
> was able to trigger a out of memory error by letting
> JMeter continue for a couple minutes after tomcat
> reaches the max processors and is denying connections.
> I discovered this by accident when I was running
> benchmarks with 120 con current connection hitting
> pages with lots of JSTL tags. the max processor was
> set to 75.
>
> 2. performance appears to be more consistent memory
> and cpu wise. Under moderate and heavy load, the cpu
> usage varies more with 4.0.3 and it takes longer for
> 4.0.3 to return to normal memory usage. This was done
> with just task monitor and not optimizeIt or JProbe
> since I can't get JProbe to work correctly with
> jasper2.
>
> 3. tag pooling does show 5-10% improvement over
> jasper2 w/o tag pooling.
I haven't profiled Jasper 2 for a long time, so I'm not sure how
complete the optimizations are (it should be quite good at this point
though, since Costin probably did).
I'd say tag pooling may help more on pages which use lots of simple tags
like some i18n tag. It still obviously helps reduce GC, which never hurts.
Did you set the "development" flag to false while testing ? I think
you're supposed to use that in production systems now (I suppose we need
a doc page on Jasper 2, as there are quite a few new configuration
parameters which are actually useful now).
> Once I figure out how to get JProbe to work with
> jasper2, i will run more tests.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.6] Milestone available for testing
Posted by Peter Lin <tc...@yahoo.com>.
I just ran some benchmarks with 4.1.6 and noticed a
couple of things.
1. 4.1.6 is showing less of an impact once the
connector reaches the max processors. With 4.0.3, I
was able to trigger a out of memory error by letting
JMeter continue for a couple minutes after tomcat
reaches the max processors and is denying connections.
I discovered this by accident when I was running
benchmarks with 120 con current connection hitting
pages with lots of JSTL tags. the max processor was
set to 75.
2. performance appears to be more consistent memory
and cpu wise. Under moderate and heavy load, the cpu
usage varies more with 4.0.3 and it takes longer for
4.0.3 to return to normal memory usage. This was done
with just task monitor and not optimizeIt or JProbe
since I can't get JProbe to work correctly with
jasper2.
3. tag pooling does show 5-10% improvement over
jasper2 w/o tag pooling.
Once I figure out how to get JProbe to work with
jasper2, i will run more tests.
peter
--- Remy Maucherat <re...@apache.org> wrote:
> Hightlights in this test release include:
> - fix for a memory leak in the request dispatcher
> - many fixes and refactorings in Jasper 2
> - admin webapp improvements
> - other misc fixes
>
> See the release notes for the list of changes.
>
> Downloads:
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.6/
>
> Remy
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>