页面报错

tlkj

如图所示，页面时不时的就会报这个错误。有时候重新刷新一下，重新登录可能就好了。


com.justep.exception.BusinessException: 编码: JUSTEP150210; 提示: 执行KSQL出错, KSQL: SELECT St_glcxx.*  FROM St_glcxx St_glcxx WHERE (St_glcxx.SCBS  = 0) LIMIT 0, -1
--> sql: SELECT  St_glcxx.BZ AS BZ, St_glcxx.DLSJ AS DLSJ, St_glcxx.DLZ AS DLZ, St_glcxx.GLCBH AS GLCBH, St_glcxx.GLCDD AS GLCDD, St_glcxx.GLCGK AS GLCGK, St_glcxx.GLCLXDH AS GLCLXDH, St_glcxx.GLCMC AS GLCMC, St_glcxx.GXSJ AS GXSJ, St_glcxx.GXZ AS GXZ, St_glcxx.SCBS AS SCBS, St_glcxx.fID AS St_glcxx, St_glcxx.VERSION AS version FROM st_glcxx St_glcxx  WHERE St_glcxx.SCBS = ?
--> binds: [0]
        at com.justep.exception.BusinessException.create(Unknown Source)
        at com.justep.system.data.impl.TableUtilsImplement.ksqlSelect(Unknown Source)
        at com.justep.system.data.impl.TableUtilsImplement.ksqlSelect(Unknown Source)
        at com.justep.system.data.impl.TableUtilsImplement.ksqlSelect(Unknown Source)
        at com.justep.system.data.BizData.query(Unknown Source)
        at BizProcedure.query(BizProcedure.java:12)
        ... 26 more
Caused by: com.justep.exception.BusinessException: 编码: JUSTEP150039; 提示: 执行sql: SELECT  St_glcxx.BZ AS BZ, St_glcxx.DLSJ AS DLSJ, St_glcxx.DLZ AS DLZ, St_glcxx.GLCBH AS GLCBH, St_glcxx.GLCDD AS GLCDD, St_glcxx.GLCGK AS GLCGK, St_glcxx.GLCLXDH AS GLCLXDH, St_glcxx.GLCMC AS GLCMC, St_glcxx.GXSJ AS GXSJ, St_glcxx.GXZ AS GXZ, St_glcxx.SCBS AS SCBS, St_glcxx.fID AS St_glcxx, St_glcxx.VERSION AS version FROM st_glcxx St_glcxx  WHERE St_glcxx.SCBS = ?, binds: [0]出错
        at com.justep.exception.BusinessException.create(Unknown Source)
        at com.justep.system.ksql.KSQLUtils.execSqlSelect(Unknown Source)
        ... 31 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 102,146,313 milliseconds ago.  The last packet sent successfully to the server was 102,152,375 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 the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
        at sun.reflect.GeneratedConstructorAccessor123.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
        at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:981)
        at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3652)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2460)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2625)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2551)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
        at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
        ... 32 more
Caused by: java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3634)
        ... 39 more

jishuang

Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 102,146,313 milliseconds ago.  The last packet sent successfully to the server was 102,152,375 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 the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

这个是mysql的错误
http://docs.wex5.com/bex5-deploy-question-list-4011/