I upgraded my server recently and had a few questions about some errors and anomalies.
To upgrade I downloaded the new server jar, copied my world, server.properties and ops files over into the new directory, nothing else. Then ran the server. At first I thought everything worked fine. But I keep getting the following errors:
2013-03-22 12:51:46 [iNFO] [ForgeModLoader] Unloading dimension 1
2013-03-22 12:51:46 [iNFO] [ForgeModLoader] Unloading dimension -23
2013-03-22 12:51:49 [sEVERE] [ForgeModLoader] Detected leaking worlds in memory. There are 4 worlds that appear to be persisting. A mod is likely caching the world incorrectly
2013-03-22 12:51:49 [sEVERE] [ForgeModLoader] The world 628356e2 (world) has leaked.
2013-03-22 12:51:49 [sEVERE] [ForgeModLoader] The world 10290f50 (world) has leaked
Also:
[iNFO] [sTDOUT] saving
Shows up every minute or so like clockwork.
The server is running and nobody has complained about performance, but I would like to know how to resolve the leaking errors. Dynmap (1.5) was acting odd last night, a restart fixed that problem. CPU usage is pretty normal as well as ram.
Is the "[iNFO] [sTDOUT] saving" message normal? I didn't see it on the old server.
Is there a way to stop the worlds leaking?
my java -version reads as:
java -version
java version "1.7.0_17"
Java SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot 64-Bit Server VM (build 23.7-b01, mixed mode)
I get the error with java8 as well.
Thanks!
