[Mifos-issues] [JIRA Studio] Created: (MIFOS-4351) Test servers batch jobs all failing
jbrewster (JIRA)
-----------------------------------
Key: MIFOS-4351
URL: http://mifosforge.jira.com/browse/MIFOS-4351
Project: mifos
Issue Type: Bug
Components: Batch jobs, Build and Testing
Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
Reporter: jbrewster
Assignee: Udai Gupta
All batch jobs on 2.0 and head-master test servers are failing. View details by going to Admin-Batch Jobs and clicking on Details link for each batch job.
For example,
GenerateMeetingsForCustomerAndSavingsTaskJob Fail Details
org.mifos.framework.exceptions.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
OR
ApplyHolidayChangesTaskJob Fail Details
org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78) at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117) at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Mifos-issues mailing list
Mifos-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
jbrewster (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jbrewster updated MIFOS-4351:
-----------------------------
Fix Version/s: Elsie F
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MIFOS-4351 started by Udai Gupta.
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63064#action_63064 ]
Udai Gupta commented on MIFOS-4351:
-----------------------------------
2010-12-20/05:29:36.328/PST WARN, org.hibernate.util.JDBCExceptionReporter, ?, ?, ?, SQL Error: 0, SQLState: 08003
2010-12-20/05:29:36.329/PST ERROR, org.hibernate.util.JDBCExceptionReporter, ?, ?, ?, No operations allowed after connection closed.Connection was implicitly closed by the driver.
2010-12-20/05:29:36.331/PST ERROR, org.springframework.batch.core.step.AbstractStep, ?, ?, ?, Encountered an error executing the step
org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query
at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78)
at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117)
at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.execute(ApplyHolidayChangesHelper.java:131)
at org.mifos.framework.components.batchjobs.TaskHelper.execute(TaskHelper.java:55)
at org.springframework.batch.core.step.tasklet.TaskletStep$ChunkTransactionCallback.doInTransaction(TaskletStep.java:358)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130)
at org.springframework.batch.core.step.tasklet.TaskletStep$2.doInChunkContext(TaskletStep.java:261)
at org.springframework.batch.core.scope.context.StepContextRepeatCallback.doInIteration(StepContextRepeatCallback.java:76)
at org.springframework.batch.repeat.support.RepeatTemplate.getNextResult(RepeatTemplate.java:367)
at org.springframework.batch.repeat.support.RepeatTemplate.executeInternal(RepeatTemplate.java:214)
at org.springframework.batch.repeat.support.RepeatTemplate.iterate(RepeatTemplate.java:143)
at org.springframework.batch.core.step.tasklet.TaskletStep.doExecute(TaskletStep.java:247)
at org.springframework.batch.core.step.AbstractStep.execute(AbstractStep.java:196)
at org.springframework.batch.core.job.SimpleStepHandler.handleStep(SimpleStepHandler.java:135)
at org.springframework.batch.core.job.flow.JobFlowExecutor.executeStep(JobFlowExecutor.java:61)
at org.springframework.batch.core.job.flow.support.state.StepState.handle(StepState.java:60)
at org.springframework.batch.core.job.flow.support.SimpleFlow.resume(SimpleFlow.java:144)
at org.springframework.batch.core.job.flow.support.SimpleFlow.start(SimpleFlow.java:124)
at org.springframework.batch.core.job.flow.FlowJob.doExecute(FlowJob.java:135)
at org.springframework.batch.core.job.AbstractJob.execute(AbstractJob.java:281)
at org.springframework.batch.core.launch.support.SimpleJobLauncher$1.run(SimpleJobLauncher.java:120)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:48)
at org.springframework.batch.core.launch.support.SimpleJobLauncher.run(SimpleJobLauncher.java:114)
at org.mifos.framework.components.batchjobs.MifosBatchJob.launchJob(MifosBatchJob.java:105)
at org.mifos.framework.components.batchjobs.MifosBatchJob.checkAndLaunchJob(MifosBatchJob.java:139)
at org.mifos.framework.components.batchjobs.MifosBatchJob.executeInternal(MifosBatchJob.java:86)
at org.mifos.framework.components.batchjobs.MifosBatchJob.checkAndLaunchJob(MifosBatchJob.java:139)
at org.mifos.framework.components.batchjobs.MifosBatchJob.executeInternal(MifosBatchJob.java:86)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: org.hibernate.exception.JDBCConnectionException: could not execute query
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:99)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.loader.Loader.doList(Loader.java:2297)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2172)
at org.hibernate.loader.Loader.list(Loader.java:2167)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:448)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1258)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:76)
... 29 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.Connection was implicitly closed by the driver.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.Util.getInstance(Util.java:381)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1012)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:986)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:981)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926)
at com.mysql.jdbc.ConnectionImpl.throwConnectionClosedException(ConnectionImpl.java:1201)
at com.mysql.jdbc.ConnectionImpl.checkClosed(ConnectionImpl.java:1188)
at com.mysql.jdbc.ConnectionImpl.prepareStatement(ConnectionImpl.java:4273)
at com.mysql.jdbc.ConnectionImpl.prepareStatement(ConnectionImpl.java:4239)
at com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:213)
at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:534)
at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:452)
at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161)
at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1596)
at org.hibernate.loader.Loader.doQuery(Loader.java:717)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270)
at org.hibernate.loader.Loader.doList(Loader.java:2294)
... 37 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 86,103,546 milliseconds ago. The last packet sent successfully to the server was 86,103,546 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)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1119)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3318)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1940)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2113)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2693)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2102)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2102)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2261)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76)
at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208)
at org.hibernate.loader.Loader.getResultSet(Loader.java:1849)
at org.hibernate.loader.Loader.doQuery(Loader.java:718)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270)
at org.hibernate.loader.Loader.doList(Loader.java:2294)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2172)
at org.hibernate.loader.Loader.list(Loader.java:2167)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:448)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1258)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
at org.mifos.framework.persistence.Persistence.runQuery(Persistence.java:112)
at org.mifos.framework.persistence.Persistence.executeNamedQuery(Persistence.java:105)
at org.mifos.accounts.fees.persistence.FeePersistence.getUpdatedFeesForCustomer(FeePersistence.java:66)
at org.mifos.framework.components.batchjobs.helpers.ApplyCustomerFeeChangesHelper.execute(ApplyCustomerFeeChangesHelper.java:51)
at org.mifos.framework.components.batchjobs.TaskHelper.execute(TaskHelper.java:55)
at org.springframework.batch.core.step.tasklet.TaskletStep$ChunkTransactionCallback.doInTransaction(TaskletStep.java:358)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130)
at org.springframework.batch.core.step.tasklet.TaskletStep$2.doInChunkContext(TaskletStep.java:261)
at org.springframework.batch.core.scope.context.StepContextRepeatCallback.doInIteration(StepContextRepeatCallback.java:76)
at org.springframework.batch.repeat.support.RepeatTemplate.getNextResult(RepeatTemplate.java:367)
at org.springframework.batch.repeat.support.RepeatTemplate.executeInternal(RepeatTemplate.java:214)
at org.springframework.batch.repeat.support.RepeatTemplate.iterate(RepeatTemplate.java:143)
at org.springframework.batch.core.step.tasklet.TaskletStep.doExecute(TaskletStep.java:247)
at org.springframework.batch.core.step.AbstractStep.execute(AbstractStep.java:196)
at org.springframework.batch.core.job.SimpleStepHandler.handleStep(SimpleStepHandler.java:135)
at org.springframework.batch.core.job.flow.JobFlowExecutor.executeStep(JobFlowExecutor.java:61)
at org.springframework.batch.core.job.flow.support.state.StepState.handle(StepState.java:60)
at org.springframework.batch.core.job.flow.support.SimpleFlow.resume(SimpleFlow.java:144)
at org.springframework.batch.core.job.flow.support.SimpleFlow.start(SimpleFlow.java:124)
at org.springframework.batch.core.job.flow.FlowJob.doExecute(FlowJob.java:135)
at org.springframework.batch.core.job.AbstractJob.execute(AbstractJob.java:281)
at org.springframework.batch.core.launch.support.SimpleJobLauncher$1.run(SimpleJobLauncher.java:120)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:48)
at org.springframework.batch.core.launch.support.SimpleJobLauncher.run(SimpleJobLauncher.java:114)
at org.mifos.framework.components.batchjobs.MifosBatchJob.launchJob(MifosBatchJob.java:105)
at org.mifos.framework.components.batchjobs.MifosBatchJob.checkAndLaunchJob(MifosBatchJob.java:136)
... 4 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3299)
... 48 more
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63073#action_63073 ]
Udai Gupta commented on MIFOS-4351:
-----------------------------------
Need more investigation,
Current workaround, use MySQL "wait_timeout" to some higher than 24 hours rather than the default of 8 hours.
http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
The batch job scheduler thread calls thread local hibernate session where the connection has timeout.
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63087#action_63087 ]
Udai Gupta edited comment on MIFOS-4351 at 12/21/10 6:20 AM:
-------------------------------------------------------------
Final conclusion:
Use in mysql configuration.
\[mysqld\]
wait_timeout = 90000 (25 hours)
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
was (Author: ugupta):
Final conclusion:
Use in mysql configuration.
[mysqld]
wait_timeout = 90000 (25 hours)
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63087#action_63087 ]
Udai Gupta commented on MIFOS-4351:
-----------------------------------
Final conclusion:
Use in mysql configuration.
[mysqld]
wait_timeout = 90000 (25 hours)
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Udai Gupta resolved MIFOS-4351.
-------------------------------
Resolution: Fixed
Story Points: 0.5
Scheduled For: Product
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63087#action_63087 ]
Udai Gupta edited comment on MIFOS-4351 at 12/21/10 6:21 AM:
-------------------------------------------------------------
Final conclusion:
Use in mysql configuration.
\[mysqld\]
# 25 hours
wait_timeout = 90000
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
was (Author: ugupta):
Final conclusion:
Use in mysql configuration.
\[mysqld\]
wait_timeout = 90000 (25 hours)
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63087#action_63087 ]
Udai Gupta edited comment on MIFOS-4351 at 12/21/10 6:22 AM:
-------------------------------------------------------------
Final conclusion:
Use in mysql configuration.
\[mysqld\]
\# 25 hours, batch job run once in 24 hours
wait_timeout = 90000
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
was (Author: ugupta):
Final conclusion:
Use in mysql configuration.
\[mysqld\]
# 25 hours
wait_timeout = 90000
read more http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
we should not use autoReconnect JDBC property,
"Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours."
from http://dev.mysql.com/doc/refman/5.1/en/connector-j-reference-configuration-properties.html
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
jbrewster (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jbrewster reopened MIFOS-4351:
------------------------------
Can you please implement this workaround on birch? Currently the demo server and other servers have this issue and batch jobs are failing.
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
>
>
> All batch jobs on 2.0 and head-master test servers are failing. View details by going to Admin-Batch Jobs and clicking on Details link for each batch job.
> For example,
> GenerateMeetingsForCustomerAndSavingsTaskJob Fail Details
> org.mifos.framework.exceptions.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
> OR
> ApplyHolidayChangesTaskJob Fail Details
> org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78) at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117) at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63272#action_63272 ]
Udai Gupta commented on MIFOS-4351:
-----------------------------------
I have applied the fix to the birch two days ago, and the batch jobs ran without failure on e-release deployment (which was deployed two days ago).
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
>
>
> All batch jobs on 2.0 and head-master test servers are failing. View details by going to Admin-Batch Jobs and clicking on Details link for each batch job.
> For example,
> GenerateMeetingsForCustomerAndSavingsTaskJob Fail Details
> org.mifos.framework.exceptions.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
> OR
> ApplyHolidayChangesTaskJob Fail Details
> org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78) at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117) at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Udai Gupta (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Udai Gupta resolved MIFOS-4351.
-------------------------------
Resolution: Fixed
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
>
>
> All batch jobs on 2.0 and head-master test servers are failing. View details by going to Admin-Batch Jobs and clicking on Details link for each batch job.
> For example,
> GenerateMeetingsForCustomerAndSavingsTaskJob Fail Details
> org.mifos.framework.exceptions.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
> OR
> ApplyHolidayChangesTaskJob Fail Details
> org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78) at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117) at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
jbrewster (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jbrewster updated MIFOS-4351:
-----------------------------
Status: Ready for Showcase (was: Ready for Testing / Resolved)
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
>
>
> All batch jobs on 2.0 and head-master test servers are failing. View details by going to Admin-Batch Jobs and clicking on Details link for each batch job.
> For example,
> GenerateMeetingsForCustomerAndSavingsTaskJob Fail Details
> org.mifos.framework.exceptions.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
> OR
> ApplyHolidayChangesTaskJob Fail Details
> org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78) at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117) at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
Kay Chau (JIRA)
[ http://mifosforge.jira.com/browse/MIFOS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kay Chau updated MIFOS-4351:
----------------------------
Status: Ready to Ship / Verified (was: Ready for Showcase)
> Test servers batch jobs all failing
> -----------------------------------
>
> Key: MIFOS-4351
> URL: http://mifosforge.jira.com/browse/MIFOS-4351
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs, Build and Testing
> Environment: http://ci.mifos.org:8116/mifos, http://ci.mifos.org:8085/mifos
> Reporter: jbrewster
> Assignee: Udai Gupta
> Fix For: Elsie F
>
>
> All batch jobs on 2.0 and head-master test servers are failing. View details by going to Admin-Batch Jobs and clicking on Details link for each batch job.
> For example,
> GenerateMeetingsForCustomerAndSavingsTaskJob Fail Details
> org.mifos.framework.exceptions.PersistenceException: org.hibernate.exception.JDBCConnectionException: could not execute query
> OR
> ApplyHolidayChangesTaskJob Fail Details
> org.mifos.core.MifosRuntimeException: org.hibernate.exception.JDBCConnectionException: could not execute query at org.mifos.accounts.savings.persistence.GenericDaoHibernate.executeNamedQuery(GenericDaoHibernate.java:78) at org.mifos.application.holiday.persistence.HolidayDaoHibernate.getUnAppliedHolidays(HolidayDaoHibernate.java:117) at org.mifos.framework.components.batchjobs.helpers.ApplyHolidayChangesHelper.initializeTaskGlobalParameters(ApplyHolidayChangesHelper.java:287)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
pavankumar (JIRA)
|
|
|||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators |
Udai Gupta (JIRA)
|
|
|||||||
|
This message is automatically generated by JIRA. |
|
If you think it was sent incorrectly, please contact your JIRA administrators |