[jboss-jira] [JBoss JIRA] (SECURITY-864) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration

[Philippe Marschall (JIRA)]

    [ https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440352#comment-13440352 ] 

Philippe Marschall commented on SECURITY-864:
---------------------------------------------

[~benze] {quote}I looked at your code in GitHub. Won't the exceptions thrown by the EmptyPolicy still cause the same slowdowns? Or is the exception thrown by WF simply limited to the fact that no policyRegistration is found (even though it is never actually used)?{quote}

Yes that's what we observed, the policyRegistration is never actually used. We profiled the application afterwards and found no more exceptions raised during normal EJB processing. It was to be noted though that we use EJB remoting and not servlets so JACC can never really be called.

However we now also provide a {{JBossPolicyRegistrationObjectFactory}} that registers a {{JBossPolicyRegistration}}.

> NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SECURITY-864
>                 URL: https://issues.jboss.org/browse/SECURITY-864
>             Project: PicketBox 
>          Issue Type: Bug
>          Components: PicketBox
>            Reporter: Chao Wang
>            Assignee: Stefan Guilhen
>
> "NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level: 
> {noformat}
>             <logger category="org.jboss.as.security">
>                 <level name="TRACE"/>
>             </logger>
>             <logger category="org.jboss.security">
>                 <level name="TRACE"/>
>             </logger>
> {noformat}
> See detailed description in community discussion [#907134|https://developer.jboss.org/message/907134]
> I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException"



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)