用mysql没有问题,就是一直控制台出黄子提示,大佬们有没有办法让这个不显示
[15:29:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@71ca1d11 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:30:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@44448f1d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:31:28 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@7ba2e804 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:31:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@6b6c12da (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:32:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@3fcae158 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:34:28 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@582a11d1 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:34:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@70a2779d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:35:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@3d973b1d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:29:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@71ca1d11 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:30:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@44448f1d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:31:28 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@7ba2e804 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:31:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@6b6c12da (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:32:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@3fcae158 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:34:28 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@582a11d1 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:34:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@70a2779d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[15:35:58 WARN]: [me.lucko.luckperms.lib.hikari.pool.PoolBase] luckperms-hikari - Failed to validate connection me.lucko.luckperms.lib.mysql.cj.jdbc.ConnectionImpl@3d973b1d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
ConsoleSpamFix  可以尝试用这个插件进行屏蔽
检查mysql的地址格式是否正确
address: 127.0.0.1
database: luckperms
username: root
password: 123456
address: 127.0.0.1
database: luckperms
username: root
password: 123456
Possibly consider using a shorter maxLifetime value.
这一行就是提示,这是hikari连接池的一个参数,请在lp修改 maxLifetime 为更小的值
如果lp中没有可供修改的地方,就需要退而求其次修改mysql中对应的参数
如果不是实在没有办法,切忌一上来就使用spamfix等屏蔽报错的插件,典型的头痛医嘴,只不过是掩盖了问题,增加了风险,对实际技能成长毫无帮助
这一行就是提示,这是hikari连接池的一个参数,请在lp修改 maxLifetime 为更小的值
如果lp中没有可供修改的地方,就需要退而求其次修改mysql中对应的参数
如果不是实在没有办法,切忌一上来就使用spamfix等屏蔽报错的插件,典型的头痛医嘴,只不过是掩盖了问题,增加了风险,对实际技能成长毫无帮助
金瓯 发表于 2022-4-18 18:28
Possibly consider using a shorter maxLifetime value.
这一行就是提示,这是hikari连接池的一个参数,请 ...
我先试试,这个提示是一直再刷,隔几分钟刷好多
-龙痕 发表于 2022-4-18 18:06
检查mysql的地址格式是否正确
address: 127.0.0.1
database: luckperms
格式完全没有问题,服务器内正常使用,权限组也有效果,mysql格式不对服务器就没法加载
@大熊 发表于 2022-4-18 19:38
格式完全没有问题,服务器内正常使用,权限组也有效果,mysql格式不对服务器就没法加载 ...
刚刚搜了一下 应该是插件的maxlifetime和mysql的wait_timeout两个参数之间需要有合理的比例关系
这是我搜到的,你也可以百度看看
https://blog.csdn.net/Just_Do_It_123/article/details/107862085