147 | | === Troubleshooting jar file ===#java |
148 | | |
149 | | ==== Double click does nothing ====#Doubleclickonafiledoesnothing |
150 | | |
151 | | In most cases this means Java wasn't installed. |
152 | | JOSM is tested and developed with Oracle JVM, therefore we recommend to get it from their [https://www.java.com/en/download/manual.jsp manual Java download site]. |
153 | | Keep your systems architecture (32 bit or 64 bit) in mind when choosing the installation. Java 64 bit is recommended for JOSM. |
154 | | Note that ''Java'' is the common name for a product now called ''Java Runtime Environment'' or short ''JRE''. |
155 | | In former years slightly different names were used. |
156 | | Please avoid the page java.com/en/download because it has an automatic detection that can mislead you. |
| 148 | === Java ===#java |
| 149 | [=#Doubleclickonafiledoesnothing] |
| 150 | When you double-click on a jar file and nothing happens in most cases this means Java isn't installed. |
| 151 | |
| 152 | JOSM is tested and developed with Oracle JVM, therefore we recommend to get Java from their [https://www.java.com/en/download/manual.jsp manual download] site. |
| 153 | Mind yoursystems architecture (32 or 64 bit) when [https://www.java.com/en/download/faq/java_win64bit.xml choosing] the installation. Java 64 bit is recommended for JOSM. |
| 154 | ''Java'' is the common name for a product called ''Java Runtime Environment'' now or short ''JRE''. |
| 155 | Formerly other names were used. |
| 156 | Please avoid the page java.com/en/download because it tries to automatically detect your system architecture but fails much to often for being a real help. |
165 | | 1. Type `cd %homepath%\desktop ⏎` |
166 | | 1. Type `java -version ⏎` |
167 | | 1. Now you should see three lines with Javas version data. If you see any other message, Java is not properly working on your machine. |
168 | | 1. Type `java -jar josm-tested.jar ⏎` |
169 | | 1. Now you should see JOSM starting up. |
170 | | |
171 | | === Troubleshooting jnlp link ===#Troubleshootingjhlplink |
172 | | [#webstart] |
173 | | Launching JOSM via Web Start has many more possible error causes than the step-by-step way with first downloading a jar file and then running it. So please work the check |
174 | | So please download the [/josm-tested.jar josm-tested.jar] file and try to start |
175 | | Assuming, [wiki:Download#Doubleclickonafiledoesnothing JVM was already installed], read [https://www.java.com/en/download/faq/java_webstart.xml Web Start] help. |
176 | | |
177 | | === Troubleshooting JVM ===#Troubleshootingjvm |
| 165 | 1. Type `cd %homepath%\desktop `⏎ |
| 166 | 1. Type `java -version `⏎ Three lines with Javas version data sould appear. When you see something else then Java is not properly installed. |
| 167 | 1. Type `java -jar josm-tested.jar `⏎. Now JOSM should run, started from the [wiki:/Help:CommandLineOptions Command Line]. |
| 168 | 1. Quit JOSM. |
| 169 | 1. Type `josm-tested.jar `⏎. If JOSM starts again, the Windows Explorer can start jar files when you by doubleclick them. |
| 170 | |
| 171 | |
| 172 | === Web Start ===#Troubleshootingjhlplink |
| 173 | [=#webstart] |
| 174 | Launching JOSM via Web Start has many more error causes than traditional way with downloading a jar file and then running it. |
| 175 | So please complete the [#JavaTest Java Test] above before starting further [https://www.java.com/en/download/faq/java_webstart.xml Web Start] tests. |
| 176 | |
| 177 | ==== Web Start Test ==== |
| 178 | 1. Download [/josm-tested.jar josm.jnlp] to your desktop. |
| 179 | 1. Open a Terminal and move to the Desktop as above |
| 180 | 1. Type `javaws josm.jnlp`⏎. This should initially download JOSM, serve a security dialog and then launch JOSM. |
| 181 | |
| 182 | |
| 183 | === Virtual Machine ===#Troubleshootingjvm |
189 | | The three paragaphes below deal with older versions of Windows and Java. |
190 | | |
191 | | For Windows 64-Bit, beware that some browsers may install only a JRE 32 bit mode, but may also install their version of the Javawebstart tool somewhere else with different file associations. This may cause your JNLP to start with this alternate JRE because it runs the wrong version of Javawebstart which only supports the 32 bit VM, and sometimes is built with a restricted support for VM options and a max VM size not exceeding 256MB. |
192 | | |
193 | | Check, for example, if there's no other javawebstart in {{{\Windows\SysWow64}}}. You should not need it (the Java control panel will not detect it) and can safely delete it. Perfom cleanup and only keep the latest version of the JRE (1 for the 32-bit mode, another one for the 64-bit mode). |
194 | | |
195 | | For shortcuts created on the desktop for JNLP and running the Javawebstart launcher (from {{{\windows\system32}}}), make sure to pass VM parameters prefixed with -J and no intermediate space before the VM option. If you have installed both the 32-bit and 64-bit version, you should pass the option "{{{-d64}}}" if you want to select the preferred 64-bit VM. Note that some Oracle documentation pages indicate the option "-D64" with the incorrect capitalization!) |
| 195 | On older versions of 64 bit Windows sometimes the 32 bit mode JRE was additionally installed. Also some browsers brought their own JVM with limited capabilities. In those cases a Web Start from the browser would not use your Java installation but that from the browser. |
| 196 | |
| 197 | Check that there's no other javawebstart in {{{\Windows\SysWow64}}}. The Java control panel will not detect it and you can safely delete it. Perfom cleanup and only keep the latest versions of each JRE (One or the 32-bit mode, another one for the 64-bit mode). |
| 198 | |
| 199 | For shortcuts created on the desktop for JNLP and running the Javawebstart launcher , make sure to pass VM parameters prefixed with -J and no intermediate space before the VM option. If you have installed both the 32-bit and 64-bit version, you should pass the option "{{{-d64}}}" if you want to select the preferred 64-bit VM. Note that some Oracle documentation pages indicate the option "-D64" with the incorrect capitalization!) |