Can't start new server (0.9.2)

Psychos · Jan 22nd 2018

Fresh installlation, Windows 7 pro 64bis / 16Gb memory / latest Java 64bits JDK (dafault installation)

Log here :

Code

Rising World - 0.9.2 - Dedicated Server
Windows 7 6.1  Java 9.0.4 (amd64)  Memory: 1073 MB
2018/01/22   03:44 PM
____________________________________________________


Start context...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.jme3.util.ReflectionAllocator (file:/C:/Steam/steamapps/common/RisingWorldDedicatedServer/lib/Jme-Core.jar) to methodsun.nio.ch.DirectBuffer.cleaner()
WARNING: Please consider reporting this to the maintainers of com.jme3.util.ReflectionAllocator
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Items initialized!
Plants initialized!
NPCs initialized!
Initialize Static Classes...
Constructions initialized!
Projectile-Definitions initialized!
Weapon-Definitions initialized!
Objects initialized!
Clothing initialized!
Picking initialized!
Food-Definitions initialized!
Crafting-Definitions initialized!
Record-Definitions initialized!
Initializing world (MySQL)
CREATE WORLD BlackMoonWorld (Survival)
WORLDINFOS   seed: 6545675421  type: Normal  caves: true  vegetations: true  ore
amount: 3  disablednpc: [[]]  disableddungeons: [[]]  disabledwatersources: [[]]


2018/01/22   03:44 PM   server.Main
SEVERE: Rising World - 0.9.2 - Dedicated Server
Windows 7 6.1  Java 9.0.4 (amd64)  Memory: 1073 MB
2018/01/22   03:44 PM
____________________________________________________
RW SERVER: Fatal error occurred!
java.lang.ExceptionInInitializerError: Biomemaps are not initialized!
at commons.world.j.a(SourceFile:161)
at server.e.b(SourceFile:1115)
at server.e.a(SourceFile:1077)
at server.Main.d(SourceFile:441)
at server.Main.initApplication(SourceFile:281)
at commons.JIWApplication.initialize(SourceFile:236)
at com.jme3.system.NullContext.initInThread(NullContext.java:87)
at com.jme3.system.NullContext.run(NullContext.java:130)
at java.base/java.lang.Thread.run(Unknown Source)

Display More

Sneaky_Koala · Jan 23rd 2018

Good that you mention this, because I'm having the same problem myself (Slackware). I thought I was stuffing something up - and very well may be - but seeing it happen to someone else on a different OS means it might not be me after all heh.

bash-4.4$ ./linux_startscript.sh start
Sukeyland-arisen is successfully started
bash-4.4$ ./linux_startscript.sh status
Sukeyland-arisen is not running

----

With pretty much the exact error message as you:

Code

bash-4.4$ java -jar server.jar


WARNING: YOUR SERVER VERSION IS OUTDATED (0.9.1.5 vs. 0.9.2.1)


Rising World - 0.9.1.5 - Dedicated Server
Linux 4.14.11  Java 9.0.1 (amd64)  Memory: 2076 MB
2018/01/23   09:55 AM
____________________________________________________


Start context...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.jme3.util.ReflectionAllocator (file:/home/trav/RWserver/server_0.9.1.5/lib/Jme-Core.jar) to method sun.nio.ch.DirectBuffer.cleaner()                                                                                                  
WARNING: Please consider reporting this to the maintainers of com.jme3.util.ReflectionAllocator                                         
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations                                   
WARNING: All illegal access operations will be denied in a future release                                                               
Items initialized!                                                                                                                      
Plants initialized!                                                                                                                     
NPCs initialized!
Initialize Static Classes...
Constructions initialized!
Projectile-Definitions initialized!
Weapon-Definitions initialized!
Objects initialized!
Clothing initialized!
Picking initialized!
Food-Definitions initialized!
Crafting-Definitions initialized!
Record-Definitions initialized!
Initializing world (sqlite)
CREATE WORLD New World (Survival)
WORLDINFOS   seed: 1516672515159  type: Normal  caves: true  vegetations: true  oreamount: 3  disablednpc: [[]]  disableddungeons: [[]]  disabledwatersources: [[]]
2018/01/23   09:55 AM   server.Main
SEVERE: Rising World - 0.9.1.5 - Dedicated Server
Linux 4.14.11  Java 9.0.1 (amd64)  Memory: 2076 MB
2018/01/23   09:55 AM
____________________________________________________
RW SERVER: Fatal error occurred! 
java.lang.ExceptionInInitializerError: Biomemaps are not initialized!
        at commons.world.j.a(SourceFile:161)
        at server.e.b(SourceFile:1115)
        at server.e.a(SourceFile:1085)
        at server.Main.d(SourceFile:441)
        at server.Main.initApplication(SourceFile:281)
        at commons.JIWApplication.initialize(SourceFile:236)
        at com.jme3.system.NullContext.initInThread(NullContext.java:87)
        at com.jme3.system.NullContext.run(NullContext.java:130)
        at java.base/java.lang.Thread.run(Unknown Source)

Display More

red51 · Jan 23rd 2018

It looks like the issue is caused by Java 9... according to the log, certain methods of the underlying engine are not supported anymore by Java 9.
Actually the game and the server haven't been tested with Java 9 yet. I'd recommend to rollback to Java 8 (unless you run software which requires at least Java 9, there should be nothing to worry about by using Java 9) and see if the issue still persists

Psychos · Jan 23rd 2018

Quote from red51

It looks like the issue is caused by Java 9... according to the log, certain methods of the underlying engine are not supported anymore by Java 9.
Actually the game and the server haven't been tested with Java 9 yet. I'd recommend to rollback to Java 8 (unless you run software which requires at least Java 9, there should be nothing to worry about by using Java and see if the issue still persists

It's the right solution, it works now. Thank you.

red51 · Jan 23rd 2018

Glad to hear it works now, and also good to know that the server is apparently incompatible with Java 9

Participate now!