[SEVERE] Could not pass event org.bukkit.event.player.PlayerMoveEvent to Ports
javax.persistence.PersistenceException: java.sql.SQLException: database is locked
at com.avaje.ebeaninternal.server.transaction.JdbcTransaction.rollback(JdbcTransaction.java:614)
at com.avaje.ebeaninternal.server.transaction.JdbcTransaction.rollback(JdbcTransaction.java:595)
at com.avaje.ebeaninternal.server.core.BeanRequest.rollbackTransIfRequired(BeanRequest.java:107)
at com.avaje.ebeaninternal.server.core.DefaultServer.findList(DefaultServer.java:1475)
at com.avaje.ebeaninternal.server.querydefn.DefaultOrmQuery.findList(DefaultOrmQuery.java:906)
at com.avaje.ebeaninternal.util.DefaultExpressionList.findList(DefaultExpressionList.java:201)
at net.robinjam.bukkit.ports.PlayerListener.onPlayerMove(PlayerListener.java:34)
at org.bukkit.plugin.java.JavaPluginLoader$7.execute(JavaPluginLoader.java:312)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:57)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:453)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:191)
at net.minecraft.server.Packet10Flying.handle(SourceFile:126)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100)
at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
Caused by: java.sql.SQLException: database is locked
at org.sqlite.DB.throwex(DB.java:370)
at org.sqlite.DB.exec(DB.java:76)
at org.sqlite.Conn.rollback(Conn.java:351)
at com.avaje.ebeaninternal.server.lib.sql.PooledConnection.rollback(PooledConnection.java:752)
at com.avaje.ebeaninternal.server.transaction.JdbcTransaction.rollback(JdbcTransaction.java:607)
... 17 more

Yes, I'm aware of this problem :(

SQL is a bit of a pain to work with, so I'm switching to YAML-based storage in version 0.2 (see issue #15). This should fix the issue.