View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005485 | Spring engine | AI | public | 2017-02-20 20:25 | 2017-04-08 14:40 |
| Reporter | DeinFreund | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 103.0 +git | ||||
| Summary | 0005485: Spring tries to use wrong java version (32/64 bit) | ||||
| Description | Spring seems to use the first Java version it finds. If Java_Home contains a 64 bit version but Spring is running in 32 bit, it will fail to initialize the AI. If it checked the version for 32/64 bit and moved on, it would find the 32 bit version in registry (in my case). There are other programs using JAVA_HOME than Spring, so it should be possible to have it set to some "wrong" version without breaking it. | ||||
| Steps To Reproduce | Set Java_Home to 64 bit java Run 32 bit Spring with Java AI AI disintegrates | ||||
| Tags | No tags attached. | ||||
| Checked infolog.txt for Errors | |||||
| related to | 0005486 | new | Lua method to check for installed Java |
|
|
IMO spring should create a list of all available jvms and then try until it can sucessfully load jvm.dll. the easy way would be to add SPRING_JAVA_HOME and prefer this env var over JAVA_HOME when available. https://github.com/spring/spring/blob/develop/AI/Interfaces/Java/src/main/native/JvmLocater_common.c#L108 |
|
|
https://github.com/spring/spring/blob/develop/AI/Interfaces/Java/src/main/native/JavaBridge.c#L932 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-20 20:25 | DeinFreund | New Issue | |
| 2017-03-11 10:50 | abma | Severity | major => feature |
| 2017-03-11 10:50 | abma | Note Added: 0017382 | |
| 2017-03-11 10:54 | abma | Note Added: 0017383 | |
| 2017-03-11 11:00 | abma | Note Edited: 0017382 | |
| 2017-03-11 11:03 | abma | Note Edited: 0017382 | |
| 2017-04-08 14:40 | abma | Relationship added | related to 0005486 |
