You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "vd (JIRA)" <ax...@ws.apache.org> on 2004/12/11 06:41:17 UTC

[jira] Created: (AXIS-1716) Axis service stops working after many requests from gSoap client

Axis service stops working after many requests from gSoap client
----------------------------------------------------------------

         Key: AXIS-1716
         URL: http://nagoya.apache.org/jira/browse/AXIS-1716
     Project: Axis
        Type: Bug
    Versions: 1.2RC2    
 Environment: Microsoft Windows XP (SP2)
    Reporter: vd


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: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.net.BindException: Address already in use: connect
 faultActor: 
 faultNode: 
 faultDetail: 
    {http://xml.apache.org/axis/}stackTrace:java.net.BindException: Address already in use: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
    at java.net.Socket.connect(Socket.java:507)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Commented: (AXIS-1716) Axis service stops working after many requests from gSoap client

Posted by "vd (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXIS-1716?page=comments#action_56753 ]
     
vd commented on AXIS-1716:
--------------------------

Please close the issue as invalid.

The problem was caused by the number of ephemeral port limit was reached (5000).

Under Windows XP environment, this problem can be solved by doing one or both of these things:

1) change the limit to higher (max is 65534)
2) reduce the TIME_WAIT (min is 30 seconds)

Step 2 is abit risky, because it could increase network error.

The procedure for doing the above steps can be found at MS knowledge base (change registry settings and  restart the computer).

> Axis service stops working after many requests from gSoap client
> ----------------------------------------------------------------
>
>          Key: AXIS-1716
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1716
>      Project: Axis
>         Type: Bug
>     Versions: 1.2RC2
>  Environment: Microsoft Windows XP (SP2)
>     Reporter: vd
>  Attachments: AxisDemo.zip
>
> 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: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode: 
>  faultString: java.net.BindException: Address already in use: connect
>  faultActor: 
>  faultNode: 
>  faultDetail: 
>     {http://xml.apache.org/axis/}stackTrace:java.net.BindException: Address already in use: connect
>     at java.net.PlainSocketImpl.socketConnect(Native Method)
>     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
>     at java.net.Socket.connect(Socket.java:507)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:585)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (AXIS-1716) Axis service stops working after many requests from gSoap client

Posted by "vd (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXIS-1716?page=history ]

vd updated AXIS-1716:
---------------------

    Attachment: AxisDemo.zip

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: http://nagoya.apache.org/jira/browse/AXIS-1716
>      Project: Axis
>         Type: Bug
>     Versions: 1.2RC2
>  Environment: Microsoft Windows XP (SP2)
>     Reporter: vd
>  Attachments: AxisDemo.zip
>
> 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: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode: 
>  faultString: java.net.BindException: Address already in use: connect
>  faultActor: 
>  faultNode: 
>  faultDetail: 
>     {http://xml.apache.org/axis/}stackTrace:java.net.BindException: Address already in use: connect
>     at java.net.PlainSocketImpl.socketConnect(Native Method)
>     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
>     at java.net.Socket.connect(Socket.java:507)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:585)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Resolved: (AXIS-1716) Axis service stops working after many requests from gSoap client

Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXIS-1716?page=history ]
     
Davanum Srinivas resolved AXIS-1716:
------------------------------------

    Resolution: Fixed

Invalid Issue as per prev comment.

> Axis service stops working after many requests from gSoap client
> ----------------------------------------------------------------
>
>          Key: AXIS-1716
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1716
>      Project: Axis
>         Type: Bug
>     Versions: 1.2RC2
>  Environment: Microsoft Windows XP (SP2)
>     Reporter: vd
>  Attachments: AxisDemo.zip
>
> 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: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode: 
>  faultString: java.net.BindException: Address already in use: connect
>  faultActor: 
>  faultNode: 
>  faultDetail: 
>     {http://xml.apache.org/axis/}stackTrace:java.net.BindException: Address already in use: connect
>     at java.net.PlainSocketImpl.socketConnect(Native Method)
>     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
>     at java.net.Socket.connect(Socket.java:507)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:585)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira