[ http://issues.apache.org/jira/browse/AXIS2-502?page=all ]
Deepal Jayasinghe resolved AXIS2-502:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
I think I regenerate the problem , and found that the additional thread
creation taking place due to following two reasons.
1.Underline thread pool
2.Setting Keep-alive HTTP header by default , even if we are not using that at
the client side
So I removed the keep alive problem and after that it worked for me :)
Any way please check whether you still have the problem , if so re-create the
JIRA (pls dont put the priority to blocker :) )
> unclosed threads
> ----------------
>
> Key: AXIS2-502
> URL: http://issues.apache.org/jira/browse/AXIS2-502
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api, core
> Versions: 0.94
> Environment: P4, Windows XP Pro, Java JDK 1.5.0_06
> Reporter: dil emma
> Priority: Blocker
> Fix For: 0.95
>
> A method (web service) invoks two other web services:
> final String ENDPOINT1 = "http://...";;
> public String say(String data) {
> //first call
> String endpoint2 = invokeEchoBlocking(ENDPOINT1, "say", data);
> //second call
> String result = invokeEchoBlocking(endpoint2, "say", data);
> return result;
> }
> On every invocation two new threads arise visible in the Task-Manager
> of Windows; they don't close. Axis 1.3 don't show this behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
