Hi,
I have faced with something interesting when I wait too much on the
Recording page (a recording is chosen bu not played) and any idea about
this error?
It is reproducible when a user enters the Recording room and chooses
one recording and waits for some time and then if he tries to go to
dashboard, system is giving this error and takes user to the dashboard
however no user picture is shown and user should refresh the dashboard
to see everything OK.
I have checked the "autoReconnect" option and it is already set to
"true" and could not find "increasing the server configured values for
client timeouts" part. How can I eliminate this error.
Thank you, best regards,
_Mahmut
ERROR is :
ERROR 03-05 11:24:26.141 SessiondataDao.java 328769539 148
org.apache.openmeetings.data.basic.SessiondataDao [http-bio-0.0.0.0-80-exec-15]
- [checkSession]:
org.apache.openjpa.persistence.PersistenceException: The last packet
successfully received from the server was 73,360,297 milliseconds ago.
The last packet sent successfully to the server was 73,360,297 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
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
~[openjpa-bundle-2.2.1.jar:2.2.1]
.
.
.
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
packet successfully received from the server was 73,360,297
milliseconds ago. The last packet sent successfully to the server was
73,360,297 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.NativeConstructorAccessorImpl.newInstance0(Native Method)
~[na:1.6.0_26]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
~[na:1.6.0_26]
.
.
.
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.connect(JDBCStoreManager.java:967)
~[openjpa-bundle-2.2.1.jar:2.2.1]
... 44 common frames omitted
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
~[na:1.6.0_26]
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
~[na:1.6.0_26]
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
~[na:1.6.0_26]
at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
~[na:1.6.0_26]
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
~[na:1.6.0_26]
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3852)
~[mysql-connector-java-5.1.23-bin.jar:na]
... 60 common frames omitted
ERROR 03-05 11:24:26.154 DownloadHandler.java 328769552 352
org.apache.openmeetings.servlet.outputhandler.DownloadHandler
[http-bio-0.0.0.0-80-exec-15] - Error downloading:
org.springframework.orm.jpa.JpaSystemException: The last packet successfully
received from the server was 73,360,297 milliseconds ago. The last packet sent
successfully to the server was 73,360,297 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.; nested exception is
<openjpa-2.2.1-r422266:1396819 fatal general error>
org.apache.openjpa.persistence.PersistenceException: The last packet successfully
received from the server was 73,360,297 milliseconds ago.
The last packet sent successfully to the server was 73,360,297 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.
FailedObject: select c from Sessiondata as c where c.session_id LIKE
:session_id [java.lang.String]
at
org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
at
org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
~[org.springframework.orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
.
.
.
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[na:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [na:1.6.0_26]
Caused by: org.apache.openjpa.persistence.PersistenceException: The last packet
successfully received from the server was 73,360,297 milliseconds ago. The
last packet sent successfully to the server was 73,360,297 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
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958)
~[openjpa-bundle-2.2.1.jar:2.2.1]
.
.
.
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
~[org.springframework.transaction-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]
... 23 common frames omitted
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last
packet successfully received from the server was 73,360,297 milliseconds ago.
The last packet sent successfully to the server was 73,360,297 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.NativeConstructorAccessorImpl.newInstance0(Native Method)
~[na:1.6.0_26]
at
.
.
.
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
~[na:1.6.0_26]
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
~[na:1.6.0_26]
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
~[na:1.6.0_26]
at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
~[na:1.6.0_26]
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
~[na:1.6.0_26]
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3852)
~[mysql-connector-java-5.1.23-bin.jar:na]
... 60 common frames omitted
