https://issues.apache.org/bugzilla/show_bug.cgi?id=54230

--- Comment #5 from Kurt Hong <[email protected]> ---
(In reply to comment #4)
> I'm not sure how the new "Close Connection" option helps.
At the moment, there is no way to control connections in TCP Sampler on behalf
of client. 

Even if the server close the connection, the connection will not be closed
immediately. There could effect next loop of the thread. 

In our case, sending "quit" message to server, the server ideally responds
"bye" and close the connection. But the response also could be an event message
which is made by another sampler of another thread, asynchronously. Then the
first sampler of next loop could try to send message to the closed socket. 

So I thought it would be better if we can control the connection on client
behalf. 

> Surely, just deselecting "Re-use connection" has the same effect? 
Yes, if you deselect "Re-Use Connection", the "Close connection" checkbox will
be disabled, set as "checked" on GUI.

> The method getSoLingerTimeut() is misspelt, but that could be easily fixed.
Sorry for that. I will fix that.

> Also, I don't think one needs both the boolean SO linger and the Linger
> timeout fields on the GUI.
> 
> If the timeout field is non-empty, only then set SO linger. The
> documentation needs to make it clear that the linger timeout is only applied
> when the socket is created.
Yes, I think that's good idea. I'll apply that.

(In reply to comment #4)
> I'm not sure how the new "Close Connection" option  helps.
> 
> Surely, just deselecting "Re-use connection" has the same effect?
> 
> The method getSoLingerTimeut() is misspelt, but that could be easily fixed.
> 
> Also, I don't think one needs both the boolean SO linger and the Linger
> timeout fields on the GUI.
> 
> If the timeout field is non-empty, only then set SO linger. The
> documentation needs to make it clear that the linger timeout is only applied
> when the socket is created.

(In reply to comment #4)
> I'm not sure how the new "Close Connection" option  helps.
> 
> Surely, just deselecting "Re-use connection" has the same effect?
> 
> The method getSoLingerTimeut() is misspelt, but that could be easily fixed.
> 
> Also, I don't think one needs both the boolean SO linger and the Linger
> timeout fields on the GUI.
> 
> If the timeout field is non-empty, only then set SO linger. The
> documentation needs to make it clear that the linger timeout is only applied
> when the socket is created.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to