It seems that the error obtained in the integration tests are not a result of mishandling of notify delete message like I had thought. Since trying with req_id 42, the TO can handle the messages properly.
I think that the messages from the V2X are replaced with "\n" messages (heartbeat) causing the TO to behave unexpectedly,
Would it be worth changing the V2X heartbeat to "\t" to avoid this issue - then if the characters received is 1 and \t is the message, then it can be disregarded.
Hello,
It seems that the error obtained in the integration tests are not a result of mishandling of notify delete message like I had thought. Since trying with req_id 42, the TO can handle the messages properly.
I think that the messages from the V2X are replaced with "\n" messages (heartbeat) causing the TO to behave unexpectedly,
Would it be worth changing the V2X heartbeat to "\t" to avoid this issue - then if the characters received is 1 and \t is the message, then it can be disregarded.