Try the isOpen method. It's possible that will return true even if
the other end is gone away, and if that's the case, then you pretty
much just have to catch the subsequent exception and retry the
connection. It might be kind of nice to have this sort of
functionality in Thrift itself...
-Bryan
On Jun 26, 2009, at 8:07 AM, Oscar wrote:
Hi all,
For the performance issue, I maintained a RPC connection pool.
Before calling a RPC, client borrowed one connection from the pool and
returned the connection after calling the RPC.
Now i have a problem, I don't know the connection is closed after
server-side restarts.
Any suggestions?
thank you very much,
-Oscar
