I'm seeing these errors with a number of nodes on testnet3.
Firstly, the formatting screws up debug.log, and secondly, the offending peer isn't displayed. (I've raised a pull request #4839 to fix this).
Thirdly, shouldn't the node be disconnected after a while, especially if a version message hasn't been received. Currently, it seems the misbehaving node is permitted to stay connected indefinately, and it continues sending invalid tx messages long after the invalid version message.
Is some misbehaviour logic appropriate here?
