Details
Description
During a Quokka workflow process, GumTree has failed to drive att due to the timeout on receiving start = att message. After checking on SICS log, SICS has reported the message was sent to its client.
SICS log:
12:49:25.051081: Executing > contextdo 8634 run att 60.0 < from socket 27
12:49:25.051162: Executing > run att 60.0 < from socket 27
12:49:25.051211: Next line intended for socket: 28
12:49:25.051226: status = Driving
12:49:25.051273: Next line intended for socket: 23
12:49:25.051286: status = Driving
12:49:25.051379: Next line intended for socket: 28
12:49:25.051392:
12:49:25.051483: Next line intended for socket: 23
12:49:25.051499:
12:49:25.051671: Next line intended for socket(1): 0
12:49:25.051684: SUID MSG STARTED = att
12:49:25.051783: Next line intended for socket: 28
12:49:25.051796:
12:49:25.051880: Next line intended for socket: 23
12:49:25.051894:
12:49:25.051953: Next line intended for socket: 28
12:49:25.051977: STARTED = att
12:49:25.055082: Next line intended for socket: 28
12:49:25.055107: /instrument/collimator/att STARTED
12:49:25.055207: Next line intended for socket: 23
12:49:25.055221: STARTED = att
12:49:25.057927: Next line intended for socket: 23
12:49:25.057948: /instrument/collimator/att STARTED
12:49:25.592755: Next line intended for socket: 28
12:49:25.592779:
GumTree log:
2011-05-19 12:49:56,949 INFO [pool-13-thread-1] org.gumtree.gumnix.sics.internal.io.Sic
sNonBlockingChannel:general - Client sent: contextdo 8634 run att 60.0
2011-05-19 12:49:56,949 INFO [pool-13-thread-1] org.gumtree.gumnix.sics.control.control
lers.DrivableController - Start waiting for /instrument/collimator/att state transition
(dirtyFlag=false, status=OK).
2011-05-19 12:49:56,949 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied: { "con": 63, "trans": 1, "object": "hnotify", "flag": "h
dbevent", "data":
}
2011-05-19 12:49:56,965 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied:
2011-05-19 12:49:56,965 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied:
2011-05-19 12:49:56,965 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied: { "con": 63, "trans": 1, "object": "hnotify", "flag": "h
dbevent", "data":
}
2011-05-19 12:49:56,965 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied: { "con": 63, "trans": 1, "object": "hnotify", "flag": "h
dbevent", "data":
}
2011-05-19 12:49:57,090 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied:
2011-05-19 12:49:57,621 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied: { "con": 63, "trans": 1, "object": "hnotify", "flag": "h
dbevent", "data":
}
Normally we should receive "STARTED = att" between message ""/data/sics_suid": 10553" and "/instrument/collimator/att STARTED" in GumTree, but it was missing.
We need to test the communication layer between SICS and GumTree to see if there is any message lost.