Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Yes, Javawebstart is not just used to start an app starting from a simple visit of the web via your browser. It is used also for JNLP deployment. And applications that need MORE than just 2-3 GB are really existing. JavaWebStart DID work in the past to start in 64 bit mode. But now javawebstart no longer honors the -D64 command line flag given to the command line parameters of the VM (what is even worse is that we are even limited to about 247MB even if we pass the VM parameters -Xmx (which are no longer honored too !!)</p> <p>Using JNLP applications is now impossible. We need full support of 64 bit mode (and a way to pass VM creation parameters). This is not just a limitation but a severe return to the old ages, with Java VM becoming now extremely slow and swapping.</p> <p>It looks like the Java documentation is wrong now or the support parameter for it has changed. If you ever have installed some tool that provides associations of JNLP with a command, it is possible that it has changed the mapping using an installation of the 32 bit version only of Javawebstart in \windows\syswow64 (which the Java control panel will not detect and not update), when at the same time you have the latest update instaleld in \windows\system32 with a 64-bit javaws laucnher that suports BOTH 32-bit and 64-bit VMs.</p> <p>To start java in 64-bit when you have installed both 32-bit and 64-bit versions, you need to check the shortcut created on the descktop or start menu to see that it effectively usees the correct path in \windows\system32 and that the parameter "-J-d64" is present (as well as "-J-Mx=3048m" if you want to increase the maximum size of the VM. Otherwise your VM will be 32 bit and limited to 247 MB !!!</p> <p>I hate those tools that install and change the Java installation somewhere else, without properly registering them in the Windows registry using a supported installation method (not just for their own use, but trying to change associations of file types.</p> <p>Anyway there's a bug in the Java control panel for Windows if it does not help restoring the file associations, and does not detect that another JRE has been setup (most often oan outdated version !) And the documentation still incorrectly states that we must use the folllowing VM parameter "-D64" when it should be "-d64" (the former is just used to define a property with an unset value in the environment).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload