axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thilina Gunarathne (JIRA)" <>
Subject [jira] Commented: (AXIS2-304) InOnly MEP blocks the caller till the operation finishes.......
Date Tue, 15 Nov 2005 15:56:28 GMT
    [ ] 

Thilina Gunarathne commented on AXIS2-304:

A bit of thinking on to this issue gave me the following ideas.....

1. We need a MessageSender(MessageSender handles Robust OutOnly) counterpart which will handle
the OutOnly MEP from the client side.... So that we can use that for Asynchronous two channel

2. We need a InOnlyMepClient (May be we should rename this to RobustInOnly....) counterpart
on the server side which will handle the InOnly MEP....So that we can use that for one way
messaging scenerios. This should work fine even when the client is using a RobustOutOnly Mep.....

3. A suggestion :: Can we release the  calling thread in all cases when the incoming message
has a replyTo EPR.... 

Pls comment..

> InOnly MEP blocks the caller till the operation finishes.......
> ---------------------------------------------------------------
>          Key: AXIS2-304
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: core
>     Reporter: Thilina Gunarathne

> 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,
> Fixing this might help to overcome the following in User list,

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message