Bug 1061181

Summary: [RHEV] (6.2.x) The upgrade of the AS from EAP 6.2.0 to 6.2.1 caused a problem in jboss-as-naming for RHEV
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Carlo de Wolf <cdewolf>
Component: NamingAssignee: Carlo de Wolf <cdewolf>
Status: CLOSED CURRENTRELEASE QA Contact: Josef Cacek <jcacek>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.2.1CC: cdewolf, cpelland, fnasser, iheim, jcacek, jkudrnac, juan.hernandez, myarboro, omachace, rdickens, vtunka
Target Milestone: CR4Keywords: Regression
Target Release: EAP 6.2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
An upgrade to the jboss-as-naming package has resulted in the failure of LDAP-specific methods such as getRequestControls. The root cause is that during startup the new version of the jboss-as-naming package is registering an InitialContextFactoryBuilder class that ignores the Context.INITIAL_CONTEXT_FACTORY property given by the user. In some instances this can result in an InvalidNameException error. No known workaround is available but it is expected to be resolved in a future update patch update. Result:
Story Points: ---
Clone Of: 1060275 Environment:
Last Closed: 2014-02-24 20:15:08 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: 1060275    
Bug Blocks: 1027004, 1060867    

Comment 1 Russell Dickenson 2014-02-11 04:26:58 UTC
Attention: Carlo

I have drafted a release notes entry for this BZ ticket but I need your review to ensure it is accurate.

Comment 2 Josef Cacek 2014-02-11 13:35:23 UTC
Verified in 6.2.1.CP.CR4.

Comment 3 Russell Dickenson 2014-02-11 13:57:12 UTC
After checking with Carlo, I realised that since this issue could not have affected a customer, a RN entry is not applicable. I have therefore cleared the flag.