#15808 closed defect (othersoftware)
JOSM won't start using josm.exe under Windows (starting with josm-tested.jar works)
Reported by: | anonymous | Owned by: | anonymous |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Installer Windows | Version: | |
Keywords: | Cc: |
Description
JOSM won't start using josm.exe under Windows (starting with josm-tested.jar works). I updated JAVA and JOSM is also up to date. I tried deleting the cache and preferences files but it did not help.
Attachments (0)
Change History (13)
comment:1 by , 7 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:2 by , 7 years ago
Component: | Core → Installer Windows |
---|
comment:3 by , 7 years ago
Unfortunately there is no error message. josm.exe shows up 1 second in the task manager and that is all.
comment:4 by , 7 years ago
Resolution: | → worksforme |
---|---|
Status: | needinfo → closed |
It works for me. There is something wrong on your setup but we cannot guess what with so little information. Only you can investigate.
follow-up: 9 comment:5 by , 7 years ago
Does anyone have an idea how and what i could investigate? Any logfile or so where I could check what happens? As I said I tried deleting the preferences but it did not work.
follow-up: 8 comment:7 by , 7 years ago
I tried doing that. There is no output at all in cmd if I start josm.exe
is there maybe a switch or something to show more output. As I understand the exe just starts java right? So maybe there is a Java-Log somewhere?
comment:8 by , 7 years ago
Replying to anonym:
As far as I know, Java would log to the command line.
It might be helpful to know your version of Windows and Java. In addition: where did you download josm.exe and which version is it?
comment:9 by , 7 years ago
Replying to anonym:
... Any logfile or so where I could check what happens?
Start josm.exe with the --l4j-debug
option in a directory where josm.exe can create a file, i.e. your Desktop.
This will create a logfile launch4j.log. Please attach that file to this bug report.
See more at http://launch4j.sourceforge.net/docs.html#Runtime_options
comment:10 by , 7 years ago
Here is the log of launch4j.log:
Version: 3.10
CmdLine: C:\Program Files (x86)\JOSM\josm.exe --l4j-debug
WOW64: yes
Java min ver: 1.8.0
Java max ver:
64-bit search: SOFTWARE\JavaSoft\Java Runtime Environment...
32-bit search: SOFTWARE\JavaSoft\Java Runtime Environment...
Check: SOFTWARE\JavaSoft\Java Runtime Environment\1.8
Ignore: 1.8
Check: SOFTWARE\JavaSoft\Java Runtime Environment\1.8.0_171
Check launcher: C:\Program Files (x86)\Java\jre1.8.0_171\bin\javaw.exe (OK)
Match: 1.8.0_171
64-bit search: SOFTWARE\JavaSoft\Java Development Kit...
32-bit search: SOFTWARE\JavaSoft\Java Development Kit...
64-bit search: SOFTWARE\JavaSoft\JRE...
32-bit search: SOFTWARE\JavaSoft\JRE...
64-bit search: SOFTWARE\JavaSoft\JDK...
32-bit search: SOFTWARE\JavaSoft\JDK...
Runtime used: 1.8.0_171 (32-bit)
Heap -Xms: Requested 128 MB / 0%, Available: 2264 MB, Heap size: 128 MB
Heap -Xmx: Requested 1024 MB / 0%, Available: 2264 MB, Heap size: 1024 MB
Launcher: C:\Program Files (x86)\Java\jre1.8.0_171\bin\javaw.exe
Launcher args: -Xms128m -Xmx1024m -jar "C:\Program Files (x86)\JOSM\josm-tested.jar"
Args length: 69/32768 chars
Exit code: 1
comment:11 by , 7 years ago
A successful launch from an elevated command prompt with Admin rights on a Windows 7 64 Bit system with both Java 64-Bit and Java 32-Bit installed gives this log:
Version: 3.10 CmdLine: C:\Program Files (x86)\JOSM\josm.exe --l4j-debug WOW64: yes Java min ver: 1.8.0 Java max ver: 64-bit search: SOFTWARE\JavaSoft\Java Runtime Environment... Check: SOFTWARE\JavaSoft\Java Runtime Environment\1.8 Ignore: 1.8 Check: SOFTWARE\JavaSoft\Java Runtime Environment\1.8.0_161 Check launcher: C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe (OK) Match: 1.8.0_161 64-bit search: SOFTWARE\JavaSoft\Java Development Kit... 64-bit search: SOFTWARE\JavaSoft\JRE... 64-bit search: SOFTWARE\JavaSoft\JDK... Runtime used: 1.8.0_161 (64-bit) Heap -Xms: Requested 128 MB / 0%, Available: 10232 MB, Heap size: 128 MB Heap -Xmx: Requested 1024 MB / 0%, Available: 10232 MB, Heap size: 1024 MB Loading: C:\Program Files (x86)\JOSM\josm.l4j.ini Launcher: C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe Launcher args: -Xms128m -Xmx1024m -Djosm.dir.name=JOSMhb -jar "C:\Program Files (x86)\JOSM\josm-tested.jar" Args length: 92/32768 chars Exit code: 0
Note that josm.l4j.ini
is an optional file which contains only the line -Djosm.dir.name=JOSMhb
to set a personal JOSM directory.
Difference between the two log files is in the search for the 32-bit Java variant on your system. So please make the 64-bit Java variant available on your system.
comment:13 by , 7 years ago
Resolution: | worksforme → othersoftware |
---|
Update to the wiki: https://josm.openstreetmap.de/wiki/Download?action=diff&version=134
Do you have any error message?