If the parser encounters an error while parsing the poll response, we drop that
message and move on. Changing that to reset the connection in that case. This
avoids missing config. Also, if the error keeps happening (say because irond is
consistently sending badly structured messages), its better to move to another
irond by resetting and retrying a new connection.
Fix intermittent failures in ifmap_restart_test. The failures happened because
the newly added properties did not get a chance to be processed by the
server-table code and so the objects did not exist at the point the test-case
ran and checked for the existence of the object.
Merge pull request #177 from Juniper/logchg

If the parser encounters an error while parsing the poll response, we dr...