[
https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug...
]
Eric B edited comment on SECURITY-864 at 7/24/17 5:00 PM:
----------------------------------------------------------
I am encountering the same issue as well after a JB4 -> Wildfly 10 migration. Although
I have not yet done performance tests, my application is EJB intensive as well and I am
definitely concerned by [~mletenay]'s performance results.
[~mletenay] Are you able to provide sample code that you use to workaround this issue?
[~pmm] 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)?
was (Author: benze):
I am encountering the same issue as well after a JB4 -> Wildfly 10 migration. Although
I have not yet done performance tests, my application is EJB intensive as well and I am
definitely concerned by [~mletenay]'s performance results.
[~mletenay] Are you able to provide sample code that you use to workaround this issue?
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)