The Jammer stopped processing: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

Products

• Automation Analytics & Intelligence

Issue/Introduction

The Jammer stopped processing with the following error message in the jaws.log:

2022-09-27 12:37:20,440 WARN  [JobStreamVendorImpl] Inserted JobStreamJobs (0) for UUID[XXXXXXX=] <JobstreamName>
2022-09-27 12:37:20,440 WARN  [GenericSessionImpl] Closing a write session where the final commit() was never called. Some changes may not have been committed
 at com.termalabs.common.connection.hibernate.GenericSessionImpl.close(GenericSessionImpl.java:285)
 at com.termalabs.server.cache.JobStreamVendorImpl.lambda$updateFilterJobsWithWriteLock$13(JobStreamVendorImpl.java:2343)
 at com.termalabs.server.cache.RetryTask.apply(RetryTask.java:43)
 at com.termalabs.server.cache.JobStreamVendorImpl.updateFilterJobsWithWriteLock(JobStreamVendorImpl.java:2348)
 at com.termalabs.server.cache.JobStreamVendorImpl.updateFilterJobs(JobStreamVendorImpl.java:2300)
 at com.termalabs.server.app.jobstream.JobStreamBuilder.rebuildJobstreamsJobs(JobStreamBuilder.java:547)
 at com.termalabs.server.app.jobstream.JobStreamBuilder.rebuildJobStreamsForJobs(JobStreamBuilder.java:491)
 at com.termalabs.server.app.scheduler.ConverterAfterCommitAction.perform(ConverterAfterCommitAction.java:77)
 at com.termalabs.server.cache.scheduler.SchedulerUpdateImpl.postCommit(SchedulerUpdateImpl.java:463)
 at com.termalabs.server.cache.scheduler.SchedulerUpdateImpl.commit(SchedulerUpdateImpl.java:331)
 at com.termalabs.server.cache.scheduler.SchedulerUpdateImpl.commit(SchedulerUpdateImpl.java:298)
 at com.termalabs.server.app.scheduler.SchedulerHelper.convertScheduler(SchedulerHelper.java:259)
 at com.termalabs.server.app.scheduler.SchedulerHelper.downloadScheduler(SchedulerHelper.java:211)
 at com.termalabs.server.tidal.jammer.TidalJammer.runIncrementalConverter(TidalJammer.java:503)
 at com.termalabs.server.tidal.jammer.TidalJammer.processRuns(TidalJammer.java:326)
 at com.termalabs.server.system.RunCycle$JammerRunner.runJammer(RunCycle.java:1029)
 at com.termalabs.server.system.RunCycle$JammerRunner.run(RunCycle.java:1011)
 at com.termalabs.server.system.RunCycle.compute(RunCycle.java:281)
 at com.termalabs.server.system.CommonJammerSequence.runCycle(CommonJammerSequence.java:225)
 at com.termalabs.server.system.CommonJammerSequence.runJammerSequence(CommonJammerSequence.java:158)
 at com.termalabs.server.system.JammerSequence.run(JammerSequence.java:136)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:750)

2022-09-27 12:37:20,456 WARN  [RetryTask] Not retrying org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1: org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1
 at org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched(Expectations.java:85)
 at org.hibernate.jdbc.Expectations$BasicExpectation.verifyOutcome(Expectations.java:70)
 at org.hibernate.jdbc.BatchingBatcher.checkRowCounts(BatchingBatcher.java:90)
 at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)

Environment

Release : 6.4.3

Resolution

The issue has been fixed in AAI v6.4.5.