Get the SASL client factories from a privileged block, in case Remoting was loaded from the null class loader
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.