Help understanding an error message

[Stacey Croft]

Hi Harry & all,

I've been trying to help a colleague by checking over a model they have been creating in JaamSim of a hospital ED department. We have noticed that when it's set to multiple replications some but not all give an error. We think it could be related to the capacity/priority of one of the resources as increasing capacity gives replications with out the error. Below is an example of the error from the log viewer, if anyone can help us understand what it's telling us and how to fix it. Please :)

(We haven't been able to replicate it yet in a file we can share and I've asked him permission to share the actual file and waiting to see if that's ok)

"EXCEPTION AT TIME: 454680.000000 s

null

Thrown exception call stack:

com.jaamsim.ProcessFlow.Queue.getFirstPriority(Queue.java:424)

com.jaamsim.ProcessFlow.AbstractLinkedResourceUser.getPriority(AbstractLinkedResourceUser.java:96)

com.jaamsim.resourceObjects.AbstractResourceProvider$UserCompare.compare(AbstractResourceProvider.java:203)

com.jaamsim.resourceObjects.AbstractResourceProvider$UserCompare.compare(AbstractResourceProvider.java:197)

java.util.TimSort.countRunAndMakeAscending(Unknown Source)

java.util.TimSort.sort(Unknown Source)

java.util.Arrays.sort(Unknown Source)

java.util.ArrayList.sort(Unknown Source)

java.util.Collections.sort(Unknown Source)

com.jaamsim.resourceObjects.AbstractResourceProvider.notifyResourceUsers(AbstractResourceProvider.java:189)

com.jaamsim.ProcessFlow.EntityProcessor.processStep(EntityProcessor.java:260)

com.jaamsim.ProcessFlow.Device.endStep(Device.java:230)

com.jaamsim.ProcessFlow.Device$EndStepTarget.process(Device.java:210)

com.jaamsim.events.EventManager.executeTarget(EventManager.java:171)

com.jaamsim.events.EventManager.execute(EventManager.java:256)

com.jaamsim.events.Process.run(Process.java:101)

 "

Thanks for any insight,

Stacey

[Harry King]

Stacey,

This looks like a bug. Please send me the input file by email if you do not want to post it to the forum. Any model you send me will kept confidential.

It is impossible to know exactly what is going on without the input file, but my guess is that the model uses an expression for the WaitQueue input for an EntityProcessor, and that the expression involves a random selection. If this is the case, you could fix the model by selecting the WaitQueue with a expression that does not involve any randomness. Otherwise, you will have to wait until the bug is fixed in the next release.

Harry

[Shammas Rahim]

Thanks Stacey, i've shared the model with Harry

[Harry King]

Stacey and Shammas,

This is a bug related to multiple EntityProcessor and/or Seize objects that share the same Queue. It will be corrected in the next release.

Harry

[Shammas Rahim]

thanks you for looking into this, I really appreciate it. Do you happen to have a rough date for the next release? (I'm just weighing up whether I need to rebuild the model or wait for the next release) as this piece of work is for a new hospital build

bw

shammas

[Harry King]

We will issue the new release in about one week or less.

Harry

[Shammas Rahim]

excellent, thank you

[Harry King]

Shammas,

The bug has been fixed in release 2022-01.

Harry

[Shammas Rahim]

Excellent, thank you