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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2005/08/30 07:22:04 UTC
[jira] Created: (AXIS2-191) call.close() logic seems to be incorrect
call.close() logic seems to be incorrect
----------------------------------------
Key: AXIS2-191
URL: http://issues.apache.org/jira/browse/AXIS2-191
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: client-api
Reporter: Deepal Jayasinghe
In the call api there is a method called call.close(), it is there to close the transport listeners , but it seems the underline logic is incorrect.
In the client side if you try to use two channel case ,it check whether the corresponding listener is there if it is not there it will start the listener else you the already started listener , but by in different service invocation if we call call.close(), all the others wont be getting an desired out put ,in fact it will be getting an socket time out exeption , that is because call.close() logic seems to be incorrect.
(Sorry I do not have a test case :( )
--
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
[jira] Resolved: (AXIS2-191) call.close() logic seems to be incorrect
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-191?page=all ]
Eran Chinthaka resolved AXIS2-191:
----------------------------------
Fix Version: 0.94
Resolution: Fixed
I hope with our latest fixes this is not there any more.
> call.close() logic seems to be incorrect
> ----------------------------------------
>
> Key: AXIS2-191
> URL: http://issues.apache.org/jira/browse/AXIS2-191
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Reporter: Deepal Jayasinghe
> Fix For: 0.94
>
> In the call api there is a method called call.close(), it is there to close the transport listeners , but it seems the underline logic is incorrect.
> In the client side if you try to use two channel case ,it check whether the corresponding listener is there if it is not there it will start the listener else you the already started listener , but by in different service invocation if we call call.close(), all the others wont be getting an desired out put ,in fact it will be getting an socket time out exeption , that is because call.close() logic seems to be incorrect.
> (Sorry I do not have a test case :( )
--
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