[
https://jira.jboss.org/browse/EJBTHREE-2042?page=com.atlassian.jira.plugi...
]
Remi Nodet commented on EJBTHREE-2042:
--------------------------------------
It is a little difficult to provide you with the bean code since this is gotten from a
large application with a lot of stateless session beans and entity beans.
However it looks to me like every single call to any method (remote, local, home or
business interface) on a session bean or entity bean (I am using EJB 2.1) results in calls
to doPrivileged(). Since we have a lot of calls to local entity beans generated for each
call to our remote stateless session beans (facade pattern) the doPrivileged() method
seems to turn out to be a nasty bottleneck.
I'll try to make a simple example with only a session bean and an entity bean to get a
simpler scenario for the profiling
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
Attachments: ProfilingHotSpots.zip
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