You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Damitha Kumarage (JIRA)" <ji...@apache.org> on 2007/03/07 12:14:24 UTC

[jira] Resolved: (AXIS2C-545) Sandesha2 in handler is called twice

     [ https://issues.apache.org/jira/browse/AXIS2C-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damitha Kumarage resolved AXIS2C-545.
-------------------------------------

    Resolution: Fixed
      Assignee: Damitha Kumarage

I just set a property AXIS2_HANDLER_ALREADY_VISITED after the incoming phases are passed from sandesha2c. So in mep_client I can check this property and avoid passing to the engine_receive again. Instead just return the response message context

> Sandesha2 in handler is called twice
> ------------------------------------
>
>                 Key: AXIS2C-545
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-545
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Damitha Kumarage
>         Assigned To: Damitha Kumarage
>         Attachments: mep_client.c.diff
>
>
> In RM 1.0 two way single channel scenario when it come to mep_client's engine_two_way_send function's engine_receive call the sandesha2_global_in_handler is already visited. So when engine_receive is called sandesha2_global_in_handler will be called twice. RM 1. 0 two way single channel implementation is a hack in sandesha2c to allow to do two way messaging in a single channel in RM. As a result this kind of unexpected difficulties arise. As a solution I can set a property  SANDESHA2_HANDLER_ALREADY_VISITED in axis2_msg_ctx  when the global in handler is visited once. So I can check this property from global_in_handler when it is visted again in the same response channel. To do that I need to do a small change
> in mep_client.c The changes is that I need to get the property map from msg_ctx and set it in response.
> If anybody see a better solution please let me know.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org