You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Paulo Henrique <pa...@adplabs.com.br> on 2006/11/11 16:33:57 UTC
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: About HTTPSender not closing the Socket
Posted by Paulo Henrique <pa...@adplabs.com.br>.
I can tell you that we call the same webservices (host/port/service)
multiple times in different threads...
Does it can be causing this delay on the Fin,Ack ? Have you seen this kind
of problem before?
BTW, current value is (looks like a resource bundle):
optionTimeout00=timeout in seconds (default is 45, specify -1 to disable)
Martin Gainty wrote:
>
> 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" <pa...@adplabs.com.br>
> To: <ax...@ws.apache.org>
> 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" <pa...@adplabs.com.br>
>>> To: <ax...@ws.apache.org>
>>> 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: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>>
>>>
>>
>> --
>> 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: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
--
View this message in context: http://www.nabble.com/About-HTTPSender-not-closing-the-Socket-tf2613265.html#a7310568
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: About HTTPSender not closing the Socket
Posted by Martin Gainty <mg...@hotmail.com>.
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" <pa...@adplabs.com.br>
To: <ax...@ws.apache.org>
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" <pa...@adplabs.com.br>
>> To: <ax...@ws.apache.org>
>> 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: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>
> --
> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: About HTTPSender not closing the Socket
Posted by Paulo Henrique <pa...@adplabs.com.br>.
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" <pa...@adplabs.com.br>
> To: <ax...@ws.apache.org>
> 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: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
--
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: About HTTPSender not closing the Socket
Posted by Martin Gainty <mg...@hotmail.com>.
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" <pa...@adplabs.com.br>
To: <ax...@ws.apache.org>
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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>