Hi again, sorry forgot the following note
You mention problems with the Logging classes, did you read the following snippet in the release notes for Java 1.7u25:
Synopsis: Remove the stack search for a resource bundle for Logger to use
java.util.logging.Logger class no longer does stack walk search for a logger's resource bundle. The stack walk search was intended as a temporary measure to allow containers to transition to using the context class loader and was specified to be removed in a future release. It will use the thread context class loader (if not set, use the system class loader) to look up the resource bundle and, if not found, it will fall back to use the class loader of the caller class that creates the Logger instance (via the Logger.getLogger() and Logger.getAnonymousLogger() method with a given resource bundle name).
If applications have not transitioned to use the thread context class loader as specified in the Logger class specification and depend on the temporary stack walk search behavior,
java.util.MissingResourceException exception will be thrown if it fails to find the resource bundle.
The workaround is to set a system property,
-Djdk.logging.allowStackWalkSearch=true, at the command-line to enable the stack walk search. This workaround is also temporary and will be removed in a future 7 update release. It is strongly recommended for applications to transition and remove the dependency on the stack walk search.
I did look at that, no help though. On that matter I'm seeing a null return value from the following line of code that gets the root logger, and no exceptions occur.
The LogManager javadocs state that root logger will never be null, and in looking at the code for LogManager the only way it could be null is if the static initializer did not run or if the AccessController.doPrivileged() call in the static initializer failed to execute. I suspect AccessController.doPrivileged did not run the code, yet the Web Start trace log shows all code is trusted with all permissions.
This only happens when launching from Java Web Start 7u25 with Java Console not showing. Making that Java Console visible does something special that I'd like to dig into, but I understand that source code is unavailable. I also find it interesting that 6u45 for Windows (released same day as 7u25) does not have these problems, but 1.6.0_51 for Mac has some issues that 6u45 does not and we're still researching those here.
I just tried the workaround mentioned here: Java 7 Update 25 Client App Downloaded From Web Start Can't Connect Out
So far it looks promising - need a few more people to test it, but the W7 test PC I use now seems to work.
We encountered the same problem, the solution that worked for us is to set the context class loader manually.
final ClassLoader workingClassLoader = Thread.currentThread().getContextClassLoader();
The safe way of doing this is to make sure it is done for 7u25 only.