Scandal 1 Опубликовано 8 октября, 2016 Всем привет помогите, в чем проблема может быть, заходит на сервер исключительно с 3 раза, с 3 раза ввода пароля, а до этого пишет неправильный пароль. Сборка l2core rev14 02:35:53.593 Could not check password: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 287┬а467 milliseconds ago. The last packet sent successfully to the server was 287┬а467 milliseconds ago. is longer than theserver configured value of 'wait_timeout'. You should consider either expiringand/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.at sun.reflect.GeneratedConstructorAccessor7.newInstance(Unknown Source)at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)at java.lang.reflect.Constructor.newInstance(Constructor.java:525)at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851)at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471)at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2734)at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2322)at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)at l2s.database.FiltredPreparedStatement.executeQuery(FiltredPreparedStatement.java:20)at l2s.login.LoginController.loginValid(LoginController.java:423)at l2s.login.LoginController.tryAuthLogin(LoginController.java:217)at l2s.login.network.clientpackets.RequestAuthLogin.runImpl(RequestAuthLogin.java:104)at l2s.login.network.clientpackets.L2LoginClientPacket.run(L2LoginClientPacket.java:33)at l2s.commons.threading.ExecuteWrapper.execute(ExecuteWrapper.java:57)at l2s.commons.threading.FIFORunnableQueue.removeAndExecuteAll(FIFORunnableQueue.java:21)at l2s.commons.threading.FIFOExecutableQueue.run(FIFOExecutableQueue.java:81)at l2s.commons.threading.FIFOExecutableQueue.executeNow(FIFOExecutableQueue.java:58)at l2s.commons.threading.FIFOSimpleExecutableQueue.executeNow(FIFOSimpleExecutableQueue.java:46)at l2s.login.network.L2LoginClient.executePacket(L2LoginClient.java:318)at l2s.login.network.L2LoginClient.executePacket(L2LoginClient.java:25)at l2s.commons.network.SelectorThread.parseClientPacket(SelectorThread.java:518)at l2s.commons.network.SelectorThread.tryReadPacket(SelectorThread.java:435)at l2s.commons.network.SelectorThread.readPacket(SelectorThread.java:380)at l2s.commons.network.SelectorThread.run(SelectorThread.java:220)Caused by: java.net.SocketException: Software caused connection abort: socket write errorat java.net.SocketOutputStream.socketWrite0(Native Method)at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)at java.net.SocketOutputStream.write(SocketOutputStream.java:153)at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832)... 24 more Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты
terege 110 Опубликовано 8 октября, 2016 Всем привет помогите, в чем проблема может быть, заходит на сервер исключительно с 3 раза, с 3 раза ввода пароля, а до этого пишет неправильный пароль. Сборка l2core rev14 02:35:53.593 Could not check password: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet success fully received from the server was 287┬а467 milliseconds ago. The last packet s ent successfully to the server was 287┬а467 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing th e server configured values for client timeouts, or using the Connector/J connect ion property 'autoReconnect=true' to avoid this problem. at sun.reflect.GeneratedConstructorAccessor7.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC onstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1 117) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3851) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2471) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2734) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.ja va:2155) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java: 2322) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Dele gatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Dele gatingPreparedStatement.java:96) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(Dele gatingPreparedStatement.java:96) at l2s.database.FiltredPreparedStatement.executeQuery(FiltredPreparedSta tement.java:20) at l2s.login.LoginController.loginValid(LoginController.java:423) at l2s.login.LoginController.tryAuthLogin(LoginController.java:217) at l2s.login.network.clientpackets.RequestAuthLogin.runImpl(RequestAuthL ogin.java:104) at l2s.login.network.clientpackets.L2LoginClientPacket.run(L2LoginClient Packet.java:33) at l2s.commons.threading.ExecuteWrapper.execute(ExecuteWrapper.java:57) at l2s.commons.threading.FIFORunnableQueue.removeAndExecuteAll(FIFORunna bleQueue.java:21) at l2s.commons.threading.FIFOExecutableQueue.run(FIFOExecutableQueue.jav a:81) at l2s.commons.threading.FIFOExecutableQueue.executeNow(FIFOExecutableQu eue.java:58) at l2s.commons.threading.FIFOSimpleExecutableQueue.executeNow(FIFOSimple ExecutableQueue.java:46) at l2s.login.network.L2LoginClient.executePacket(L2LoginClient.java:318) at l2s.login.network.L2LoginClient.executePacket(L2LoginClient.java:25) at l2s.commons.network.SelectorThread.parseClientPacket(SelectorThread.j ava:518) at l2s.commons.network.SelectorThread.tryReadPacket(SelectorThread.java: 435) at l2s.commons.network.SelectorThread.readPacket(SelectorThread.java:380 ) at l2s.commons.network.SelectorThread.run(SelectorThread.java:220) Caused by: java.net.SocketException: Software caused connection abort: socket wr ite error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) at java.net.SocketOutputStream.write(SocketOutputStream.java:153) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82 ) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3832) ... 24 more Бд доступ неисправен Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты
Scandal 1 Опубликовано 8 октября, 2016 (изменено) как исправить? Изменено 8 октября, 2016 пользователем Scandal Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты
Scandal 1 Опубликовано 8 октября, 2016 есть такой файл и пустой мб он виноват? #---------------------------------------------- # Настрока пула конектов для субд !# Желательно не менять настроек если не знаете для чего они!!!#----------------------------------------------# Настроки для пула с использованием BoneCP http://www.jolbox.com/#----------------------------------------------# Время в минутах, как часто будет делатся проверка конекта к БД.# Default: 240 min, set to 0 to disableidleConnectionTestPeriod# The time (in minutes), for a connection to remain unused before it is closed off. Do not use aggressive values here!# Default: 60 minutes, set to 0 to disableidleMaxAge# In order to reduce lock contention and thus improve performance, each incoming connection request picks off# a connection from a pool that has thread-affinity, i.e. pool[threadId % partition_count].# The higher this number, the better your performance will be for the case when you have plenty of short-lived threads.# Beyond a certain threshold, maintenence of these pools will start to have a negative effect on performance# (and only for the case when connections on a partition start running out).# Default: 3, minimum: 1, recommended: 3-4 (but very app specific)partitionCount# The number of connections to create per partition. Setting this to 5 with 3 partitions means you will have 15 unique# connections to the database. Note that BoneCP will not create all these connections in one go but rather start off with# minConnectionsPerPartition and gradually increase connections as required.# Default: 50maxConnectionsPerPartition# The number of connections to start off with per partition.# Default: 10minConnectionsPerPartition# When the available connections are about to run out, BoneCP will dynamically create new ones in batches.# This property controls how many new connections to create in one go (up to a maximum of maxConnectionsPerPartition).# Note: This is a per partition setting.# Default: 10acquireIncrement# Number of threads to create that will handle releasing a connection. Useful when your application is doing lots# of work on each connection (i.e. perform an SQL query, do lots of non-DB stuff and perform another query),# otherwise will probably slow things down.# Default: 3, Set to 0 to disable.releaseHelperThreads# Instruct the pool to create a helper thread to watch over connection acquires that are never released (or released twice).# When the pool detects such a condition it will log a stack trace of the source of the problem.# This is intended for debugging purposes only - it incurs a large negative performance impact.# Default: falsecloseConnectionWatch# Stops the pool from talking to the database until a first getConnection() request is made.# Default: falselazyInit#----------------------------------------------# Настроки для пула с использованием Apache DBCP http://commons.apache.org/dbcp/#----------------------------------------------#----------------------------------------------# Настроки для пула с использованием C3P0 http://sourceforge.net/projects/c3p0/#---------------------------------------------- Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты
terege 110 Опубликовано 9 октября, 2016 есть такой файл и пустой мб он виноват? #---------------------------------------------- # Настрока пула конектов для субд ! # Желательно не менять настроек если не знаете для чего они!!! #---------------------------------------------- # Настроки для пула с использованием BoneCP http://www.jolbox.com/ #---------------------------------------------- # Время в минутах, как часто будет делатся проверка конекта к БД. # Default: 240 min, set to 0 to disable idleConnectionTestPeriod # The time (in minutes), for a connection to remain unused before it is closed off. Do not use aggressive values here! # Default: 60 minutes, set to 0 to disable idleMaxAge # In order to reduce lock contention and thus improve performance, each incoming connection request picks off # a connection from a pool that has thread-affinity, i.e. pool[threadId % partition_count]. # The higher this number, the better your performance will be for the case when you have plenty of short-lived threads. # Beyond a certain threshold, maintenence of these pools will start to have a negative effect on performance # (and only for the case when connections on a partition start running out). # Default: 3, minimum: 1, recommended: 3-4 (but very app specific) partitionCount # The number of connections to create per partition. Setting this to 5 with 3 partitions means you will have 15 unique # connections to the database. Note that BoneCP will not create all these connections in one go but rather start off with # minConnectionsPerPartition and gradually increase connections as required. # Default: 50 maxConnectionsPerPartition # The number of connections to start off with per partition. # Default: 10 minConnectionsPerPartition # When the available connections are about to run out, BoneCP will dynamically create new ones in batches. # This property controls how many new connections to create in one go (up to a maximum of maxConnectionsPerPartition). # Note: This is a per partition setting. # Default: 10 acquireIncrement # Number of threads to create that will handle releasing a connection. Useful when your application is doing lots # of work on each connection (i.e. perform an SQL query, do lots of non-DB stuff and perform another query), # otherwise will probably slow things down. # Default: 3, Set to 0 to disable. releaseHelperThreads # Instruct the pool to create a helper thread to watch over connection acquires that are never released (or released twice). # When the pool detects such a condition it will log a stack trace of the source of the problem. # This is intended for debugging purposes only - it incurs a large negative performance impact. # Default: false closeConnectionWatch # Stops the pool from talking to the database until a first getConnection() request is made. # Default: false lazyInit #---------------------------------------------- # Настроки для пула с использованием Apache DBCP http://commons.apache.org/dbcp/ #---------------------------------------------- #---------------------------------------------- # Настроки для пула с использованием C3P0 http://sourceforge.net/projects/c3p0/ #---------------------------------------------- как у тебя вообше запустился Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты
devKOFFE 102 Опубликовано 9 октября, 2016 (изменено) За спасибо не берусь ) хоть бы не спалися дядя) модераторы поймают атата сделают Изменено 9 октября, 2016 пользователем Location Поделиться сообщением Ссылка на сообщение Поделиться на другие сайты