Comment 1 for bug 1741844

I agree that this is undesirable, but I see no way to avoid this for CA put w/o callback. The protocol doesn't define a completion ack. message. So the fact that the client gets the CA exception message at all is a side-effect of the second get. And handling of exception message has always been a weak point of CA implementations.

The only logic I can think of is the return non-zero if any ca exception message is received.
Not sure if this would trigger any false positives though.