#18 cant connect, server crashed

[Simon]

again the server crashed while playing.
(this time i was using a mysql database)
Now i can't login and servers last messages are:

$ ./DarkWorld.sh
10:52:01.461 EVENT Starting Jetty/4.2.9
10:52:01.965 EVENT Started
WebApplicationContext[/,DarkWorld Web Administrator]
10:52:02.140 EVENT Started SocketListener on
0.0.0.0:9042
10:52:02.141 EVENT Started
org.mortbay.jetty.Server@c8f6f8
04.11.2006 10:55:37 darkWorld.admin.GameImpl create
INFO: Loaded data definitions DB in 0.05
04.11.2006 10:55:38 darkWorld.admin.GameImpl create
INFO: Cleared databases in 1.72
04.11.2006 10:55:39 darkWorld.admin.GameImpl
loadInitialData
INFO: Saved administrative data in 0.204
04.11.2006 10:55:44 darkWorld.admin.GameImpl
loadInitialData
INFO: Generated universe in 4.984
04.11.2006 10:55:44 darkWorld.admin.GameImpl create
INFO: Started simulation and server in 0.137
04.11.2006 10:55:44 darkWorld.admin.GameImpl create
INFO: Total startup time : 7.236
Exception in thread "sim" java.sql.SQLException: Can't
call rollback when autocommit=true
at
com.mysql.jdbc.Connection.rollback(Connection.java:4711)
at darkWorld.db.DB.abort(DB.java:490)
at
darkWorld.sim.SimImpl$Worker.run(SimImpl.java:147)
darkWorld.db.DBException
at darkWorld.db.DB.abort(DB.java:492)
at
darkWorld.sim.SimImpl$Worker.run(SimImpl.java:147)

[Simon]

Logged In: YES
user_id=1121598

and the attempt to reload the game fails with:

Browser:
HTTP ERROR: 500 Internal Server Error
RequestURI=/gameDispatcher

Server:
$ ./DarkWorld.sh
00:11:20.557 EVENT Starting Jetty/4.2.9
00:11:21.135 EVENT Started WebApplicationContext[/,DarkWorld Web Administrator]
00:11:21.405 EVENT Started SocketListener on 0.0.0.0:9042
00:11:21.406 EVENT Started org.mortbay.jetty.Server@c8f6f8
06.11.2006 00:11:45 darkWorld.admin.GameImpl resume
INFO: Initialized game simulation DB in 0.0
00:12:02.245 WARN!! Exception for /gameDispatcher
java.lang.NullPointerException
at darkWorld.sim.data.TemporalMapData.getLinkInfoIterator(TemporalMapData.java:183)
at darkWorld.sim.TemporalMap.initializeFromPersistentData(TemporalMap.java:540)
at darkWorld.sim.data.PersistenceManager.finishRestoration(PersistenceManager.java:143)
at darkWorld.sim.data.SimDataFacade.restore(SimDataFacade.java:116)
at darkWorld.sim.SimImpl.loadData(SimImpl.java:306)
at darkWorld.admin.GameImpl.resume(GameImpl.java:314)
at darkWorld.webAdmin.GameServlet.service(GameServlet.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:507)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:863)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)

[Keith Turner]

Logged In: YES
user_id=28123

In response to your initial comment, the last message
indicates the simulation thread crashed... can you look in
the logs dir of your server and see any Exceptions in the
log dir?

In response to your second comment related to reloading,
that is a seperate bug which I fixed and checked into CVS.

[Simon]

game.log file with exception

[Simon]

Logged In: YES
user_id=1121598

this time i found a log file with an exception (see attached file)

[Keith Turner]

Logged In: YES
user_id=28123

The errors in the log you attached are related to reloading a game and do not indicate why a game crahsed. However
this will be more errors to look into in relation to load failures.