Netconf session closes and reconnects on error from non-heart beat RPC

NETCONF session closes on rpc error for non-heatbeat transaction. The desired behavoir is for the session to stay up and an error returned to the application (in this case it was a RESTconf initiated PUT (lock before edit-config).

Here is the log entry for the lock that failed. The failed lock was due to a mis-configuration on the device side wrt write transactions but get-config and other read only transactions were working fine before this error.

2016-06-28 21:59:10,858 | TRACE | oupCloseable-7-1 | NetconfDeviceCommunicator | RemoteDevice

{ncs5502}: Matched request: <rpc message-id="m-1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lock>
<target>
<candidate/>
</target>
</lock>
</rpc>
to response: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-message xml:lang="en">ME_BACKEND_ERROR_UNAUTHORIZED [non-QT backend request failed]</error-message>
</rpc-error>
<rpc-error>
<error-type>application</error-type>
<error-tag>backend-status-summary</error-tag>
<error-severity>warning</error-severity>
<error-message xml:lang="en">QT/SysDB backend passed, non-QT backend failed [read rest of response for details]</error-message>
</rpc-error>
</rpc-reply>

2016-06-28 21:59:10,860 | WARN | oupCloseable-7-1 | KeepaliveSalFacade | RemoteDevice{ncs5502}

: Rpc failure detected. Reconnecting netconf session