Java 7 update started by Oracle 25 Since our applications are no longer function.
Initially we got some warning about codebase & amp; The Survival tag which disappears in the manifest file, which we have decided.
The problem now is that we only get the following lines in the console:
#### Java Web Start Error: #### Null We also get an application error dialog with the message: Unable to launch the app . The Details button gives the following details in the exception:
java.lang.NullPointerException at com.sun.jnlp.JNLPClassLoader.getPermissions (unknown source) java.security. on SecureClassLoader java.net.URLClassLoader.access $ 100 on .getProtectionDomain (SecureClassLoader.java:206) java.security.SecureClassLoader.defineClass (SecureClassLoader.java:142) on java.net.URLClassLoader.defineClass (URLClassLoader.java:449) (URLClassLoader Java: 71) java.net.URLClassLoader $ 1.run (URLClassLoader.java:361) java.net.URLClassLoader $ 1.run (java.security.AccessController.doPrivileged (URLClassLoader.java:355) Native method ) At least java.net.URLClassLoad er.findClass com.sun.jnlp.JNLPClassLoader.findClass (URLClassLoader.java:354) (unknown source) java.lang.ClassLoader.loadCla Ss (ClassLoader.java:424) on java.lang.ClassLoader.loadClass (classloader at Java: 357) desktop.DesktopProxySelector on & lt; Init & gt; (DesktopProxySelector.java:24) & lt; - Smipete code at desktop.Main.main (Main.java:139) & lt; Smipet the code down at sun.reflect .. NativeMethodAccessorImpl.invoke0 sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:57) (Native Method On sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke) (Method . Java: 606) (unknown source com.sun.javaws.Launcher.executeApplication) on com.sun.javaws.Launcher.executeMainClass on com.sun.javaws.Launcher.doLaunchApp (unknown source) com.sun (unknown source) But on Java.lang.Thread.run (unknown source). Javaws.Launcher.run (Thread.Java: 724) The related code sections are:
Desktop.Main.main / ** * The main method, Application start / public / static zero main (string [] args) {System.setProperty ("java.net.useSystemProxies", "true"); //Logger.getLogger ("httpclient.wire.header.level").setLevel(Level.FINEST); //Logger.getLogger("org.apache.commons.httpclient.level").setLevel(Level.FINEST); Java.net.ProxySelector.setDefault (New DesktopProxySelector (java.net.ProxySelector.getDefault ())); (last line is line number 139)
desktop.DesktopProxySelector: public class DesktopProxySelector extends ProxySelector {public DesktopProxySelector (ProxySelector defaultSelector) {URI httpsUri = new Central Configuration Service () GetCentralLocation (); (the previous line is line number 24 where the exception occurs)
Can someone give us some clue (or better solution) for this new behavior of Java This is due to the 'minor' update.
When we download the application directly from the Java-Jare Desktop, the applications use the Willy Run file, so this issue has clearly done with the changes in the Java web. Get started.
@trashgod: Error is clearly something in the permissions with changes in 7u25, because NullPointerException occurs in com.sun.jnlp.JNLPClassLoader.getPermissions.
What I think just explain (I would Wouter am a fellow): desktop.Main a DesktopkDesktopProxySelector (reflects our class), reflects desktop.DesktopProxySelector desktop.configuration. The CentralConfigurationService desktop.configuration.CentralConfigurationService shows a java.net.URI.
The first line of the DesktopProxySelector init where the CentralConfigurationService getPermissions method is instantiated, upon the called from JNLPClassLoader, throws NullPointerException. Therefore, with the permission for the class, something is going wrong while Java Webstart loads the central configuration service class. Could that happen with the fact that a URI class instantiated, which did not require additional permission (connection to a remote URI is setup)?
"text after" itemprop = "text"> Eventually the problem was resolved. This problem occurs between a mismatch in the jar files contained in the main MANIFEST.MF file, which happens with jar files mentioned in the launch.jnlp.
All jar files will now be partly present in the launch.jnlp file also used.
(In the past it was decided to keep this file in sync manually, which was clearly not always kept in a proper manner. Now this process is automated, so the problem is now our Should not be accompanied.)
No comments:
Post a Comment