Errors with message trigger

Question

question

Shuo Zhang asked Mar 22, '17 Ben Wilson commented Mar 22, '17

Errors with message trigger

Hello!

I keep receiving the following error:

time: 830.924241 exception: Exception caught in TreeNode::receivemessage() time: 830.924241 exception: Exception caught in Executive::processeventinlist(). Throwing. time: 830.924241 exception: Exception caught in Executive::steptotime(). Throwing. time: 830.924241 exception: Exception caught in Executive::tick(). Throwing. time: 830.924241 exception: int runthemessageloop() #4 exception: core->theexecutive.tick(); time: 830.924241 exception: int runthemessagelwarehouse-simulation-v01.fsmoop() #6

The fact is that I have the same onentry-send message onmessage-create flowitem settings in multiple places. But only in one place(sink2 and queue2) it gives me this error. I did looked at the previous post about a similar issue and I changed the delay to be 1 and reopened the model several times. But I still receive the same error. Can someone help me look at it please?

Much thanks in advance!

Sam

Software Version:

FlexSim 17.0.3

onentry onmessage

warehouse-simulation-v01.fsm (2.2 MiB)

Answer 1 · 2017-03-22T16:33:03Z

Steven Hamoen answered Mar 22, '17 Ben Wilson commented Mar 22, '17

@Shuo Zhang Because with your onmessage code you create a token which fires the onentry and onexit of the Queue2 so the combiner works and then the pallets with 300 bottles enters queue3. All inside your onmessage code. The problem is that Queue3 had a sendmessage option to a centerport object but there are no centerport connections on that Queue3.

Better to create the flowitem in the onmessage and then use a senddelayed message with a delay 0 to open and close the ports on the queue. That way you break up the chain of commands and makes it easier to debug.

· 1

Shuo Zhang commented · Mar 22, 2017 at 04:47 PM

Thanks, Steven! I think the issue was with the queue3 onentry sendmessage trigger and actually it's something I don't need in my model. So I just simply deleted that trigger and the error went away!

1 ·

question