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 "AravindPS (JIRA)" <ji...@apache.org> on 2012/11/12 11:19:12 UTC
[jira] [Created] (AXIS2-5453) Threads not getting closed at server
side on High Load.
AravindPS created AXIS2-5453:
--------------------------------
Summary: Threads not getting closed at server side on High Load.
Key: AXIS2-5453
URL: https://issues.apache.org/jira/browse/AXIS2-5453
Project: Axis2
Issue Type: Bug
Components: client-api
Affects Versions: 1.6.2, 1.5.5
Environment: OS: win2k R2 server
App server: apache-tomcat-7.0.32-windows-x64
Axis2 version:- Axis2 1.5.5 at server side AND Axis2 1.6.2 at client side.
Web service stubs generated using Axis2 1.6.2 jar files with ADB data binding.
Reporter: AravindPS
Attachments: catalina.2012-11-12.log
Hi,
We are doing a load test on web Services. When we run a test for 25 thread and 25 cycles per thread with each cycle processing a few web service requests, we are seeing that the number of threads for tomcat server is reaching the max limit of 300 and the threads are not closed automatically by client side or server side. The stubs are generated using the ADB databinding. We are using new instance of the stub for different threads. We are sending the requests from a single host.
Some config on client side include:
-------------------------------------------------------------------------------------------------------------------------
MultiThreadedHttpConnectionManager httpConnectionManager = new MultiThreadedHttpConnectionManager();
HttpClient httpClient = new HttpClient(httpConnectionManager);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Constants.VALUE_TRUE);
HttpConnectionManagerParams params = new HttpConnectionManagerParams();
params.setDefaultMaxConnectionsPerHost(100); /* 20 per host is fine in practical scenario */
params.setMaxTotalConnections(300);
httpConnectionManager.setParams(params);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, 10000);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, 10000);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED, "false");
// to avoid retries
HttpMethodParams methodParams = new HttpMethodParams();
DefaultHttpMethodRetryHandler retryHandler = new DefaultHttpMethodRetryHandler(0, false);
methodParams.setParameter(HttpMethodParams.RETRY_HANDLER, retryHandler);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.HTTP_METHOD_PARAMS, methodParams);
-------------------------------------------------------------------------------------------------------------------------
After running the threads I am calling:
-----------------------------------------------------------------------------
stub._getServiceClient().cleanupTransport();
stub._getServiceClient().cleanup();
stub.cleanup();
httpConnectionManager.closeIdleConnections(0);
httpConnectionManager.deleteClosedConnections();
httpConnectionManager.shutdown();
stub = null;
httpConnectionManager = null;
-----------------------------------------------------------------------------
After each web service call I am calling:
-----------------------------------------------------------------
stub._getServiceClient().cleanupTransport();
-----------------------------------------------------------------
When I shutdown the tomcat, I am getting 'severe' errors in the Tomcat log "catalina.2012-11-12.log". I have attached the log. All the threads are in "Waiting" state. I am not able to close the threads and server gets hanged and it cannot process any new requests.
Regards,
Aravind
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5453) Threads not getting closed at server
side on High Load.
Posted by "AravindPS (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
AravindPS updated AXIS2-5453:
-----------------------------
Attachment: catalina.2012-11-12.log
Shutdown log tomcat
> Threads not getting closed at server side on High Load.
> -------------------------------------------------------
>
> Key: AXIS2-5453
> URL: https://issues.apache.org/jira/browse/AXIS2-5453
> Project: Axis2
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.5.5, 1.6.2
> Environment: OS: win2k R2 server
> App server: apache-tomcat-7.0.32-windows-x64
> Axis2 version:- Axis2 1.5.5 at server side AND Axis2 1.6.2 at client side.
> Web service stubs generated using Axis2 1.6.2 jar files with ADB data binding.
> Reporter: AravindPS
> Labels: adb-codegen, client, load
> Attachments: catalina.2012-11-12.log
>
>
> Hi,
> We are doing a load test on web Services. When we run a test for 25 thread and 25 cycles per thread with each cycle processing a few web service requests, we are seeing that the number of threads for tomcat server is reaching the max limit of 300 and the threads are not closed automatically by client side or server side. The stubs are generated using the ADB databinding. We are using new instance of the stub for different threads. We are sending the requests from a single host.
> Some config on client side include:
> -------------------------------------------------------------------------------------------------------------------------
> MultiThreadedHttpConnectionManager httpConnectionManager = new MultiThreadedHttpConnectionManager();
> HttpClient httpClient = new HttpClient(httpConnectionManager);
> stub._getServiceClient().getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Constants.VALUE_TRUE);
> HttpConnectionManagerParams params = new HttpConnectionManagerParams();
> params.setDefaultMaxConnectionsPerHost(100); /* 20 per host is fine in practical scenario */
> params.setMaxTotalConnections(300);
> httpConnectionManager.setParams(params);
> stub._getServiceClient().getOptions().setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient);
> stub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, 10000);
> stub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, 10000);
> stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED, "false");
>
> // to avoid retries
> HttpMethodParams methodParams = new HttpMethodParams();
> DefaultHttpMethodRetryHandler retryHandler = new DefaultHttpMethodRetryHandler(0, false);
> methodParams.setParameter(HttpMethodParams.RETRY_HANDLER, retryHandler);
> stub._getServiceClient().getOptions().setProperty(HTTPConstants.HTTP_METHOD_PARAMS, methodParams);
> -------------------------------------------------------------------------------------------------------------------------
> After running the threads I am calling:
> -----------------------------------------------------------------------------
> stub._getServiceClient().cleanupTransport();
> stub._getServiceClient().cleanup();
> stub.cleanup();
> httpConnectionManager.closeIdleConnections(0);
> httpConnectionManager.deleteClosedConnections();
> httpConnectionManager.shutdown();
> stub = null;
> httpConnectionManager = null;
> -----------------------------------------------------------------------------
> After each web service call I am calling:
> -----------------------------------------------------------------
> stub._getServiceClient().cleanupTransport();
> -----------------------------------------------------------------
> When I shutdown the tomcat, I am getting 'severe' errors in the Tomcat log "catalina.2012-11-12.log". I have attached the log. All the threads are in "Waiting" state. I am not able to close the threads and server gets hanged and it cannot process any new requests.
> Regards,
> Aravind
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org