- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -8,7 +8,7 @@
The fix for that ticket blocks the client from using the handle
until the pending reply has been resolved.
-The reply can be resolved either by the OI replying (late) or
+The reply can be resolved either by the OI replying or
by the immnd-server time-out for continuations.
The latter will also clean up continuations for crashed or hung
OIs.
@@ -20,12 +20,17 @@
will simply abort the CCB in the server and not clear the handle.
This enhancement proposes that the cleanup of CCB-operation
-continuations should also generate a TIMEOUT reply to the client.
-Such a TIMEOUT will either be sent all the way to the client,
+continuations at OI timeout should also generate an ERROR reply to the client.
+An OI timeout on a ccb callback will always abort the CCB so any reply
+forwarded towards the OM CCB client should be an ERR_FAILED_OPERATION and not
+ERR_TIMEOUT.
+
+Such a timeout related error will either be sent all the way to the client,
if the client-side timeout is longer than the server timeout.
Or (when the client has already timed out in the library)
be discarded by MDS.
-The main point is that the handle gets cleared in the server when
-the continuation times out in the server.
+The main points are (a) that the handle gets cleared in the server when
+the continuation times out in the server; and (b) that the the CCB OM client
+receives an error reply when that om client has NOT timed out.
~~~~
---
** [tickets:#57] IMM: Immnd timeout on CCB-OI upcall should reset client
handle**
**Status:** assigned
**Milestone:** future
**Created:** Wed May 08, 2013 08:31 AM UTC by Anders Bjornerstedt
**Last Updated:** Mon Nov 04, 2013 01:01 PM UTC
**Owner:** Anders Bjornerstedt
Migrated from:
http://devel.opensaf.org/ticket/2339
See ticket 2284.
http://devel.opensaf.org/ticket/2284
The fix for that ticket blocks the client from using the handle
until the pending reply has been resolved.
The reply can be resolved either by the OI replying or
by the immnd-server time-out for continuations.
The latter will also clean up continuations for crashed or hung
OIs.
It is actually the case that for admin-operation continutaions and
for search-request-continuations, this should already be working.
But for CCB-operation continuations, a timeout in the immnd server
will simply abort the CCB in the server and not clear the handle.
This enhancement proposes that the cleanup of CCB-operation
continuations at OI timeout should also generate an ERROR reply to the client.
An OI timeout on a ccb callback will always abort the CCB so any reply
forwarded towards the OM CCB client should be an ERR_FAILED_OPERATION and not
ERR_TIMEOUT.
Such a timeout related error will either be sent all the way to the client,
if the client-side timeout is longer than the server timeout.
Or (when the client has already timed out in the library)
be discarded by MDS.
The main points are (a) that the handle gets cleared in the server when
the continuation times out in the server; and (b) that the the CCB OM client
receives an error reply when that om client has NOT timed out.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
