Bug 1510010

Summary:	[GSS](6.4.z) NameNotFoundException due to policyRegistration -- service jboss.naming.context.java.policyRegistration
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	tmiyargi
Component:	Security	Assignee:	jboss-set
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Slavicek <pslavice>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4.17	CC:	anmiller, bdawidow, bmaxwell, darran.lofthouse, jondruse, psilva, pskopek
Target Milestone:	CR1
Target Release:	EAP 6.4.20
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:40:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1510090

Description tmiyargi 2017-11-06 14:38:41 UTC

"NameNotFoundException due to policyRegistration – service jboss.naming.context.java.policyRegistration" is recorded in server.log during quickstart example run by changing log level:
<logger category="org.jboss.as.security">
<level name="TRACE"/>
</logger>
<logger category="org.jboss.security">
<level name="TRACE"/>
</logger>
See detailed description in community discussion #907134
I choose Jira component picketbox since the exception is titled as "PBOX000293: Exception caught: javax.naming.NameNotFoundException"

To reproduce:
run ejb-security example with trace log level for "org.jboss.secuirty" and "org.jboss.as.security". Then login from page: localhost:8080/wildfly-ejb-security with username and password. The result is successful, however, you will see the exception in server.log file.

Comment 1 tmiyargi 2017-11-13 08:21:25 UTC

This situation causes a big performance problem since there is a JNDI lookup performed that is not needed.

Comment 8 Jiří Bílek 2018-05-02 14:47:54 UTC

Regression tests passed
Verified with EAP 6.4.20.CP.CR1