Page 1 of 1

Repository timeout issue

PostPosted:Fri Sep 23, 2011 7:31 am
by ibrahim
Hi,

I get error when I login (Repository timeout) every morning after server stays idle for night. Once I restart the jobss server, it works good. How to increase timeout for repository. I am using version 4.1.

With regards,

Ibrahim.

Re: Repository timeout issue

PostPosted:Fri Sep 23, 2011 6:14 pm
by jllort
That's strange error, it's not normal. Which database do you have, that comes by default or other.
Why are you using so older version 4.1 ... I suggest upgrading because we're not mantaining this older version.

Re: Repository timeout issue

PostPosted:Wed Sep 28, 2011 7:23 am
by ibrahim
Thanks for your reply.

I have done some customization on version 4.1, so upgrading to newer version is bit difficult. I am using MySQL5.1.

Please find the error console.
Code: Select all
OKM-020001: Repository internal error

No operations allowed after statement closed.

OKM-020001: Repository internal error

The last packet successfully received from the server was69747 seconds ago.The last packet sent successfully to the server was 69747 seconds ago, which 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.

OKM-020001: Repository internal error

No operations allowed after statement closed.

OKM-020001: Repository internal error

No operations allowed after statement closed.

OKM-020001: Repository internal error

No operations allowed after statement closed.

OKM-020001: Repository internal error

No operations allowed after statement closed.

OKM-020001: Repository internal error

No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: ** BEGIN NESTED EXCEPTION ** 

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException MESSAGE: The last packet successfully received from the server was59789 seconds ago.The last packet sent 

successfully to the server was 59789 seconds ago, which 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. STACKTRACE: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the 

server was59789 seconds ago.The last packet sent successfully to the server was 59789 seconds ago, which 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) at 

sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at 

java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at 

com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3246) at 

com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1917) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL

(ConnectionImpl.java:2542) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734) at com.mysql.jdbc.PreparedStatement.execute

(PreparedStatement.java:995) at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.execute(CachedPreparedStatement.java:214) at 

org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:299) at com.usc.edms.dao.ActivityDAO.create(ActivityDAO.java:105) at 

com.usc.edms.util.UserActivity.log(UserActivity.java:63) at com.usc.edms.module.direct.EDMSDirectAuthModule.login(EDMSDirectAuthModule.java:166) at 

com.usc.edms.module.direct.EDMSDirectAuthModule.login(EDMSDirectAuthModule.java:326) at com.usc.edms.api.EDMSAuth.login(EDMSAuth.java:68) at 

org.apache.jsp.com_usc_edms_frontend_Main.index_jsp._jspService(index_jsp.java:61) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at 

javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at 

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) at 

javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at 

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at 

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter

(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at 

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke

(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at 

org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at 

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke

(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at 

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at 

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run

(JIoEndpoint.java:446) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Software caused connection abort: socket write error at 

java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown 

Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at com.mysql.jdbc.MysqlIO.send

(MysqlIO.java:3227) ... 38 more ** END NESTED EXCEPTION ** 

OKM-020001: Repository internal error

No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: ** BEGIN NESTED EXCEPTION ** 

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException MESSAGE: The last packet successfully received from the server was59789 seconds ago.The last packet sent 

successfully to the server was 59789 seconds ago, which 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. STACKTRACE: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the 

server was59789 seconds ago.The last packet sent successfully to the server was 59789 seconds ago, which 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) at 

sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at 

java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at 

com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3246) at 

com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1917) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL

(ConnectionImpl.java:2542) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734) at com.mysql.jdbc.PreparedStatement.execute

(PreparedStatement.java:995) at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.execute(CachedPreparedStatement.java:214) at 

org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:299) at com.usc.edms.dao.ActivityDAO.create(ActivityDAO.java:105) at 

com.usc.edms.util.UserActivity.log(UserActivity.java:63) at com.usc.edms.module.direct.EDMSDirectAuthModule.login(EDMSDirectAuthModule.java:166) at 

com.usc.edms.module.direct.EDMSDirectAuthModule.login(EDMSDirectAuthModule.java:326) at com.usc.edms.api.EDMSAuth.login(EDMSAuth.java:68) at 

org.apache.jsp.com_usc_edms_frontend_Main.index_jsp._jspService(index_jsp.java:61) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at 

javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at 

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) at 

javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at 

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at 

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter

(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at 

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke

(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at 

org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at 

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke

(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at 

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at 

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run

(JIoEndpoint.java:446) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Software caused connection abort: socket write error at 

java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown 

Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at com.mysql.jdbc.MysqlIO.send

(MysqlIO.java:3227) ... 38 more ** END NESTED EXCEPTION ** 

OKM-020001: Repository internal error

No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: ** BEGIN NESTED EXCEPTION ** 

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException MESSAGE: The last packet successfully received from the server was59789 seconds ago.The last packet sent 

successfully to the server was 59789 seconds ago, which 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. STACKTRACE: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the 

server was59789 seconds ago.The last packet sent successfully to the server was 59789 seconds ago, which 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) at 

sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at 

java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at 

com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3246) at 

com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1917) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL

(ConnectionImpl.java:2542) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734) at com.mysql.jdbc.PreparedStatement.execute

(PreparedStatement.java:995) at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.execute(CachedPreparedStatement.java:214) at 

org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:299) at com.usc.edms.dao.ActivityDAO.create(ActivityDAO.java:105) at 

com.usc.edms.util.UserActivity.log(UserActivity.java:63) at com.usc.edms.module.direct.EDMSDirectAuthModule.login(EDMSDirectAuthModule.java:166) at 

com.usc.edms.module.direct.EDMSDirectAuthModule.login(EDMSDirectAuthModule.java:326) at com.usc.edms.api.EDMSAuth.login(EDMSAuth.java:68) at 

org.apache.jsp.com_usc_edms_frontend_Main.index_jsp._jspService(index_jsp.java:61) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at 

javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at 

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) at 

javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at 

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at 

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter

(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at 

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke

(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at 

org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at 

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke

(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at 

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at 

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run

(JIoEndpoint.java:446) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException: Software caused connection abort: socket write error at 

java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown 

Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at com.mysql.jdbc.MysqlIO.send

(MysqlIO.java:3227) ... 38 more ** END NESTED EXCEPTION ** 

OKM-020001: Repository internal error

No operations allowed after statement closed. 

With regards,

Ibrahim.

Re: Repository timeout issue

PostPosted:Fri Sep 30, 2011 6:31 am
by jllort
OK, You've got a mysql connection timeout problem.

In openkm-ds must add
Code: Select all
 <idle-timeout-minutes>28680</idle-timeout-minutes>
In openkm-ds, workspace.xml and repository.xml must add the ?autoReconnect=true parameter
Code: Select all
jdbc:mysql://localhost:3306/okm_app?autoReconnect=true

Re: Repository timeout issue

PostPosted:Fri Sep 30, 2011 9:37 am
by ibrahim
Thanks for your reply... let me configure those settings and check.

With regards,

Ibrahim

Re: Repository timeout issue

PostPosted:Thu Jan 05, 2012 10:21 am
by ibrahim
Hi,

I did the modifications in repository.xml, workspace.xml and openkm-ds.xml as you suggest. still am getting the same issue.

any idea to resolve this issue?

With regards,

Ibrahim,

Re: Repository timeout issue

PostPosted:Sun Jan 08, 2012 11:20 am
by jllort
Version 4.1 is older version, you should think to upgrading to 5.1. Althought it you could try upgrading your jdbc mysql driver to ensure there's no problem on it.