Return-Path: Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 29806 invoked by uid 500); 17 Mar 2003 16:51:54 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 29746 invoked from network); 17 Mar 2003 16:51:53 -0000 Message-ID: From: "Davis, Kevin" To: "'axis-user@ws.apache.org'" Subject: RE: HTTP Connections Hanging Date: Mon, 17 Mar 2003 11:50:33 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Anyone else have any suggestions, workarounds for this? Kevin -----Original Message----- From: Davis, Kevin Sent: Friday, March 14, 2003 1:19 PM To: 'axis-user@ws.apache.org' Subject: RE: HTTP Connections Hanging I think much of the issue I'm having is around the bug pertaining to Xerces/Axis still holding the connection open to ensure that all the bytes have been recieved. But it does sound similar, but I'm letting Axis do all the socket stuff. Kevin -----Original Message----- From: Kevin.Bedell@sunlife.com [mailto:Kevin.Bedell@sunlife.com] Sent: Friday, March 14, 2003 11:35 AM To: axis-user@ws.apache.org Subject: Re: HTTP Connections Hanging I ran into a similar problem using Weblogic while doing some low-level TCP socket communications. It turns out that whenever a socket timeout occured I was handling the Exception - but not specifically 'closing' the socket in a "finally{}" clause. As a result the sockets chewed up my weblogic threads until they were gone. Not sure if this applies exactly - it may be a piece of the puzzle... Kevin "Davis, Kevin" To: "'axis-user@ws.apache.org'" cc: (bcc: Kevin Bedell/Systems/USHO/SunLife) 03/14/2003 10:53 AM Subject: HTTP Connections Hanging Please respond to axis-user I've been looking through the past messages and the Apache Axis bugzilla database and it appears that the issue surrounding HTTP Connections "hanging" is a known issue. What is the easiest way to get around this issue? I'm expieriencing some rather interesting problems surrounding this. I have an app, running on Weblogic 7.0.1 using an Axis client to call a MS-SOAP C++ service on Win2K. I am noticing the thread count in Weblogic continues to grow steadily over time and eventually runs out. After doing a thread dump, Weblogic shows that all of those thread are in the Axis Client "hanging" waiting for the HTTP connection to close. Any suggestions would be appreciated. Kevin Davis --------------------------------------------------------------------------- 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. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ---------------------------------------------------------------------------