I am installing JDK 8 171 on windows 2016 server core using Ansible. When I install using the GUI, it updates my path on my workstation. But when I do it silently it does not. I will have to make Ansible update the path or the batch files if it won't, but that means changing the code for every new version of Java. I wanted to use JRE, but that fails to install at all on core 2016 with Ansible, it tries to update JavaWS reg settings for browsers and as there are no browsers, fails and rolls back. I've extracted the MSI and run a jdkxxxx.msi /? and see no parameters to tell it to update the path. Just wondered if anyone else had run into this, been trying different combinations for two days now and pretty much hit a wall with this now.
I suddenly found that I could no longer run my own developed JAVA apps by simply double-clicking the JAR file - it reported that the main class was not found.
With trial and error I found that if I forced 32-bit JAVA 1.8.0_161 to run then things worked fine. What was running by default was 64-bit JAVA 1.9. I also found it was not using JAVA_HOME but instead was running what it found in %APPDATA%\Oracle\Java.
I tried lots of things but in the end I uninstalled the 64-bit JAVA 1.9, put the path for 1.8.0_161 in JAVA_HOME, put %JAVA_HOME%\bin in the PATH and that got me most of the way...
Now if I run java -jar <jarFileName.jar> then my program runs just fine, but if I attempt to run the jar file by double clicking on it then it still could not load the main class.
Windows 10 default programs for JAR files says Java(TM) Platform SE Binary - tried forcibly changing this to point to the java.exe for 1.8.0_161 but that still doesn't work.
The JAVA Settings Console doesn't look like the ones in various web queries - I think it changed with 64-bit JAVA.
So I suspect my system is no longer properly configured.
How do I fixup the configuration to get back to where I can simply double click a JAR file in order to run it.
Best Regards
SteveM
I'm working on getting a Cassandra instance up and running, but i'm having issues telling Cassandra which Java installation to use. The situation is as follows:
The server has Java 6 installed, and all Java environment variables are pointed to this installation ($JAVA_HOME, etc). This installation is what every other program on the server utilizes right now.
Java 7 is also installed, in a separate location, but is not the version used by default.
I've attempted to dig into the cassandra-env.sh script in $CASS_HOME/conf and the cassandra script in $CASS_HOME/bin, but I haven't had much luck finding a place to specify a different $JAVA_HOME directory. Does anyone have experience with doing this sort of thing with Cassandra?
I did finally find this setting:
In the $CASSANDRA_HOME/bin dir, there is a file called cassandra.in.sh, there is a section that looks like this:
# JAVA_HOME can optionally be set here
JAVA_HOME=/usr/local/jdk6
You can modify this to have Cassandra use a different Java installation.
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.
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.