Robert
http://www.braziloutsource.com/
On 3/13/06, Deepal Jayasinghe (JIRA) <
[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/AXIS2-304?page=all ]
Deepal Jayasinghe resolved AXIS2-304:
-------------------------------------
Fix Version: 0.95
Resolution: Fixed
- Clien side is sloved with ServiceClinet.firAndForget()
- In the server side , if you use Async message receiver then you are done
> InOnly MEP blocks the caller till the operation finishes.......
> ---------------------------------------------------------------
>
> Key: AXIS2-304
> URL: http://issues.apache.org/jira/browse/AXIS2-304
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Reporter: Thilina Gunarathne
> Fix For: 0.95
>
> The above behaviour of the InOnly MEP causes the long running activities to timeout + It's ruining the advantages behind one way messaging......
> Quoting Dr.Sanjiva,
> when we get a message after dispatch is finished we know the MEP. If the MEP is In-Only, then we should immediately hand over the delivery of the message to a thread and return the original thread
> Related to the following threads in the Dev list,
> http://www.opensubscriber.com/message/[email protected]/2572316.html
> http://www.opensubscriber.com/message/[email protected]/2296180.html
> Fixing this might help to overcome the following in User list,
> http://www.opensubscriber.com/message/[email protected]/2464960.html
--
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
