[4suite] [ foursuite-Bugs-881027 ] 4ss client commands can silently fail in edge cases

[SourceForge.net]

Bugs item #881027, was opened at 2004-01-20 18:37
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428292&aid=881027&group_id=39954

Category: 4SS (4Suite Server)
Group: v1.0a
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Brown (mike_j_brown)
Assigned to: Jeremy Kloth (jkloth)
Summary: 4ss client commands can silently fail in edge cases

Initial Comment:
'dsuch' on IRC reports that if the network goes down 
during a '4ss create container' invocation, the command 
may seem to work, but actually silently fails, most likely 
during the txCommit().

Probably the blind try/except in the command code 
should be around the txRollback only, not the txCommit, 
so that errors during the commit can be reported. This 
would need to be done in various other commands, too.

It was noted by Jeremy that there may be some commit 
errors that we do not want to expose. Also, there may 
be some advantage to moving the blind try/except into 
the client txRollback() code, rather than doing it in each 
command. To catch network errors at a lower level, 
maybe implement QOS/ACK-type stuff in FtRpc.

At J's request, I'm filing this as a bug so he'll remember 
to give it more thought and implement some kind of 
solution.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428292&aid=881027&group_id=39954