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

[Husgaard (JIRA)]

     [ https://issues.jboss.org/browse/EJBTHREE-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Husgaard updated EJBTHREE-2042:
-------------------------------

    Attachment: patch-trace.diff


I uploaded a simple patch to avoid CPU-expensive calls not needed unless logging at TRACE level.

Depending on the real-world scenarios in our application, this cuts off 4-22% of processing time.

> Investigate performance issue related to use of @SecurityDomain on EJB
> ----------------------------------------------------------------------
>
>                 Key: EJBTHREE-2042
>                 URL: https://issues.jboss.org/browse/EJBTHREE-2042
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>         Attachments: hotspots.tar.gz, patch-trace.diff, 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira