#13 Bad message stops remote broker subscription permanently

v3.0 (2012 update)
closed-fixed
9
2012-03-09
2012-03-09
Bob Denny
No

If the remote broker message handler gets an error while loading the XML, it yanks down the transport connection. It should 'nak' the message and press on. Here's what it looks like in the log right now.

2012-03-08T21:20:17 [stcp] **Fatal error handling message from 209.208.78.170
2012-03-08T21:20:17 [stcp] '1.0' is an unexpected token. The expected token is '"' or '''. Line 87, position 19.
2012-03-08T21:20:17 [stcp] Connection to 209.208.78.170 will be terminated

Discussion

  • Bob Denny

    Bob Denny - 2012-03-09

    In RemoteBroker.HandleReceivedMessage, if the message fails to load as XML, respond with a NAK and the XML engine's error message.

     
  • Bob Denny

    Bob Denny - 2012-03-09
    • status: open --> closed-fixed