[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-2042) Investigate performance issue related to use of @SecurityDomain on EJB
[
https://jira.jboss.org/browse/EJBTHREE-2042?page=com.atlassian.jira.plugi...
]
Remi Nodet commented on EJBTHREE-2042:
--------------------------------------
Did not finish my comment ..
Also noticeable:
12.3% - 19,653 ms java.lang.StringBuilder.append
Called from 2 places:
2.3% - 3,650 ms org.jboss.ejb.plugins.security.SecurityActions$10.run
2.2% - 3,463 ms org.jboss.ejb.plugins.security.SecurityActions$11.run
And
7.0% - 11,144 ms java.lang.StringBuffer.append(java.lang.Object)
Called from : org.jboss.ejb.plugins.security.SecurityActions$xx.run
All in all, almost 40% of the "Runnable" time is spent the above security
related methods. That corresponds pretty much to the experienced performance decrease on
our production servers.
Investigate performance issue related to use of @SecurityDomain on
EJB
----------------------------------------------------------------------
Key: EJBTHREE-2042
URL: https://jira.jboss.org/browse/EJBTHREE-2042
Project: EJB 3.0
Issue Type: Task
Reporter: jaikiran pai
Assignee: jaikiran pai
A user has reported that the use of @SecurityDomain shows a relatively poor performance
(even when a @PermitAll) is applied to the bean. See the referenced forum thread for
details.
Although, it can't be guaranteed that the performance of a bean method invocation
with a @SecurityDomain will be same as that without a @SecurityDomain, the difference in
the timings as reported in that thread looks a bit too high. This JIRA is to track to
investigate the issue and see if there's any genuine performance bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira