Operations | MESOperationsManager: Exception updating actual production quantity
Error When Running Operation in OEE Run Director
You are attempting to run an Operation from the OEE Run Director and receive this (only in the Gateway Logs)
particular error
|
MESOperationsManager 15Jun2021 14:34:50 Exception updating actual production quantity.
java.lang.InterruptedException: null
at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(Unknown Source)
at java.base/java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.tryLock(Unknown Source)
at com.sepasoft.analysis.core.manager.AnalysisManagerImpl.extractOperationSequence(AnalysisManagerImpl.java:1553)
at com.sepasoft.analysis.api.AnalysisManager.extractOperationSequence(AnalysisManager.java:282)
at com.sepasoft.production.analysis.mes.manager.MESAnalysisManager.executeAnalysis(MESAnalysisManager.java:740)
at com.sepasoft.production.analysis.mes.manager.MESAnalysisManager.executeAnalysis(MESAnalysisManager.java:714)
at com.sepasoft.production.mes.manager.MESOperationsManager.calcOEEOutfeedCount(MESOperationsManager.java:3526)
at com.sepasoft.production.mes.manager.MESOperationsManager.updateAutoLotCounts(MESOperationsManager.java:6209)
at com.sepasoft.production.mes.manager.MESOperationsManager$ActiveOperation.executeUpdateEvent(MESOperationsManager.java:11788)
at com.sepasoft.production.mes.manager.MESOperationsManager$ActiveOperation.run(MESOperationsManager.java:11461)
at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:538)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) |
Why and Solution
The Operation is set to Auto End when it will hit the Production Target Counts.
but if you are starting this Operation in the OEE Run Director,
it will have a production count of 0 as soon as going from ChangeOver to Production ...
the Segment will end on the first update after it begins,
and ending the Operation will interrupt the thread updating the counts, leading to this Gateway
message.
This kind of Material configuration, and created Operation, should only be used via Work Order => Schedule
with a Production Count target
