Exception caught: javax.naming.NameNotFoundException: policyRegistration

[valsaraj007]

DEBUG [org.jboss.security] (default task-1) PBOX000293: Exception caught: javax.naming.NameNotFoundException: policyRegistration -- service jboss.naming.context.java.policyRegistration

  at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)

  at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)

  at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)

  at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_07]

  at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_07]

  at org.jboss.security.plugins.javaee.EJBAuthorizationHelper.getPolicyRegistrationFromJNDI(EJBAuthorizationHelper.java:353) [picketbox-4.0.21.Final.jar:4.0.21.Final]

  at org.jboss.security.plugins.javaee.EJBAuthorizationHelper.authorize(EJBAuthorizationHelper.java:303) [picketbox-4.0.21.Final.jar:4.0.21.Final]

  at org.jboss.as.security.service.SimpleSecurityManager.authorize(SimpleSecurityManager.java:303) [wildfly-security-8.2.0.Final.jar:8.2.0.Final]

  at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:133) [wildfly-ejb3-8.2.0.Final.jar:8.2.0.Final]

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-8.2.0.Final.jar:8.2.0.Final]

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-8.2.0.Final.jar:8.2.0.Final]

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-8.2.0.Final.jar:8.2.0.Final]

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-8.2.0.Final.jar:8.2.0.Final]

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326)

  at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448)

  at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326)

  at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

  at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185)

  at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182)

  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)

  at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

I am seeing this on startup. What may be the reason?

[jaysensharma]

Refer to :  https://developer.jboss.org/message/914518#914518

This is harmless DEBUG message. Which comes from the code picketbox/EJBAuthorizationHelper.java at 4.0.21.Final · picketbox/picketbox · GitHub

1. protected String POLICY_REGISTRATION_JNDI = "java:/policyRegistration"; 

WildFly 8.2 uses picketbox 4.0.21 so in the above code you will find that   it tries to lookup above JNDI name which is not registered hence the lookup fails Whenever the "getPolicyRegistrationFromJNDI()" is invoked.    As this is just a DEBUG message hence it should not cause any harm to the functionality of your application.  This DEBUG message is there from past many picketbox versions.   so you should avoid it.

[valsaraj007]

Thanks Jay!

This occurs repeatedly and it contains 90% of my log file. Is there any way to avoid this?

When I checked in detail, I found that it is throwing from a method in EJB. That EJB class is annotated as @RolesAllowed("admin") and this method has @PermitAll annotation. I suspect whether I missed anything and that causes this DEBUG message.

[jaysensharma]

If you will be running your server on DEBUG mode or if you will configure the "org.jboss.security" logger category level to "DEBUG/TRACE"  then you will repeatedly see the same message.

If you really want to avoid that kind of logging then change changing "org.jboss.security" logger category level to INFO and then see:

<logger category="org.jboss.security">
      <level name="INFO"/>
</logger>

[valsaraj007]

ok, let me check.

[mletenay]

As I mentioned in the related SECURITY-864 issue, the thrown and caught exception is not only polluting logs but has also a severe negative performance impact.

Performance of our (secured ejb calls intensive) application went down by factor of 10 after switch from JBoss 7.1 to Wildfly 9.

The problem is that the JNDI lookup is performed upon each and every (secured) EJB method invocation.

And in the case of Delegate or JACC authorization module the lookup is always negative (with NamingException thrown), since the PolicyRegistration seems to be relevant only for XACML authorization modules.

The JNDI lookup, exception throw and catch and log is a serious unnecessary overhead for every EJB invocation in non-XACML scenarios.