Up until recently, I was able to launch/open JNLP files in Firefox using Java web start.
Don't know what happened all of a sudden JNLP files stopped launching, a splash screen appears saying Java Starting... and then nothing happens. Even the Java Console in the browser and javacpl.cpl applet doesn't open.
Tried all possibilities: removed all older version and installed the latest JRE (java version "1.6.0_17"), still it doesn't work.
Done some googling for this problem, people suggested to start javaws.exe with -viewer option but same behavior (a splash screen appears saying "Java Starting..." and then disappears)
The problem is that I don't know any place (logs etc.) to look for to see what is causing the problem.
I am using WinXP SP3, and some of the screenshots below shows further info about my system.
I can provide any other detail if required but please help me solve this problem.
Have a look at what happens if you run javaws.exe directly from the command line.
I know this is an older question but this past week I started to get a similar problem, so I leave here some notes regarding the solution that fits me.
This happened only in some Windows machines using even the last JRE to date (1.8.0_45).
The Java Web Start started to load but nothing happened and none of the previous solution attempts worked.
After some digging i've found this thread, which gives the same setup and a great explanation.
https://community.oracle.com/thread/3676876
So, in conclusion, it was a memory problem in x86 JRE and since our JNLP's max heap was defined as 1024MB, we changed to 780MB as suggested and it was fixed.
However, if you need more than 780MB, can always try launching in a x64 JRE version.
i had the same problem here. go to your Java Control Panel and Settings... Uncheck 'Keep temporary files on my computer'. Apply changes and try again your .jnlp
Note: Tested on different machines; Windows Server 2012, Windows Server 2008 and Windows 7 64bit.
Java Version: 1.7++ since my jnlp app is built on 1.7
Please let me know your feedback too. :D
Java web start should be enabled.
Check if javaws (Java web start is enabled for your system), Use below command in console to open java control panel.
javaws -viewer
If javacpl does not open and gives you Could not find the main class:, it could be that Java is confused because of changes in deployment.properties (can be found in C:\Users\<username>\AppData\LocalLow\Sun\Java\Deployment on Win7). Delete that file and everything's fine.
This bug seems to be 6 years old, cf. An app should be able to ignore properties that have become obsolete over time, shouldn't it?
Although this question is bit old, the issue was caused by corrupted ClearType registry setting and resolved by fixing it, as described in this ClearType, install4j and case of Java bug post.
ClearType, install4j and case of Java bug Java
Do you know what
ClearType (font-smoothing technology in Windows) has in common with
Java (programming language and one of the recommended frameworks)?
Nothing except that they were working together hard at making me
miserable for few months. I had some Java software that I couldn’t
install. I mean really couldn’t – not even figure out reason or
reproduce it on another PC.
Recently I was approved for Woopra beta (site analytics service) and
it uses desktop client written in Java… I couldn’t install. That got
me really mad. :)
Story All of the software in question was similar :
setup based on install4j; setup crashing with bunch of errors. I was
blaming install4j during early (hundred or so) attempts to solve
issue. Later I slowly understood that if it was that bugged for that
long time – solution would have been created and googled.
Tracing After shifting focus from install4j I decided to push Java
framework. I was trying stable versions earlier so decided to go for
non-stable 1.6 Update 10 Release Candidate.
This actually fixed error messages but not crashes. I had also noticed
that there was new error log created in directory with setup files.
Previously I had only seen logs in Windows temporary directory.
New error log was saying following :
Could not display the GUI. This application needs access to an X
Server. If you have access there is probably an X library missing.
******************************************************************* You can also run this application in console mode without access to an
X server by passing the argument -c Very weird to look for X-Server on
non-Linux PC, isn’t it? So I decided to try that “-c” argument. And
was actually able to install in console mode.
Happy ending? Nope. Now installed app was crashing. But it really got
me thinking. If console works but graphical interface doesn’t – there
must be problem with latter.
One more error log (in application folder) was now saying (among other
things) :
Caused by: java.lang.IllegalArgumentException: -60397977 incompatible
with Text-specific LCD contrast key Which successfully googled me
description of bug with Java unable to read non-standard ClearType
registry setting.
Solution I immediately launched ClearType Tuner from Control Panel and
found setting showing gibberish number. After correcting it to proper
one all problems with Java were instantly gone.
cleartypetuner_screenshot Lessons learned Don’t be fast to blame
software problems on single application. Even minor and totally
unrelated settings can launch deadly chain reactions. Links Jave
Runtime Environment http://www.java.com/en/download/index.jsp
ClearType Tuner
http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx
Woopra http://www.woopra.com/
install4j
http://www.ej-technologies.com/products/install4j/overview.html
I was also facing the same problem. To fix this to the following steps.
open Javaws from cmd runnig javaws -viewer command. A new window will open
Select the jnlp file which you want and click the run button.
Close the javaws viewer window.
Same solution worked as suggested by hpereira
The issue was due to JRE version was 32 bit and not 64 Bit
Check with java -version to see if your Java is 64 bit
C:\>java -version
java version "1.8.0_192"
Java(TM) SE Runtime Environment (build 1.8.0_192-b12)
Java HotSpot(TM) **64-Bit Server** VM (build 25.192-b12, mixed mode)
Is this an application to which you have the code? Java 6u14 included a change to the way it handles jar security that for us caused very similar issues. If your jars are signed and work with Java 6u13 or below, you might consider either refactoring your code to work around this update or requiring Java 6u13 or below. Unfortunately I don't recall exactly what we did to resolve the issue - it was panic mode at the time.
Again, if you have the code you have tools to work with. You can put in System.out.println statements in your startup routines - anything console output is displayed in the command window when you run the JNLP from the command line. Otherwise you might consider using a nice logger like log4j to get a better idea of the point of failure.
You may also consider removing the application entirely and downloading it anew. Java Web Start has a Control Panel applet that allows you to see the URL your app is downloading from (could be the wrong one), uninstall the app, set security options, etc.
I had the exact same problem. Turned out that the max-heap-size was set to 1024 and missing the unit. The configuration needed to be max-heap-size=1024m.
So apparently invalid memory configuration in the jnlp file will cause this exact behavior.
In my case, the problem was caused by starting my app from a shortcut on the public desktop (windows 7). As a result, as far as I can tell, the temporary files location was set to c:\users\public\etc. This resulted in the unable to write to cache detail. When I reset to defaults in the temporary files control applet, all worked fine.
In my case, Netbeans automatically creates a .jnlp file that doesn't work and my problem was due to an accidental overwriting of the launch.jnlp file on the server (by the inadequate and incorrect version from Netbeans). This caused a mismatch between the local .jnlp file and the remote .jnlp file, resulting in Java Web Start just quitting after "Verifying application."
So no one else has to waste an hour finding a bug that should be communicated adequately (but isn't) by Java WS.
This can also be due to environment variable CATALINA_HOME in your system. In our organization there were several cases where JNLP applications just refused to start without logging anything and emptying CATALINA_HOME solved the issue.
I had the environment variable set in the command prompt and it didn't appear in GUI. I'm not sure if setx command or register removal commands did the trick. Restart seems to be necessary after removing the variable.
I believe this is a security problem. If I download the jnpl file and execute it after a clean java 8 installation via javaws myfile.jnpl everything is working fine (I get multiple windows where I have to confirm some security problems).
I wanted to share the root cause for my issue. I was using High DPI in Windows and this caused JNLP to not launch. I had to turn off High DPI for this to work. Hope this helps.
Try Java Web Launcher, rather than Java Web Start Launcher. It worked for me.
Right-click on the JNLP file that is not opening and select Open With.
In the ‘How you want to open this File’ window, scroll down and click on Look for another app on this PC option.
When the File Explorer window opens, navigate to the following location:
C:\Program Files (x86)\Java\jre1.8.0_261\bin
or the folder for 64bit version
Select javaws.exe and click the Open button. This will open the JNLP file as intended.
Make sure to check the Always use this app to open .jnlp files.
That's all.
Related
I've been trying to run OldSchool RuneScape on my desktop and whenever I try any of the launch options that Jagex provides, nothing happens. I've had extensive talks with their staff and it's to the point where they don't know what's wrong, but I have a pretty good idea.
Whenever I try to install 32 bit Java (Online or Offline), I get "java error code 1603". The official help page for this error on the Java website says that they don't know what causes this error, but have two possible solutions. I have tried both, they don't work.
I do have x64 Java installed and working, but OSRS requires x86. So, what do?
Side note, I know this might not be the right place for this question. If not, please redirect me to the right spot.
EDIT: I've managed to install previous versions of x86 Java (6 and 7), but they throw this error https://i.imgur.com/cxqsj91.png before "confirming" that Java has been installed correctly. Despite this confirmation, still nothing works. I'm in talks with the RS mods again and we're working through more confirmations. If I get this working before someone else suggests here, I'll update this again.
SOLUTION: I used an uninstall tool called JavaRa to remove lingering files as well as removing anything Java-related from System PATH, then re-installed Java. Now it works. Don't understand why, but I'm not questioning it.
check here
1 Close the installer when you see Java error 1603. (It has installed a bunch of files, but exits prematurely.)
2 Open javacpl.exe from C:\Program Files (x86)\Java\jre1.8.0_XX\bin (or for x64, C:\Program Files\Java\jre1.8.0_XX\bin) where XX is the update number.
3 Uncheck Enable Java content in the browser on security tab and click OK to close Java control panel
4 Retry installing Java. It usually succeeds for this time.
5 Open javacpl.exe again (see step #2)
6 Check Enable Java content in browser on security tab and click OK to close Java control panel
7 If it still fails, try uninstalling windows update KB2918614, then reboot and try these steps again
We have a Java web app that uses javaws. It will run fine under Java 8 update 40, but under Java 8 update 51 jp2launcher.exe just stops, without launching the application.
I have found the logs in C:\Users\me\AppData\LocalLow\Sun\Java\Deployment\log but they're identical between j8u40 and j8u51 (except of course for the order jars are loaded, the jre version and the launch time).
I have logged the launch using Process Monitor, for both jre versions. Under j8u51, jp2launcher.exe just exits with the resule "SUCCESS". Comparing the two procmon logs, I can't pick out anything unusual. They both rummage through the C:\Users\me\AppData\LocalLow\Sun\Java\Deployment directory and their respective C:\Program Files\Java\jre1.8.0_XX\lib directories and such like, but then the j8u51 one just exits.
The Windows event logs don't show anything Java related.
Is there anywhere else I can look for diagnostic information? Any suggestions on what might be going wrong here?
update: I have managed to run the jnlp with set "JAVAWS_VM_ARGS=-Xcheck:jni -XX:-TraceClassLoadingPreorder -XX:+PrintCommandLineFlags -verbose:jni -verbose:class -verbose:gc -XX:+PrintGCDetails -Djava.util.logging.config.file=C:\misc\logging.properties" and log the stdout/stderr. It looks like javaws and jp2launcher log to the output, then both jre8u40 and jre8u51 versions terminate. Presumably in the j8u40 version it is launching another jp2launcher.exe to run the application.
Comparing the two output logs yields nothing of interest. The classes are loaded in nearly identical order, mostly identical classes other than a few differences that are easily explained by just being more up-to-date classes being used.
further update: I have been able to launch the application directly, using java.exe, by obtaining the client files from the server install and unpacking them. The app itself runs just fine under jre8u51, so the problem definitely lies with javaws itself.
update3: clearing the cache does not solve the problem. The issue occurs on separate machines, even with entirely fresh Java installs.
update4: As an experiment, I've just tried under Ubuntu Linux. Our product does not technically support Linux, but I thought I'd try anyway. As it happens, the behaviour is identical! Under jre8u40 the app launches, and under jre8u51 it does not!
5: it turns out the problem is happening under u45 as well, which is the update immediately after u40. So, the cause seems to be something that changed in u45, rather than in u51.
Got it!
There are a few interacting elements here:
The jnlp contains a j2se element for Java 6 and for Java 7. Running on Java 8, it appears that it uses the Java 6 entry.
The Java 6 entry specifies VM arguments, while the Java 7 one does not.
After trial and error, I have determined that the -XX:+CMSIncrementalMode VM argument is what’s causing it to fail. I don’t know what this arg does, but apparently JRE8u45+ doesn’t like it.
I downloaded and modified the jnlp to test the above. To get javaws to actually use my changes, I had to remove the href attribute of the root jnlp element. Otherwise, javaws ignored my changes and used the copy of the jnlp on the server.
My current hypothesis is that JRE8u45+ has a bug where it uses the VM arguments from the wrong version.
I have just tested a custom jnlp with 1.6, 1.7 and 1.8 entries in it, where the 1.6 one has the vm args and the 1.7 and 1.8 ones do not.
Javaws does not prompt “The application wants to use Java 7, but you should instead use the most up-to-date one on your system, is that ok?”. Therefore, at this point is has recognised that there is a 1.8 entry in there.
However, it fails to launch the app. Therefore, at that point, it must have got confused about what jnlp element it was on.
So, it looks like the workaround is to remove the -XX:+CMSIncrementalMode VM arg from the jnlp on the server side.
I'm sure this has a relatively simple answer -_- , but I keep getting a ton of errors and I have no idea why.
Here is the guide I am following:
http://akbarahmed.com/2012/05/12/install-pentaho-bi-server-4-5-on-windows-7-x64/
I am using Java 1.8.0.05, and biserver-ce-5.0.1-stable
When I run start-pentaho.bat, and the Tomcat window opens, I get a whole host of errors.
If I go to localhost:8080/pentaho, I get the following errors:
One or more system listeners failed. These are set in the systemListeners.xml.
org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 -
Error while trying to execute startup sequence for
org.pentaho.platform.repository2.unified.BackingRepositoryLifecycleManagerSystemListener
I have gone through this entire process 3 times, but nothing seems to work.
There are 3 things you have to take care of:
When running on windows, it is easy to run into Windows' path-length limitation. This then will break the jar-loading which in return gives you random errors as the Tomcat server cannot find the classes contained in these jars. So when you install, do not install it deep into a directory, keep it at the root of your disk. From hard experience, I now always install it in DRIVE:\Pentaho
The Server will not run without the system database. If your logs show you a Quartz-Error, or a Hibernate error, then your HSQL database is not running. In the download, you'll find a "data" directory. Start the "start-hypersonic.bat" before you start the main Pentaho server.
Pentaho does not run with Java 8. There seem to be some incompatible changes in the JDK and I have not been able to actually start it up correctly. You have to use JDK 1.7 to be successful. ALso make sure that your JAVA_HOME or PENTAHO_JAVA_HOME points to the correct JDK.
The Pentaho bat files try to locate a Java installation automatically, and without explicitly setting these environment variables, any JDK may be picked up at random. Usually that is the last JDK that has been installed or updated. So to be safe, lock down the JDK by setting these variables (via Control Panel-> System -> Advanced System Settings -> Environment Variables)
You need to check the catalina.out and pentaho.log files (both should be at biserver-ce/tomcat/logs).
They'll give you more detail on why the server is not starting.
I was having the same error when I installed Java 8 and even after I reinstall Java 7 without removing Java 8 completely.
Remove all Java installations, then you install Java SDK 7
Set the environment variable PENTAHO_JAVA_HOME as your Java 7 path
Then you reboot your computer
Then you start Pentaho BI Server
Hope this help you.
BTW, don't use IE or Safari.
This question was dogging me for a few days until I found almost a full answer but I want to share the issue first:
ISSUE
I have a Windows 7 pro 64 bit laptop that supports both IPv4 and IPv6 (important later)
I downloaded and installed the latest Java 7 u 51 jre / browser plugin and would always get a grey applet box before it would eventually redirect and say "failed to verify" if java was installed.
I am also a java developer and had a few JDKs installed as well as jres. Thinking it was my environment I did a complete wipe of jave from my system (I ran JavaRa and made sure everything was removed http://singularlabs.com/software/javara/)
I installed the 32 bit version of the JRE for the chrome plugin and made sure all the setting and security info was correct (per the many posts about this topic).
After clearing all cache (browser and java), punching holes through my firewall (even disabling it to see if that would resolve it) as well as running things as administrator, verifying java was installed and running in all my browsers (it failed in IE, Chrome and FF)
All of this was per many posts that said how to solve the issue of Java 7 not running in any browser.
After enabling full trace and debugging with the Java console via the Java Control Panel
I finally get some decent clues from the stack traces displayed in the console. It was failing to get resources from java or any site that had an applet or jnlp web start file.
SOLUTION
Finally I ran across this post here (Java 7 on 32-bit Windows 7 - Java Webstart - Unable to load resource)
When adding "-Djava.net.preferIPv4Stack=true" to the runtime parameters under the Java Control Panel (java tab, view) for the current JRE, it solved the problem. I was able to restore my security setting to proper levels and was able to run the java verification tests as well asa bunch of other applets just fine.
When it cam to running jnlp files, I would still get errors unless I manually edit the jnlp file and add it to the vm args i.e.
If you want to apply this change system wide, add the _JAVA_OPTIONS environment variable and add -Djava.net.preferIPv4Stack=true to it
Regards, Shawn Recinto
We are using Windows 8.1 and after updating to the newest java 7u51 we had the same problem and after tech service gave up on our problem, using your help, we found that there was a check box in the Java Control panel that said "Enable Java content in the browser" just needed to be checked. This apparently still needed to be done even though it had already been enabled in the internet settings 'manage add-ons'.
This check box was under the Security Tab in the Java Control Panel.
If you have Chrome and 64-bit Windows here is the answer (originally found here):
"... We all will just have to not use Chrome until they have another release or patch to fix the problem, or roll back Java to pre-7 versions.
"Chrome does not support Java 7. Java 7 runs only on 64-bit browsers and Chrome is a 32-bit browser.
If you download Java 7, you will not be able to run Java content in Chrome and will need to use a 64-bit browser (such as Safari or Firefox) to run Java content within a browser. Additionally, installing Java 7 will disable the ability to use Apple Java 6 on your system..."
Solution
This is a Java.net.SocketException, problem the first answer is correct but here is a very quick way of solving this problem in under a minute.
How to fix
Open command prompt (windows start button, type cmd in search)
Click top left of command prompt, click properties, enable quick edit mode
Copy: setx _JAVA_OPTIONS -Djava.net.preferIPv4Stack=true
Right click on command prompt, should paste
Hit enter. That easy!
After following these steps you applets/java applications should run well and correctly.Refer to this site youtube video for visual presentation.https://www.youtube.com/watch?v=serdRSsl5wE
This is a Java.net.SocketException, problem the first answer is correct but here is a very quick way of solving this problem in under a minute:
Open command prompt (windows start button, type cmd in search)
Click top left of command prompt, click properties, enable quick edit mode
Copy: setx _JAVA_OPTIONS -Djava.net.preferIPv4Stack=true
Right click on command prompt, should paste
Hit enter. That easy!
After following these steps you applets/java applications should run well and correctly.Refer to this site youtube video for visual presentation.
Reference: https://www.youtube.com/watch?v=serdRSsl5wE
I am trying to run a java jnlp application from my computer. Every time I try launch the file I get the error java.lang.NoClassDefFoundError: java/security/CodeSigner
From searching Google it seems to be a common enough problem and is normally blamed on 'java 6'. I couldn't find a solution that doesn't involve rolling back to an older java version.
Does anyone know how fix this without reverting versions?
Looks like SUN JRE 1.6.0_14 was the last SUN JVM without that nasty bug... I'd install that version in parallel and use it more or less exclusively for jnlp applications, that still request Java 1.4. (guess you can't change the jnlp application so that it request a higher Java version)