KOltin 1 Опубликовано 4 ноября, 2019 Спойлер Mon Nov 04 20:26:46 MSK 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. [INFO 20:29:45]: Olympiad System: Data updated successfully. [WARN 20:29:56]: could not restore inventory: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 189,473 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3562) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3462) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3903) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2530) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2683) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2486) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1858) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1966) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) at ru.catssoftware.gameserver.model.itemcontainer.PcInventory.restoreVisibleInventory(PcInventory.java:594) at ru.catssoftware.gameserver.model.CharSelectInfoPackage.<init>(CharSelectInfoPackage.java:21) at ru.catssoftware.gameserver.network.serverpackets.CharSelectionInfo.restoreChar(CharSelectionInfo.java:295) at ru.catssoftware.gameserver.network.serverpackets.CharSelectionInfo.loadCharacterSelectInfo(CharSelectionInfo.java:204) at ru.catssoftware.gameserver.network.serverpackets.CharSelectionInfo.<init>(CharSelectionInfo.java:32) at ru.catssoftware.gameserver.LoginServerThread.acceptPlayer(LoginServerThread.java:369) at ru.catssoftware.gameserver.LoginServerThread.run(LoginServerThread.java:303) Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost. at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:3014) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:3472) ... 16 more java.sql.SQLException: Already closed. at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:114) at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:191) at ru.catssoftware.gameserver.model.itemcontainer.PcInventory.restoreVisibleInventory(PcInventory.java:623) at ru.catssoftware.gameserver.model.CharSelectInfoPackage.<init>(CharSelectInfoPackage.java:21) at ru.catssoftware.gameserver.network.serverpackets.CharSelectionInfo.restoreChar(CharSelectionInfo.java:295) at ru.catssoftware.gameserver.network.serverpackets.CharSelectionInfo.loadCharacterSelectInfo(CharSelectionInfo.java:204) at ru.catssoftware.gameserver.network.serverpackets.CharSelectionInfo.<init>(CharSelectionInfo.java:32) at ru.catssoftware.gameserver.LoginServerThread.acceptPlayer(LoginServerThread.java:369) at ru.catssoftware.gameserver.LoginServerThread.run(LoginServerThread.java:303) Mon Nov 04 20:29:56 MSK 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Mon Nov 04 20:29:57 MSK 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Mon Nov 04 20:35:02 MSK 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Установили лимит одновременных соединений - 400. Также сократили время ожидания, после которого соединение будет закрываться автоматически, если соединение неактивно. Сейчас это значение составляет 180 секунд. Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты