[ERROR] SCHEDULER-304

Help
webx
2012-09-28
2012-12-10
  • webx

    webx - 2012-09-28

    Hi I have a problem using jobscheduler
    I get this error when I keep the application running for more than one day.
    So I have to restart jobscheduler every day…

    When I try to execute a job I have this error message on the web interface :

    Z-JAVA-105  Java exception com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException("No operations allowed after connection closed.
    The last packet successfully received from the server was 62 175 033 milliseconds ago. The last packet sent successfully to the server was 62 175 039 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 'autoReconnec..."), method=prepareStatement []
    

    When I have a look on logs file I see this :

    28 10:51:00.345     1 25650.B778C6D0 {scheduler} [ERROR]  SCHEDULER-304  Error when reading next id (column "spooler_job_id"): Z-JAVA-105  Java exception com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException("No operations allowed after connection closed.
    ==> scheduler-2012-09-27-084256.scheduler.log <==
    2012-09-28 10:51:00.345 [ERROR]  SCHEDULER-304  Error when reading next id (column "spooler_job_id"): Z-JAVA-105  Java exception com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException("No operations allowed after connection closed.
    ==> scheduler.log <==
    28 10:51:00.345     0 25650.B778C6D0 {scheduler} [ERROR]  The last packet successfully received from the server was 62?175?033 milliseconds ago.  The last packet sent successfully to the server was 62?175?039 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...
    ==> scheduler-2012-09-27-084256.scheduler.log <==
    2012-09-28 10:51:00.345 [ERROR]  The last packet successfully received from the server was 62?175?033 milliseconds ago.  The last packet sent successfully to the server was 62?175?039 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...
    

    I found on a website I have to set up differently the hibernate.cfg.xml config file. Is it right ?
    How can I adjust the server timing and client timeout to prevent this problem ?

    Regards

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks