Forums Register Login

RMI: Connection timeout on client

+Pie Number of slices to send: Send
Guys, those of you who used RMI, how did you handle the connection timeout issues on client side? Does it make sense to start timer immediately before the the remote call was made to abort the connection that has taken longer then some certain amount of time?
+Pie Number of slices to send: Send
I think most of us do not handle this case as it is considered out of the scope of the application (by most people).
+Pie Number of slices to send: Send
I did not implement any "extra" functionality to handle this.
If the remote call would time out I'm just showing an "error dialog".
Always! Wait. Never. Shut up. Look at this tiny ad.
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 851 times.
Similar Threads
why is it necessary for unLock() to check clientID?
LockManager ... Timeout
Passed 150/155
timeout for client
cleanup on session expiring
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 10:10:08.