axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vd (JIRA)" <>
Subject [jira] Updated: (AXIS-1716) Axis service stops working after many requests from gSoap client
Date Sat, 11 Dec 2004 05:52:09 GMT
     [ ]

vd updated AXIS-1716:


The attached file is a zip of Netbeans 4.0 project.  Inside it, it also has 2 gSoap VC++ 6.0
projects that has client codes for connecting to the server.

> Axis service stops working after many requests from gSoap client
> ----------------------------------------------------------------
>          Key: AXIS-1716
>          URL:
>      Project: Axis
>         Type: Bug
>     Versions: 1.2RC2
>  Environment: Microsoft Windows XP (SP2)
>     Reporter: vd
>  Attachments:
> When making request repeatedly from a gSoap client to an Axis server, the server will
stop reponse to any request. 
> Please see attachment for the demo of the problem. The demoImpl package includes all
classes needed for deployment.  Also there is an Axis client in there.  In the gSoap folder
(unzip gSoap into this folder to compile and run the client), there are 2 VC++ client projects.
 1 project is C, another is C++.  You can use either one of these. Make sure to change the
number of requests in the gSoap client up to around 20000 requests. After deploy the service,
you can use the Java client (included) to make a call for sanity check.  Next, run the gSoap
client with couple requests first (change the for loop).  Next, change the for loop to about
20000 then run the client.  Wait until there is no output other than error is printed, stop.
 Next, run the Java client and you'll see the error message below.
> Here's the error message when trying to make request on the server using an Axis client
after the server has been hitted by many gSoap client requests:
> AxisFault
>  faultCode: {}Server.userException
>  faultSubcode: 
>  faultString: Address already in use: connect
>  faultActor: 
>  faultNode: 
>  faultDetail: 
>     {} Address already in
use: connect
>     at Method)
>     at
>     at
>     at
>     at
>     at
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>     at java.lang.reflect.Method.invoke(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message