Bad memory config reply hangs memory/datagram service

[bobjacobsen]

A coding error that resulted in sending an ill formed datagram to JMRI, which JMRI rejected, as it should have. However, after this datagram gets rejected, JMRI will no longer send any subsequent datagrams, for example, to initiate a fresh read of the CDI of a node. It seems like the datagram logic is stuck in a bad place.

S: 02.01.12.FE.97.05 - 09.00.99.DD.02.40 Datagram: (7) 20.43.0.0.0.0.40
R: 09.00.99.DD.02.40 - 02.01.12.FE.97.05 DatagramReceivedOK with payload 80 flags 0x80
R: (Start of Datagram)
R: (Middle of Datagram)
R: (Middle of Datagram)
R: (Middle of Datagram)
R: (Middle of Datagram)
R: (Middle of Datagram)
R: (Middle of Datagram)
R: (Middle of Datagram)
R: 09.00.99.DD.02.40 - 02.01.12.FE.97.05 Datagram: (70) 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0
S: 02.01.12.FE.97.05 - 09.00.99.DD.02.40 DatagramRejected with payload 10 42 flags 0x1042