2 Replies Latest reply on Jul 28, 2013 5:47 AM by smith.gerry Branched from an earlier discussion.

PBOX000293: Exception caught: javax.naming.NameNotFoundException: policyRegistration

smith.gerry Jul 27, 2013 10:55 PM

I am also getting this exception:

The log level is DEBUG, so perhaps a lot of people get it but haven't seen it.

I saw another post that it's caused by not having the policy security domains in the config file, but I do have those domains. (https://community.jboss.org/message/775155#775155)

The exception is reported before every jndi call.

Although I'm trying to debug a problem [since upgrading to 7.2, I seem to have to log in twice through the web tier to have a principal in the ejb tier], this exception doesn't seem to stop anything from working, but when I have logging set to trace it slows processes down and fills the log with chaff that makes debugging difficult (and now in 7.2 you need DEBUG messages to get any info on why authorization fails).

Any ideas what could cause this exception?

Thanks,

Gerry

1. Re: PBOX000293: Exception caught: javax.naming.NameNotFoundException: policyRegistration

jaikiran Jul 27, 2013 10:56 PM (in response to smith.gerry)

You can ignore those DEBUG stacktraces. It's the way it's implemented. As for enabling TRACE levels, for production the recommended log level is INFO. So you shouldn't be running into this problem in production environments.
Actions
2. Re: PBOX000293: Exception caught: javax.naming.NameNotFoundException: policyRegistration

smith.gerry Jul 28, 2013 5:47 AM (in response to jaikiran)

OK thanks,
Yes indeed, but when you do need to debug, it's difficult with all those stack traces.
Since upgrading from 4.2 to 7.2 I've had to physically login twice to have a principal when I called create on a session bean. (I'm still using 2.1). Having tried everything I can think of, I've made my GWT code login twice. That works fine but obviously not a very satisfacotry solution.

Gerry
Actions

Go to original post