Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Player home lost #696

Closed
CodeZhangBorui opened this issue Oct 3, 2024 · 1 comment
Closed

Player home lost #696

CodeZhangBorui opened this issue Oct 3, 2024 · 1 comment
Labels
resolution: invalid This issue is invalid

Comments

@CodeZhangBorui
Copy link

Reopen issue of #658

Problem still occurs here, with plugin fakeplayer.

Version: PaperMC 1.20.1 & HuskHomes-Paper-4.7.1-ab7237f.

[12:31:29 INFO]: LSamoyedy lost connection: Disconnected
[12:31:29 INFO]: - LSamoyedy left the server
[12:41:05 INFO]: LSamoyedy_Bot_1 lost connection: [fakeplayer] Creator offline
[12:41:05 INFO]: - LSamoyedy_Bot_1 left the server
[12:41:05 INFO]: LSamoyedy_Bot_2 lost connection: [fakeplayer] Creator offline
[12:41:05 INFO]: - LSamoyedy_Bot_2 left the server
[12:41:05 INFO]: [fakeplayer] LSamoyedy is offline more than 12000 ticks, removing 2 fake players
[12:41:05 ERROR]: [HuskHomes] Failed to set the offline position of LSamoyedy_Bot_2
org.sqlite.SQLiteException: [SQLITE_BUSY] The database file is locked (cannot commit transaction - SQL statements in progress)
        at org.sqlite.core.DB.newSQLException(DB.java:1179) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.newSQLException(DB.java:1190) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.throwex(DB.java:1150) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.ensureAutocommit(DB.java:1255) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.lambda$ensureAutoCommit$2(DB.java:1226) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.SafeStmtPtr.safeRunConsume(SafeStmtPtr.java:142) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.lambda$ensureAutoCommit$3(DB.java:1225) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.SafeStmtPtr.safeRunConsume(SafeStmtPtr.java:142) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.ensureAutoCommit(DB.java:1223) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.execute(DB.java:977) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.core.DB.executeUpdate(DB.java:1054) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.jdbc3.JDBC3PreparedStatement.lambda$executeLargeUpdate$2(JDBC3PreparedStatement.java:119) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.jdbc3.JDBC3Statement.withConnectionTimeout(JDBC3Statement.java:454) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.jdbc3.JDBC3PreparedStatement.executeLargeUpdate(JDBC3PreparedStatement.java:118) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at org.sqlite.jdbc3.JDBC3PreparedStatement.executeUpdate(JDBC3PreparedStatement.java:100) ~[sqlite-jdbc-3.42.0.0.jar:?]
        at net.william278.huskhomes.database.SqLiteDatabase.updatePosition(SqLiteDatabase.java:178) ~[HuskHomes-Paper-4.7.1-ab7237f.jar:?]
        at net.william278.huskhomes.database.SqLiteDatabase.setOfflinePosition(SqLiteDatabase.java:894) ~[HuskHomes-Paper-4.7.1-ab7237f.jar:?]
        at net.william278.huskhomes.listener.EventListener.lambda$handlePlayerLeave$7(EventListener.java:107) ~[HuskHomes-Paper-4.7.1-ab7237f.jar:?]
        at org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftTask.run(CraftTask.java:101) ~[purpur-1.20.1.jar:git-Purpur-2062]
        at org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57) ~[purpur-1.20.1.jar:git-Purpur-2062]
        at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[purpur-1.20.1.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
        at java.lang.Thread.run(Thread.java:833) ~[?:?]
@WiIIiam278
Copy link
Owner

Duplicate of #688, but will copy your report over there. Thanks.

@WiIIiam278 WiIIiam278 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 5, 2024
@WiIIiam278 WiIIiam278 added the resolution: invalid This issue is invalid label Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: invalid This issue is invalid
Projects
None yet
Development

No branches or pull requests

2 participants