> Is it considered safe to interrupt the execute task that way? Is > method.releaseConnection() the way to go for full cleanup of > underlying resources, or the interruption might leave things in a > bad state?
There's no definitive answer to this question. TimeoutController does not actually interrupt the method execution. All is does is leaving the client object at the mercy of garbage collector. The client may linger in the memory until the second coming or get GCed in a reasonable amount of time. The exact behaviour is unfortunately JRE specific. Oleg *************************************************************************************************** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *************************************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
