[
https://issues.apache.org/jira/browse/FINERACT-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127578#comment-17127578
]
Michael Vorburger commented on FINERACT-995:
--------------------------------------------
[~xurror] just in case you are looking for things to do, and if you are tired
:D of EclipseLink work in FINERACT-849 and could be interested in helping to
still fix a problem with OpenJPA (before we eventually migrate.. but I have
"feeling" that 1.4.0 release may still be OpenJPA, and only 1.5.0 may be
EclipseLink?), this to me looks like a bad bug which I would suggest we
consider a hard Blocker for a possible future 1.4.0 release. Actually, this may
not even be directly OpenJPA related, perhaps it's some JPA API mis-use
(configuration) that would even still happen when we'll move to EclipseLink
some day - IMHO it's worth for someone to analyse more what's going on here
either way. Also /Cc [~Percy Ashu], [~ptuomola], [~awasum] in case you're
looking for something to do... ;)
> Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY
> --------------------------------------------------------------------------
>
> Key: FINERACT-995
> URL: https://issues.apache.org/jira/browse/FINERACT-995
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Michael Vorburger
> Priority: Blocker
> Fix For: 1.4.0
>
>
> See FINERACT-932 for general background. This should definitely be "fixed":
> {noformat}org.quartz.SchedulerException: Job threw an unhandled exception.
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
> Caused by:
> org.springframework.scheduling.quartz.JobMethodInvocationFailedException:
> Invocation of method 'updateLoanArrearsAgeingDetails' on target class [class
> org.apache.fineract.portfolio.loanaccount.service.LoanArrearsAgingServiceImpl$$EnhancerBySpringCGLIB$$f1072374]
> failed; nested exception is
> org.springframework.dao.TransientDataAccessResourceException:
> StatementCallback; SQL [select ml.id as loanId, mr.duedate as dueDate,
> mr.principal_amount as principalAmount, mr.interest_amount as interestAmount,
> mr.fee_charges_amount as feeAmount, mr.penalty_charges_amount as
> penaltyAmount from m_loan ml INNER JOIN m_loan_repayment_schedule_history
> mr on mr.loan_id = ml.id where mr.duedate < SUBDATE(CURDATE(),INTERVAL
> ifnull(ml.grace_on_arrears_ageing,0) day) and ml.id IN(8, 9) and mr.version
> = (select max(lrs.version) from m_loan_repayment_schedule_history lrs where
> mr.loan_id = lrs.loan_id) order by ml.id,mr.duedate]; Operation not allowed
> for a result set of type ResultSet.TYPE_FORWARD_ONLY.; nested exception is
> java.sql.SQLException: Operation not allowed for a result set of type
> ResultSet.TYPE_FORWARD_ONLY.
> at
> org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:276)
> at
> org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:75)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202){noformat}
> As per FINERACT-932, this happened on Fineract.dev, which runs with the MySQL
> JDBC thin driver that is part of our Docker image. It's possible that this is
> related to a specific JDBC Driver, and cannot be reproduced with Drizzle.
> IMHO we should consider FINERACT-982 (which won't fix this, but perhaps make
> it appear in integration testing already; worth a try at least).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
