[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-2042) Investigate performance issue related to use of @SecurityDomain on EJB

[Husgaard (JIRA)]

    [ https://jira.jboss.org/browse/EJBTHREE-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557112#action_12557112 ] 

Husgaard commented on EJBTHREE-2042:
------------------------------------

I just discussed this with Rémi Nodet, and this application has a lot of calls from session facade beans to EJB2 entity beans. Here the PreSecurityInterceptor is in the interceptor chain, and I see lots of possible optimization here.

In particular some low-hanging fruit (trivially easy optimization): In PreSecurityInterceptor.java we have the following lines in different places:

log.trace("SecurityIdentity="+SecurityActions.trace(si));
log.trace("Going to the SecurityInterceptor with SC="+SecurityActions.trace(currentSC));
log.trace("establishSecurityIdentity:SecCtx="+SecurityActions.trace(newSC));

The calls to the SecurityActions.trace() involve an expensive AccessController.doPrivileged() to build the string returned, even when logging is not at trace level.

> 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