Paulo-

did you ensure that there are no other listeners on that socket?
where Port is the Port number assigned to your connector..
netstat -a | grep <Port>

in any case timeout should be set to 0 for 'infinite' ..

M-

This e-mail communication and any attachments may contain confidential and 
privileged information for the use of the 
designated recipients named above. If you are not the intended recipient, you 
are hereby notified that you have received
this communication in error and that any review, disclosure, dissemination, 
distribution or copying of it or its 
contents
----- Original Message ----- 
From: "Paulo Henrique" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, November 12, 2006 3:43 PM
Subject: Re: About HTTPSender not closing the Socket


> 
> 
> Are you sure? That looks like a resource bundle for i18n purposes... I'm
> looking at:
> 
> src\org\apache\axis\i18n\resource.properties
> 
> I didn't understand, should I change that property to (for instance)
> 
> optionTimeout00=2
> 
> ?
> 
> Thanks,
> 
> Paulo
> 
> 
> 
> Martin Gainty wrote:
>> 
>> Paolo-
>> 
>> Have you looked at modifying optionTimeout00 in resources.properties?
>> 
>> M-
>> This e-mail communication and any attachments may contain confidential and
>> privileged information for the use of the 
>> designated recipients named above. If you are not the intended recipient,
>> you are hereby notified that you have received
>> this communication in error and that any review, disclosure,
>> dissemination, distribution or copying of it or its 
>> contents
>> ----- Original Message ----- 
>> From: "Paulo Henrique" <[EMAIL PROTECTED]>
>> To: <[email protected]>
>> Sent: Saturday, November 11, 2006 10:33 AM
>> Subject: About HTTPSender not closing the Socket
>> 
>> 
>>> 
>>> Hi,
>>> 
>>> we use Axis 1.1 and are having some problems with TCP connections (there
>>> is
>>> a big delay right before the last Fin,Ack of the TCP connection). 
>>> Then I took a look at the HTTPSender class and saw that the invoke method
>>> does not close the socket after using it (in a "finally" clause, for
>>> instance).
>>> 
>>> That is possibly causing problems in our application, cause sometimes the
>>> last Fin,Ack is delaying a lot (such as 7s) and causing us performance
>>> problems...
>>> 
>>> So, I would like to know if there is any reason why close() is not being
>>> called after the Socket is used. 
>>> 
>>> Any help will be appreciated,
>>> 
>>> Thanks in advance,
>>> 
>>> Paulo
>>> 
>>> -- 
>>> View this message in context:
>>> http://www.nabble.com/About-HTTPSender-not-closing-the-Socket-tf2613265.html#a7293646
>>> Sent from the Axis - User mailing list archive at Nabble.com.
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>> 
>>>
>> 
> 
> -- 
> View this message in context: 
> http://www.nabble.com/About-HTTPSender-not-closing-the-Socket-tf2613265.html#a7307218
> Sent from the Axis - User mailing list archive at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Reply via email to