Large allocations in EJBContext#isCallerInRole

[Philippe Marschall]

We have a use case where we need to know the roles a user has. We currently do this by iterating over all roles and calling EJBContext#isCallerInRole for each. Unfortunately this results in a lot of allocations. As a short term measure we will migrate to org.wildfly.security.auth.server.SecurityDomain but other use cases or users may benefit from an optimised implementation. Here's a screenshot from a Java Flight Recorder allocation profile, it completely dominates our allocations.

[Darran Lofthouse]

Could you get this into a WildFly bug report please, we are about to spend some time looking at the current bug reports and this does sound like a candidate we should work on.

[Philippe Marschall]

dlofthouse  wrote:

Could you get this into a WildFly bug report please, we are about to spend some time looking at the current bug reports and this does sound like a candidate we should work on.

There you go [WFLY-12836] Large allocations in EJBContextImpl#isCallerInRole - JBoss Issue Tracker