Gumtree

GumTree has failed to receive SICS message

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.5.6
  • Fix Version/s: 1.6.0, 1.5.7
  • Component/s: sics
  • Labels:
    None
  • Number of attachments :
    0

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:

{"/instrument/collimator/att/target": 62}

12:49:25.051483: Next line intended for socket: 23
12:49:25.051499:

{"/instrument/collimator/att/target": 62}

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:

{"/data/sics_suid": 10553}

12:49:25.051880: Next line intended for socket: 23
12:49:25.051894:

{"/data/sics_suid": 10553}

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:

{"/instrument/collimator/att": 89.9806}

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":

{ "/monitor/bm2_time": 10.172200 }

}
2011-05-19 12:49:56,965 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied:

{ "con": 63, "trans": 4, "object": "status", "flag": "wa rning", "data": "status = Driving" }

2011-05-19 12:49:56,965 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied:

{ "con": 63, "trans": 4, "object": "status", "flag": "wa rning", "data": "status = Driving" }

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":

{ "/instrument/collimator/att/target": 62 }

}
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":

{ "/data/sics_suid": 10553 }

}
2011-05-19 12:49:57,090 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.internal
.io.SicsProxy - Server replied:

{ "con": 63, "trans": 3, "object": "statemon", "flag": " warning", "data": "/instrument/collimator/att STARTED" }

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":

{ "/instrument/collimator/att": 89.980600 }

}

Normally we should receive "STARTED = att" between message ""/data/sics_suid": 10553" and "/instrument/collimator/att STARTED" in GumTree, but it was missing.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tony Lam added a comment -

We need to test the communication layer between SICS and GumTree to see if there is any message lost.

Show
Tony Lam added a comment - We need to test the communication layer between SICS and GumTree to see if there is any message lost.
Hide
Permalink
Tony Lam added a comment -

The "STARTED = att" was captured in the GumTree proxy:

2011-05-19 12:49:25,054 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.
internal.io.SicsProxy - Server replied: { "con": 43, "trans": 1, "object": "hnot
ify", "flag": "hdbevent", "data":

{ "/data/sics_suid": 10553 }

}
2011-05-19 12:49:25,056 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics.
internal.io.SicsProxy - Server replied:

{ "con": 43, "trans": 2, "object": "stat emon", "flag": "warning", "data": "STARTED = att" }

2011-05-19 12:49:25,056 INFO [pool-1-thread-1] org.gumtree.gumnix.sics.control.
controllers.DrivableController - State changed (old_status=OK, sics_state=STARTE
D).

This means either the message is lost between ics1-quokka and dav1-quokka, or there is a problem in the SICS proxy code.

Show
Tony Lam added a comment - The "STARTED = att" was captured in the GumTree proxy: 2011-05-19 12:49:25,054 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics. internal.io.SicsProxy - Server replied: { "con": 43, "trans": 1, "object": "hnot ify", "flag": "hdbevent", "data": { "/data/sics_suid": 10553 } } 2011-05-19 12:49:25,056 INFO [SICS Message Dispatcher] org.gumtree.gumnix.sics. internal.io.SicsProxy - Server replied: { "con": 43, "trans": 2, "object": "stat emon", "flag": "warning", "data": "STARTED = att" } 2011-05-19 12:49:25,056 INFO [pool-1-thread-1] org.gumtree.gumnix.sics.control. controllers.DrivableController - State changed (old_status=OK, sics_state=STARTE D). This means either the message is lost between ics1-quokka and dav1-quokka, or there is a problem in the SICS proxy code.
Hide
Permalink
Tony Lam added a comment -

Problem identified:

GumTree discard the last message if the return character is received on the next socket packet.

eg
Packet 1 contains: "message 1\nmessage2"
Packet 2 contains: "\nmessage 3\message 4\n"

In this case message 2 will not be dispatched to GumTree.

Show
Tony Lam added a comment - Problem identified: GumTree discard the last message if the return character is received on the next socket packet. eg Packet 1 contains: "message 1\nmessage2" Packet 2 contains: "\nmessage 3\message 4\n" In this case message 2 will not be dispatched to GumTree.
Hide
Permalink
Tony Lam added a comment -

Fixed by re-writing buffering logic
See: http://fisheye.codehaus.org/changelog/gumtree/?cs=10410

Show
Tony Lam added a comment - Fixed by re-writing buffering logic See: http://fisheye.codehaus.org/changelog/gumtree/?cs=10410

People

  • Assignee:
    Tony Lam
    Reporter:
    Tony Lam
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: