Greetings all. Long time player and forum reader, first time poster.
I'm having an odd bit of server troubles and was hoping that the collective wisdom here could help me figure out where I'm in error. I've looked around here a bit, but for this task my google-fu seems weak.
The difficulties I'm having are connecting to my MC server when running Bukkit through 64-bit Java. Everything works fine with 32-bit Java.
My MC server specs:
Windows 7 Enterprise Edition 64-bit SP1
Intel 3.00Ghz Core2 Duo
6GB RAM
160GB HD
10GB Page file
Firewall set to allow exceptions across port 25565
Minecraft server 1.6.6
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
@ECHO OFF
SET BINDIR=%~dp0
CD /D "%BINDIR%"
"%ProgramFiles(x86)%\Java\jre6\bin\java.exe" -Xincgc -Xmx1536m -Xms1536m -jar craftbukkit-0.0.1-SNAPSHOT.jar
PAUSE
64-bit Java batch file:
@ECHO OFF
SET BINDIR=%~dp0
CD /D "%BINDIR%"
"%ProgramFiles%\Java\jre6\bin\java.exe" -Xincgc -Xmx3072m -Xms3072m -jar craftbukkit-0.0.1-SNAPSHOT.jar
PAUSE
The server appears to launch fine and reports no errors with either batch file. The only difference is between the allocated memory for java and the specific java environment being called (32 vs 64 bit).
The reason behind the desire to run the 64-bit Java over the 32-bit version is that the 32-bit Java environment is limited to 1.5GB of memory, while the 64-bit Java is capable of utilizing a higher memory range in excess of 1.5GB (I'd like to use around 3GB).
Server output log for 32-bit batch executable:
148 recipes
16 achievements
23:06:28 [INFO] Starting minecraft server version Beta 1.6.6
23:06:28 [INFO] Loading properties
23:06:28 [INFO] Starting Minecraft server on *:25565
23:06:28 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-766-
g3fc0460-b818jnks (MC: 1.6.6)
23:06:28 [INFO] Preparing level "world"
23:06:28 [INFO] Preparing start region for level 0
23:06:28 [INFO] Preparing start region for level 1
23:06:29 [INFO] Preparing spawn area: 32%
23:06:29 [INFO] Loaded Essentials build 2.2.22 by Zenexer, ementalo, Aelux, Bret
tflan, KimKandor, snowleo, ceulemans and Xeology
23:06:29 [INFO] Loaded EssentialsChat build 2.2.22 by Zenexer, ementalo, Aelux,
Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:06:29 [INFO] Loaded EssentialsGeoIP build 2.2.22 by Zenexer, ementalo, Aelux,
Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:06:29 [INFO] This product includes GeoLite data created by MaxMind, available
from http://www.maxmind.com/.
23:06:29 [INFO] GroupManager - INFO - Scheduled Data Saving is set for every 10
minutes!
23:06:29 [INFO] GroupManager version 1.0(alpha-5) is enabled!
23:06:29 [INFO] Loaded EssentialsProtect build 2.2.22 by Zenexer, ementalo, Aelu
x, Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:06:29 [INFO] Loaded EssentialsSpawn build 2.2.22 by Zenexer, ementalo, Aelux,
Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:06:29 [INFO] [Runecraft] Rune blacklist with 0 runes loaded.
23:06:29 [INFO] [Runecraft] World 'world': id changed to 0
23:06:30 [INFO] [Runecraft] Runecraft 2.7 initialized.
23:06:30 [INFO] [Runecraft] World 'world_nether': id changed to 1
23:06:30 [INFO] Runecraft plugin version 0.4 is enabled!
23:06:30 [INFO] Fake Permissions version 2.7.2 is enabled!
23:06:30 [INFO] Done (0.180s)! For help, type "help" or "?"
>mem
23:07:47 [INFO] Maximum memory: 1,532 MB
23:07:47 [INFO] Minimum memory: 1,409 MB
23:07:47 [INFO] World "world": 625chunks,92entities
23:07:47 [INFO] Nether "world_nether": 625chunks,0entities
Server output log for 64-bit batch executable:
148 recipes
16 achievements
23:08:54 [INFO] Starting minecraft server version Beta 1.6.6
23:08:54 [INFO] Loading properties
23:08:54 [INFO] Starting Minecraft server on *:25565
23:08:54 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-766-
g3fc0460-b818jnks (MC: 1.6.6)
23:08:54 [INFO] Preparing level "world"
23:08:54 [INFO] Preparing start region for level 0
23:08:55 [INFO] Preparing start region for level 1
23:08:55 [INFO] Preparing spawn area: 60%
23:08:56 [INFO] Loaded Essentials build 2.2.22 by Zenexer, ementalo, Aelux, Bret
tflan, KimKandor, snowleo, ceulemans and Xeology
23:08:56 [INFO] Loaded EssentialsChat build 2.2.22 by Zenexer, ementalo, Aelux,
Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:08:56 [INFO] Loaded EssentialsGeoIP build 2.2.22 by Zenexer, ementalo, Aelux,
Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:08:56 [INFO] This product includes GeoLite data created by MaxMind, available
from http://www.maxmind.com/.
23:08:56 [INFO] GroupManager - INFO - Scheduled Data Saving is set for every 10
minutes!
23:08:56 [INFO] GroupManager version 1.0(alpha-5) is enabled!
23:08:56 [INFO] Loaded EssentialsProtect build 2.2.22 by Zenexer, ementalo, Aelu
x, Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:08:56 [INFO] Loaded EssentialsSpawn build 2.2.22 by Zenexer, ementalo, Aelux,
Brettflan, KimKandor, snowleo, ceulemans and Xeology
23:08:56 [INFO] [Runecraft] Rune blacklist with 0 runes loaded.
23:08:56 [INFO] [Runecraft] World 'world': id changed to 0
23:08:56 [INFO] [Runecraft] Runecraft 2.7 initialized.
23:08:56 [INFO] [Runecraft] World 'world_nether': id changed to 1
23:08:56 [INFO] Runecraft plugin version 0.4 is enabled!
23:08:56 [INFO] Fake Permissions version 2.7.2 is enabled!
23:08:56 [INFO] Done (0.200s)! For help, type "help" or "?"
>mem
23:09:07 [INFO] Maximum memory: 3,067 MB
23:09:07 [INFO] Minimum memory: 2,940 MB
23:09:07 [INFO] World "world": 625chunks,91entities
23:09:07 [INFO] Nether "world_nether": 625chunks,0entities
I'll be happy to provide you with any other information that might lead to an answer. I figure at this point, I'm just over looking something simple. Thank you in advance, I appreciate your efforts.
However, it does look like your batch files are reversed in that you appear to be allocating additional RAM for 32bit and are staying with the 1024MB for the 64bit or is it just too damn late in the night for me?
Rollback Post to RevisionRollBack
"Never try to teach a pig to sing. It wastes your time and annoys the pig." Lazarus Long
Updated server and bukkit versions; bumping for hopeful solution.
Added Mem report to server log.
I haven't found any indication that the standard Minecraft client can't connect to a 64-bit java run server. All information I've come across so far says that a 32-bit java application should work fine within a 64-bit java environment; similar to running 32-bit programs in a 64-bit operating system.
Updated a lot of information over on the Bukkit forum (HERE).
Essentially:
-Uninstalled all Java versions and only reinstalled the 64-bit environment.
-Removed all plugins and attempted to run the core Bukkit Jar initiated server
-Created a new directory for the server, utilizing only the Bukkit Jar and the RUN batch file
-Various locations and systems tested.
All tests and procedures result in same issue: Client systems unable to connect to server.
So far we have a solution - It appears the Windows firewall was blocking the traffic to the server when run in a 64-bit environment. Disabling the firewall allows clients to connect to the server.
However, using the 32-bit environment and having the firewall turned on - everything works fine.
The firewall is configured to allow all traffic across port 25565, with no specific association to a service or application. It shouldn't matter if I'm running 32-bit or 64-bit java.
Now I need to figure out why the firewall is oppressing my 64-bit server.
I'm not sure of the specifics. That's just the Batch file commands and settings listed in the instructions from Bukkit (HERE). I just used them directly as configured.
I'm not sure of the specifics. That's just the Batch file commands and settings listed in the instructions from Bukkit (HERE). I just used them directly as configured.
I'll give it a try in a moment - I have to run out of the office for a bit.
Though, I seem to be able to connect to the 64-bit server now with the firewall disabled. I'm now trying to figure out why the firewall is only blocking the 64-bit java environment and the 32-bit works perfectly fine with the currently configured exception. If I need to add an additional port exception because of the 64-bit environment that won't be an issue.
I'll give it a try in a moment - I have to run out of the office for a bit.
Though, I seem to be able to connect to the 64-bit server now with the firewall disabled. I'm now trying to figure out why the firewall is only blocking the 64-bit java environment and the 32-bit works perfectly fine with the currently configured exception. If I need to add an additional port exception because of the 64-bit environment that won't be an issue.
Instead of running what I just suggested, try to do "java -version" in CMD. If it reports back java build something 64-bit then try this (the other one was based upon the server JVM):
Instead of running what I just suggested, try to do "java -version" in CMD. If it reports back java build something 64-bit then try this (the other one was based upon the server JVM):
Java -version reports:
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
Using the given batch file, clients are still unable to connect with firewall enabled. Server appears to run fine.
Connection appears to work fine with firewall disabled, as similarly indicated with previous batch file.
Apparently, when Java 32-bit and 64-bit were installed, they both made their own firewall exceptions (for a total of 4 exceptions). However, both exceptions were pointing to the 32-bit Program Files(x86) location of Java. Why the 64-bit version didn't create it's own proper pathing, I haven't a clue.
When they were uninstalled, neither of them were removed.
Now that only the 64-bit Java environment is installed, I re-examined the Java firewall exceptions and manually pointed all exceptions to the directory of the 64-bit Java.
So either the Windows firewall was screwing me over, or someone at Java doesn't have the 64-bit firewall exception path set correctly by default.
---
Feel free to cross-reference with the Bukkit forum thread (HERE) should you experience any similar issues. The answers might be found within.
Apparently, when Java 32-bit and 64-bit were installed, they both made their own firewall exceptions (for a total of 4 exceptions). However, both exceptions were pointing to the 32-bit Program Files(x86) location of Java. Why the 64-bit version didn't create it's own proper pathing, I haven't a clue.
When they were uninstalled, neither of them were removed.
Now that only the 64-bit Java environment is installed, I re-examined the Java firewall exceptions and manually pointed all exceptions to the directory of the 64-bit Java.
So either the Windows firewall was screwing me over, or someone at Java doesn't have the 64-bit firewall exception path set correctly by default.
---
Feel free to cross-reference with the Bukkit forum thread (HERE) should you experience any similar issues. The answers might be found within.
Could you tell me how to do this? I have been having this problem as well. Also, my Cmd Prompht: "java -version" doesnt work
I'm having an odd bit of server troubles and was hoping that the collective wisdom here could help me figure out where I'm in error. I've looked around here a bit, but for this task my google-fu seems weak.
The difficulties I'm having are connecting to my MC server when running Bukkit through 64-bit Java. Everything works fine with 32-bit Java.
My MC server specs:
Windows 7 Enterprise Edition 64-bit SP1
Intel 3.00Ghz Core2 Duo
6GB RAM
160GB HD
10GB Page file
Firewall set to allow exceptions across port 25565
Minecraft server 1.6.6
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
Bukkit version: git-Bukkit-0.0.0-766-g3fc0460-b818jnks (MC: 1.6.6)
Essentials version: 2.2.22
32-bit Java batch file:
64-bit Java batch file:
The server appears to launch fine and reports no errors with either batch file. The only difference is between the allocated memory for java and the specific java environment being called (32 vs 64 bit).
The reason behind the desire to run the 64-bit Java over the 32-bit version is that the 32-bit Java environment is limited to 1.5GB of memory, while the 64-bit Java is capable of utilizing a higher memory range in excess of 1.5GB (I'd like to use around 3GB).
Server output log for 32-bit batch executable:
Server output log for 64-bit batch executable:
I'll be happy to provide you with any other information that might lead to an answer. I figure at this point, I'm just over looking something simple. Thank you in advance, I appreciate your efforts.
Short version for TL;DR people:
32-bit server: client connects fine
64-bit server: client unable to connect
32bit: [Lnet.minecraft.server.Statistic;@6e293a
64bit: [Lnet.minecraft.server.Statistic;@5b6df84b
However, it does look like your batch files are reversed in that you appear to be allocating additional RAM for 32bit and are staying with the 1024MB for the 64bit or is it just too damn late in the night for me?
While the 64-bit batch file calls for 3GB of memory:
Added Mem report to server log.
I haven't found any indication that the standard Minecraft client can't connect to a 64-bit java run server. All information I've come across so far says that a 32-bit java application should work fine within a 64-bit java environment; similar to running 32-bit programs in a 64-bit operating system.
Essentially:
-Uninstalled all Java versions and only reinstalled the 64-bit environment.
-Removed all plugins and attempted to run the core Bukkit Jar initiated server
-Created a new directory for the server, utilizing only the Bukkit Jar and the RUN batch file
-Various locations and systems tested.
All tests and procedures result in same issue: Client systems unable to connect to server.
However, using the 32-bit environment and having the firewall turned on - everything works fine.
The firewall is configured to allow all traffic across port 25565, with no specific association to a service or application. It shouldn't matter if I'm running 32-bit or 64-bit java.
Now I need to figure out why the firewall is oppressing my 64-bit server.
I'm not sure of the specifics. That's just the Batch file commands and settings listed in the instructions from Bukkit (HERE). I just used them directly as configured.
Try this:
I'll give it a try in a moment - I have to run out of the office for a bit.
Though, I seem to be able to connect to the 64-bit server now with the firewall disabled. I'm now trying to figure out why the firewall is only blocking the 64-bit java environment and the 32-bit works perfectly fine with the currently configured exception. If I need to add an additional port exception because of the 64-bit environment that won't be an issue.
Instead of running what I just suggested, try to do "java -version" in CMD. If it reports back java build something 64-bit then try this (the other one was based upon the server JVM):
Java -version reports:
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)
Using the given batch file, clients are still unable to connect with firewall enabled. Server appears to run fine.
Connection appears to work fine with firewall disabled, as similarly indicated with previous batch file.
Apparently, when Java 32-bit and 64-bit were installed, they both made their own firewall exceptions (for a total of 4 exceptions). However, both exceptions were pointing to the 32-bit Program Files(x86) location of Java. Why the 64-bit version didn't create it's own proper pathing, I haven't a clue.
When they were uninstalled, neither of them were removed.
Now that only the 64-bit Java environment is installed, I re-examined the Java firewall exceptions and manually pointed all exceptions to the directory of the 64-bit Java.
So either the Windows firewall was screwing me over, or someone at Java doesn't have the 64-bit firewall exception path set correctly by default.
---
Feel free to cross-reference with the Bukkit forum thread (HERE) should you experience any similar issues. The answers might be found within.
Could you tell me how to do this? I have been having this problem as well. Also, my Cmd Prompht: "java -version" doesnt work
Which portion were you having trouble with?
the Java -version command isn't run from the command prompt but from the Java console if I recall properly.
Did you try to run cmd as administrator? When you type cmd right click and select run as admin.
Java -version worked for me tho.