epics/pcas
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

dont send extra exception message conveying the context string when a get

Browse Source 
callback request fails
This commit is contained in:
Jeff Hill
2003-04-22 22:29:26 +00:00
parent 5bbf7bc341
commit d812f89280
1 changed files with 0 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
src/cas/generic/casStrmClient.cc
View File

@@ -571,26 +571,6 @@ caStatus casStrmClient::readNotifyResponse ( epicsGuard < casClientMutex > & gua
if ( completionStatus != S_cas_success ) {
caStatus ecaStatus = this->readNotifyFailureResponse (
guard, msg, ECA_GETFAIL );
if ( ecaStatus != S_cas_sendBlocked ) {
//
// send independent warning exception to the client so that they
// will see the error string associated with this error code
// since the error string cant be sent with the get call back
// response (hopefully this is useful information)
//
// order is very important here because it determines that the get
// call back response is always sent, and that this warning exception
// message will be sent at most one time (in rare instances it will
// not be sent, but at least it will not be sent multiple times).
// The message is logged to the console in the rare situations when
// we are unable to send.
//
caStatus tmpStatus = this->sendErrWithEpicsStatus ( guard,
& msg, pChan->getCID(), completionStatus, ECA_GETFAIL );
if ( tmpStatus ) {
errMessage ( completionStatus, "<= get callback failure detail not passed to client" );
}
}
return ecaStatus;
}