Bug 1215715
| Summary: | (6.4.z) Get the SASL client factories from a privileged block, in case Remoting was loaded from the null class loader | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Brad Maxwell <bmaxwell> |
| Component: | Remoting | Assignee: | David M. Lloyd <david.lloyd> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jitka Kozana <jkudrnac> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.0 | CC: | bbaranow, cdewolf, jawilson, rjanik, rsvoboda |
| Target Milestone: | CR2 | ||
| Target Release: | EAP 6.4.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-17 10:12:56 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: | 1199231, 1219165 | ||
|
Description
Brad Maxwell
2015-04-27 14:18:00 UTC
Please include more detailed description of the problem linked commit is solving. SET/GSS - please provide automated test (as discussed on triage) to increase CP throughput. I will qa_ack afterwards or when the scope of CP01 is clear and we have enough seats. Please include more detailed description of the problem which is soled by linked commit. FYI - there is no customer case attached to this BZ. Fixing null classloader by adding a doPrivileged block does not seem to work for me - classloader is still null - thus FailedQA. Since the last customer ticket has been removed, this bug no longer has a valid customer ticket related to it. Details below: I've been trying to reproduce the situation where the getClass().getClassLoader() call returns null. I've done that by creating a jar file which contains a testing class (and its methods return the class loader name with and without a doPrivileged block). Then I created another project which calls the methods of the testing class and I've added the jar file to -Xbootclasspath. Thus, when calling a method of the testing class the methods were run from a context with bootstrap (null) classloader. However, both calls to getClass().getClassLoader() (with and without a doPrivileged block) returned null. The point of this issue isn't to somehow magically prevent the class loader from being "null". The point is to ensure that when the class loader *is* null, and a security manager is present, that the class can be loaded without an error. Retroactively bulk-closing issues from released EAP 6.4 cumulative patches. |