[
https://issues.apache.org/jira/browse/MYFACES-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019409#comment-13019409
]
Bernd Bohmann commented on MYFACES-2823:
----------------------------------------
The issue is solved in Tomcat 6.0.30
see: https://issues.apache.org/bugzilla/show_bug.cgi?id=49613
> Request attribute names are not cached which causes performance degredation
> ---------------------------------------------------------------------------
>
> Key: MYFACES-2823
> URL: https://issues.apache.org/jira/browse/MYFACES-2823
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.2.9
> Environment: Tomcat 6.0.20 (with an SSL connector)
> MyFaces 1.2.9
> RichFaces 3.3.2
> Java 1.6.0_15
> Reporter: Sampo Savolainen
> Attachments: stack.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When rendering a simple request, MyFaces ends up calling
> Request.getAttributeNames() 1000+ times. This causes performance degredation
> in cases when it is not trivial for the container to produce the names. This
> is the case for example with Tomcat when there is an SSL connector: reading
> the attribute names requires tomcat to check if there are peer certificates.
> I will attach a screenshot from a profiling session where a substantial
> portion of the server processing went into
> org.apache.myfaces.context.servlet.RequestMap.getAttributeNames(). This
> screenshot shows a backtrace from one JSSE accessor called by
> getAttributeNames() up to the faces components where the calls are initiated
> from.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
