-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
On 2/17/2010 3:59 AM, Michael Heinen wrote:
> I patched org.apache.jasper.compiler.Generator and removed the
> AnnotationHelper.
> The compiled jsps did not contain these calls anymore but this did
> not have any noticeable effect on performa
r real app but
this seems to be not so trivial.
Michael
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Dienstag, 16. Februar 2010 22:54
To: Tomcat Users List
Subject: Re: performance problems with Tomcat 6 and JSF 1.2
On 16/02/2010 21:39, Christopher Schultz wrote:
> M
On 16/02/2010 21:39, Christopher Schultz wrote:
> Mark Thomas is a frequent contributor to this list and, if he's
> got time and you're willing to help, he's quite likely to help
> investigate and maybe work on a solution.
It is on my radar but I haven't had time to look at it yet. There is at
lea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micheal,
On 2/16/2010 7:45 AM, Michael Heinen wrote:
> I created bug 48750: https://issues.apache.org/bugzilla/show_bug.cgi?id=48750
>
> The source jsp and the compiled jsps are attached at this bug.
You might also want to show what JSF 1.1 gets you
class for each tag.
Michael
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Samstag, 13. Februar 2010 16:28
To: Tomcat Users List
Subject: Re: performance problems with Tomcat 6 and JSF 1.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
On 2/12/2010 11:11 AM, Michael Heinen wrote:
> I noticed serious performance problems with JSF 1.2 and Tomcat which seems to
> be caused by Tomcat.
> One major performace problem is bug
> https://issues.apache.org/bugzilla/show_bug.cgi?id=
Hi Richard
I've printed that off for future reference. Thank you for your prompt response.
Regards
Roger
>
> Roger,
>
> A thread dump/stack trace of all the threads in the Tomcat
> JVM is one way to
> see whats happening. It will show what is happening in detail
> - and may even
> highlight
Roger,
A thread dump/stack trace of all the threads in the Tomcat JVM is one way to
see whats happening. It will show what is happening in detail - and may even
highlight some problems. It does take a bit of study to understand what you
are seeing. Here is an article I use that covers both Windows
