You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by seanc <se...@gmail.com> on 2007/03/20 00:16:43 UTC
Axis2 Client, JVM Hangs- Recommended stopgap solution for JIRA
AXIS2-935
http://issues.apache.org/jira/browse/AXIS2-935
I was wondering if anyone had come across a recommended way to work around
the issues listed in this bug. Right now, this causes our JVMs to hang.
In all cases, it seems recommended from a performance and memory standpoint
to cache the ConfigurationContext object, but this issue is more or less a
showstopper if you plan to use either the single or multithreaded HTTPSender
objects for calling your Axis2 server instance.
We basically get a hung JVM once we've crossed some threshold either tied to
pooled httpclient objects or open file descriptors, that sometimes clears
itself. (after an unidentified period of time)
Ideally, it would be great if we could definitively answer this question:
If REUSE_HTTP_CLIENT, is there a way to get rid of the CLOSE_WAIT file
descriptors other than garbage collect?
--
View this message in context: http://www.nabble.com/Axis2-Client%2C-JVM-Hangs--Recommended-stopgap-solution-for-JIRA-AXIS2-935-tf3430423.html#a9563019
Sent from the Apache SOAP - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@ws.apache.org
For additional commands, e-mail: soap-user-help@ws.apache.org
Re: Axis2 Client, JVM Hangs- Recommended stopgap solution for JIRA
AXIS2-935
Posted by seanc <se...@gmail.com>.
Martin..
thanks, will certainly try to determine our feasiblity to upgrade to JDK
version listed.
Just for reference, if we had to modify the code itself, what class within
the axis2 stack would we be dealing with in order to patch the code snippet
below? Im assuming something within commons http client?
Sean
Martin Gainty wrote:
>
> Sean-
>
> This is an acknowledged bug fixed in 5.0u7 and Mustang
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6215050
> if you upgrade to JDK/JVM 5.0u7 (JDK/JVM 5.0 Update 7) or JVM/JDK 6
> (Mustang)
>
> OR
> //configure the InputStream to close ..and disable the OutputStream
> sChannel.socket().shutdownInput(); //Place EOS in InputStream
> sChannel.socket().shutdownOutput(); //Disable OutputStream for the socket
>
> //close the socket
> sChannel.close();
>
> HTH,
> M--
> ---------------------------------------------------------------------------
> This e-mail message (including attachments, if any) is intended for the
> use of the individual or entity to which it is addressed and may contain
> information that is privileged, proprietary , confidential and exempt from
> disclosure. If you are not the intended recipient, you are notified that
> any dissemination, distribution or copying of this communication is
> strictly prohibited.
> ---------------------------------------------------------------------------
> Le présent message électronique (y compris les pièces qui y sont annexées,
> le cas échéant) s'adresse au destinataire indiqué et peut contenir des
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
> destinataire de ce document, nous vous signalons qu'il est strictement
> interdit de le diffuser, de le distribuer ou de le reproduire.
> ----- Original Message -----
> From: "seanc" <se...@gmail.com>
> To: <so...@ws.apache.org>
> Sent: Monday, March 19, 2007 7:16 PM
> Subject: Axis2 Client, JVM Hangs- Recommended stopgap solution for JIRA
> AXIS2-935
>
>
>>
>> http://issues.apache.org/jira/browse/AXIS2-935
>>
>> I was wondering if anyone had come across a recommended way to work
>> around
>> the issues listed in this bug. Right now, this causes our JVMs to hang.
>>
>> In all cases, it seems recommended from a performance and memory
>> standpoint
>> to cache the ConfigurationContext object, but this issue is more or less
>> a
>> showstopper if you plan to use either the single or multithreaded
>> HTTPSender
>> objects for calling your Axis2 server instance.
>>
>> We basically get a hung JVM once we've crossed some threshold either tied
>> to
>> pooled httpclient objects or open file descriptors, that sometimes clears
>> itself. (after an unidentified period of time)
>>
>> Ideally, it would be great if we could definitively answer this question:
>> If REUSE_HTTP_CLIENT, is there a way to get rid of the CLOSE_WAIT file
>> descriptors other than garbage collect?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-Client%2C-JVM-Hangs--Recommended-stopgap-solution-for-JIRA-AXIS2-935-tf3430423.html#a9563019
>> Sent from the Apache SOAP - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: soap-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: soap-user-help@ws.apache.org
>>
>>
>
--
View this message in context: http://www.nabble.com/Axis2-Client%2C-JVM-Hangs--Recommended-stopgap-solution-for-JIRA-AXIS2-935-tf3430423.html#a9565307
Sent from the Apache SOAP - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@ws.apache.org
For additional commands, e-mail: soap-user-help@ws.apache.org
Re: Axis2 Client, JVM Hangs- Recommended stopgap solution for JIRA AXIS2-935
Posted by Martin Gainty <mg...@hotmail.com>.
Sean-
This is an acknowledged bug fixed in 5.0u7 and Mustang
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6215050
if you upgrade to JDK/JVM 5.0u7 (JDK/JVM 5.0 Update 7) or JVM/JDK 6 (Mustang)
OR
//configure the InputStream to close ..and disable the OutputStream
sChannel.socket().shutdownInput(); //Place EOS in InputStream
sChannel.socket().shutdownOutput(); //Disable OutputStream for the socket
//close the socket
sChannel.close();
HTH,
M--
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: "seanc" <se...@gmail.com>
To: <so...@ws.apache.org>
Sent: Monday, March 19, 2007 7:16 PM
Subject: Axis2 Client, JVM Hangs- Recommended stopgap solution for JIRA AXIS2-935
>
> http://issues.apache.org/jira/browse/AXIS2-935
>
> I was wondering if anyone had come across a recommended way to work around
> the issues listed in this bug. Right now, this causes our JVMs to hang.
>
> In all cases, it seems recommended from a performance and memory standpoint
> to cache the ConfigurationContext object, but this issue is more or less a
> showstopper if you plan to use either the single or multithreaded HTTPSender
> objects for calling your Axis2 server instance.
>
> We basically get a hung JVM once we've crossed some threshold either tied to
> pooled httpclient objects or open file descriptors, that sometimes clears
> itself. (after an unidentified period of time)
>
> Ideally, it would be great if we could definitively answer this question:
> If REUSE_HTTP_CLIENT, is there a way to get rid of the CLOSE_WAIT file
> descriptors other than garbage collect?
>
> --
> View this message in context: http://www.nabble.com/Axis2-Client%2C-JVM-Hangs--Recommended-stopgap-solution-for-JIRA-AXIS2-935-tf3430423.html#a9563019
> Sent from the Apache SOAP - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: soap-user-help@ws.apache.org
>
>