Sam Corl
Assigned
Reported
Comments
Ok, tested with OpenJDK 1.7.0 - and it works! thank you so much!!
Ok, thanks. I'll update and test.
this is a basic, generally unmodified CentOS dedicated server. more details are:
Dell T110 Xeon E3-1220v2 3.1GHz 4 Cores
Hard Drive: Dell 1TB 7.2K RPM SATA 3Gbps
CentOS 6.3 - 64 Bit
16GB RAM
1GB network uplink
hosted in Arizona, USA at Codero
I have run public servers with 1.6.2, 1.6.4 on this same machine (vanilla at first, then bukkit), same Java, no crashes. I have some players that I know built giant spawners on those servers, running on this machine, and we've never had this problem.
When I visited the player's base who was crashing our server, the cows were just glitching like crazy in a 1x1 box. As soon as I "cleared" the mobs with some splash harming, server RAM returned to normal. Like immediately.
At the moment, I've asked my players to keep the mobs in "free range" enclosures - with a limited number and room to find a path to walk - to ensure the health and safety of the server and all it's inhabitants. All players are now able to use the server, and it has not crashed since.
If you need anything else, please let me know.
Oh, the server address is minecraft1-7.com
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.14) (rhel-1.65.1.11.14.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
edited the java version in env. on first try, reported the version from my workstation accidentally, sorry.
I used a stone button to prevent users from accessing my iron door, but....
I thought that since wood buttons are not activated by being pressed by users under spawn protect, they should also be blocked from being shot by player arrows. Seems like it should behave predictably for any player interaction. Thanks for your attention, and sorry to bother with a non-bug report.