[ http://issues.apache.org/jira/browse/AXIS2-212?page=all ]
Chamikara Jayalath resolved AXIS2-212:
--------------------------------------
Resolution: Fixed
This is not a bug anymore. Releasing the thread seems to be better than holding
it. Holding will comsume too much resources in the server side.
> calling setPausedTrue() on message contexts causes the incoming thread to
> immediately return.
> ---------------------------------------------------------------------------------------------
>
> Key: AXIS2-212
> URL: http://issues.apache.org/jira/browse/AXIS2-212
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Reporter: Chamikara Jayalath
>
> It seems that the when a handler calls msgCtx.setPausedTrue() the AxisEngine
> causes the incoming thread to immediately return (i.e. it will not invoke any
> handlers after the current handler both in the requst and response path).
> This does not seem to be the correct way for two reasons. (please check the
> logic of AxisEngine.receive() method).
> 1. Some modules (e.g RM) may want to pause the msgCtx and later resume it
> without loosing the current incoming thread.
> 2. Since this does not call any response handlers some functionalities like
> security may get violated
--
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
