[
http://mifosforge.jira.com/browse/MIFOS-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau resolved MIFOS-4822.
-----------------------------
Resolution: Won't Fix
Might be caused by moving around system date, resolving
> Error viewing Batch job page after executing update test
> --------------------------------------------------------
>
> Key: MIFOS-4822
> URL: http://mifosforge.jira.com/browse/MIFOS-4822
> Project: mifos
> Issue Type: Bug
> Affects Versions: Release 2.0.2
> Environment: 2.0.2 with customer data, moved date fwd for savings
> posting tests
> Reporter: Jeff Brewster
> Attachments: screenshot-1.jpg
>
>
> In anticipation of upgrading customers to 2.0.2, I tested savings posting and
> end of Q1 by moving system date foward to April 2 and executing all batch
> jobs via the batch jobs page.
> After letting batch jobs execute, next day login to system (system date is
> now back to current date/time) and view Batch Job page. Now see attached
> screen with error:
> Error when retrieving batch jobs information: PreparedStatementCallback; SQL
> [SELECT JOB_INSTANCE_ID, JOB_NAME from BATCH_JOB_INSTANCE where JOB_NAME = ?
> order by JOB_INSTANCE_ID desc]; The last packet successfully received from
> the server was 98,292,833 milliseconds ago. The last packet sent successfully
> to the server was 98,292,835 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 com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The
> last packet successfully received from the server was 98,292,833 milliseconds
> ago. The last packet sent successfully to the server was 98,292,835
> 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.
> Is this a test-only bug?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
