| [CDO] Loss of connectivity hosing the client [message #619334] |
Tue, 01 July 2008 07:57 |
 Tom Crockett
Messages: 54
Registered: July 2009 |
Member |
|
|
Hi, I'm wondering how best to handle network drops and loss of
connectivity in client code when using CDO. So far my experience has been
that this completely hoses the client beyond all repair, so that it must
be restarted (in certain cases it not only ceases to function but becomes
unresponsive waiting on a response from the server which never comes.) I
am using the HTTP connector.
Things I have tried to attempt to recover from network outages:
1) Close the transaction, open a new one. (throws an exception)
2) Close the session, open a new one.
3) Close the session's channel.
4) Disconnect the session's connector and reconnect it.
I've tried these steps in various orders and combinations with one
another, all to no avail. The only thing that gets the client working
again is to restart the whole application--needless to say this is far
from desirable. What is the "right" way to do this (assuming there is
one)?
My experience so far has been that CDO works great when you use it exactly
as you're supposed to (which takes some figuring out since it doesn't have
much documentation yet). It has the makings of a great project, I hope it
continues to grow!
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.02623 seconds
] 
Search
Help
Register
Login
Home
