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 Jonas Rathert <jr...@gmx.de> on 2004/11/05 18:53:18 UTC

Open Sockets on BEA Weblogic 8.1

Hi there,

we are using Apache Axis on a BEA Weblogic Server 8.1 (no SP). Our web
application is calling other web services on other servers:
   - Apache Axis WebServices on another BEA server (using https)
   - .NET WebServices on an IIS (using http)

In our BEA Admin console, we see a large number of "Active Sockets".
Unfortunately, the server does not tell us much nore (e.g. the status of
the socket), and BEA does not provide much more information about these
open sockets as well (they just say: "This page displays IP address and
protocol information for this server's opened sockets.") We *think* that
the open sockets might be caused by the web service calls, but we can not
verify this at the moment.  I am trying to debugging the situation, but
first I want to know

   - if there is there any known situation / scenario where axis may
     leave some open sockets?
   - if there is there any way to increase logging output to debug the
     web service calls?

Any help appreciated. Thanks in advance

    Jonas

-- 
   Note: 96.31% of all statistics are fiction.

Re: Open Sockets on BEA Weblogic 8.1

Posted by Davanum Srinivas <da...@gmail.com>.

Try using CommonsHTTPSender and see if the # of socket drops. It does HTTP1.1.

-- dims


On Fri, 05 Nov 2004 18:53:18 +0100, Jonas Rathert <jr...@gmx.de> wrote:
> Hi there,
> 
> we are using Apache Axis on a BEA Weblogic Server 8.1 (no SP). Our web
> application is calling other web services on other servers:
>    - Apache Axis WebServices on another BEA server (using https)
>    - .NET WebServices on an IIS (using http)
> 
> In our BEA Admin console, we see a large number of "Active Sockets".
> Unfortunately, the server does not tell us much nore (e.g. the status of
> the socket), and BEA does not provide much more information about these
> open sockets as well (they just say: "This page displays IP address and
> protocol information for this server's opened sockets.") We *think* that
> the open sockets might be caused by the web service calls, but we can not
> verify this at the moment.  I am trying to debugging the situation, but
> first I want to know
> 
>    - if there is there any known situation / scenario where axis may
>      leave some open sockets?
>    - if there is there any way to increase logging output to debug the
>      web service calls?
> 
> Any help appreciated. Thanks in advance
> 
>     Jonas
> 
> --
>    Note: 96.31% of all statistics are fiction.
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/