[Sblim-issues] [ sblim-Bugs-1647148 ] HttpClient.resetSocket() doesn't set socket timeout

[SourceForge.net <no...@so...>]

Bugs item #1647148, was opened at 2007-01-29 15:43
Message generated for change (Settings changed) made by lupusalex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=1647148&group_id=128809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Java Client
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: lupusalex (lupusalex)
Assigned to: lupusalex (lupusalex)
Summary: HttpClient.resetSocket() doesn't set socket timeout

Initial Comment:
When a socket is reused the resetSocket() method doesn't set the socket timeout to the current value from the session properties. This prevents code like this:

set timeout to 60s
enumerateInstances
set timeout to 60000s
invokeMethod

Especially TPC uses long timeouts for extrinsic method calls of providers that have long-running synchronous methods. They don't want to apply these timeouts to usual enumentations and association traversal. 

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

Comment By: lupusalex (lupusalex)
Date: 2007-01-30 08:43

Message:
Logged In: YES 
user_id=1363884
Originator: YES

We've a couple of patches that build on each other (1646434, 1647148,
1647159). Please forgive that this time I didn't prepare patches against
1.3.1 but Experimental.
File Added: patch_1647148_head.txt

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=1647148&group_id=128809