You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Damitha Kumarage (JIRA)" <ji...@apache.org> on 2007/03/05 10:18:50 UTC
[jira] Created: (SANDESHA2C-28) Terminate message is sent twice
Terminate message is sent twice
-------------------------------
Key: SANDESHA2C-28
URL: https://issues.apache.org/jira/browse/SANDESHA2C-28
Project: Sandesha2/C
Issue Type: Bug
Reporter: Damitha Kumarage
Assigned To: Damitha Kumarage
When RM 1.0 two way single channel message's are sent eg.rm_mtom_1_0 the terminate message is sent twice.
If I do as the first comment in axis2c-545 then this won't happen. But then after several sends the client segfaults at
if (out_msg_ctx && in_msg_ctx)
{
/* may be this is the second invocation using the same service clinet,
so reset */
AXIS2_MSG_CTX_FREE(out_msg_ctx, env);
out_msg_ctx = NULL;
msg_ctx_map[AXIS2_WSDL_MESSAGE_LABEL_OUT] = NULL;
AXIS2_MSG_CTX_FREE(in_msg_ctx, env);
in_msg_ctx = NULL;
msg_ctx_map[AXIS2_WSDL_MESSAGE_LABEL_IN] = NULL;
AXIS2_OP_CTX_SET_IS_COMPLETE(op_client_impl->op_ctx, env, AXIS2_FALSE);
}
when it try to free in_msg_ctx. This happen when it try to free AXIS2_TRANSPORT_IN property.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2C-28) Terminate message is sent twice
Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2C-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damitha Kumarage resolved SANDESHA2C-28.
----------------------------------------
Resolution: Fixed
This is fixed by changing mep_client. This happen because engine_receive is called twice. I fixed mep_client such that it check a property set in sandesha2_global_in_handler and avoid calling engine_receive but just return the response context.
> Terminate message is sent twice
> -------------------------------
>
> Key: SANDESHA2C-28
> URL: https://issues.apache.org/jira/browse/SANDESHA2C-28
> Project: Sandesha2/C
> Issue Type: Bug
> Reporter: Damitha Kumarage
> Assigned To: Damitha Kumarage
>
> When RM 1.0 two way single channel message's are sent eg.rm_mtom_1_0 the terminate message is sent twice.
> If I do as the first comment in axis2c-545 then this won't happen. But then after several sends the client segfaults at
> if (out_msg_ctx && in_msg_ctx)
> {
> /* may be this is the second invocation using the same service clinet,
> so reset */
> AXIS2_MSG_CTX_FREE(out_msg_ctx, env);
> out_msg_ctx = NULL;
> msg_ctx_map[AXIS2_WSDL_MESSAGE_LABEL_OUT] = NULL;
> AXIS2_MSG_CTX_FREE(in_msg_ctx, env);
> in_msg_ctx = NULL;
> msg_ctx_map[AXIS2_WSDL_MESSAGE_LABEL_IN] = NULL;
> AXIS2_OP_CTX_SET_IS_COMPLETE(op_client_impl->op_ctx, env, AXIS2_FALSE);
> }
> when it try to free in_msg_ctx. This happen when it try to free AXIS2_TRANSPORT_IN property.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2C-28) Terminate message is sent twice
Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2C-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damitha Kumarage resolved SANDESHA2C-28.
----------------------------------------
Resolution: Fixed
This is fixed by changing mep_client. This happen because engine_receive is called twice. I fixed mep_client such that it check a property set in sandesha2_global_in_handler and avoid calling engine_receive but just return the response context.
> Terminate message is sent twice
> -------------------------------
>
> Key: SANDESHA2C-28
> URL: https://issues.apache.org/jira/browse/SANDESHA2C-28
> Project: Sandesha2/C
> Issue Type: Bug
> Reporter: Damitha Kumarage
> Assigned To: Damitha Kumarage
>
> When RM 1.0 two way single channel message's are sent eg.rm_mtom_1_0 the terminate message is sent twice.
> If I do as the first comment in axis2c-545 then this won't happen. But then after several sends the client segfaults at
> if (out_msg_ctx && in_msg_ctx)
> {
> /* may be this is the second invocation using the same service clinet,
> so reset */
> AXIS2_MSG_CTX_FREE(out_msg_ctx, env);
> out_msg_ctx = NULL;
> msg_ctx_map[AXIS2_WSDL_MESSAGE_LABEL_OUT] = NULL;
> AXIS2_MSG_CTX_FREE(in_msg_ctx, env);
> in_msg_ctx = NULL;
> msg_ctx_map[AXIS2_WSDL_MESSAGE_LABEL_IN] = NULL;
> AXIS2_OP_CTX_SET_IS_COMPLETE(op_client_impl->op_ctx, env, AXIS2_FALSE);
> }
> when it try to free in_msg_ctx. This happen when it try to free AXIS2_TRANSPORT_IN property.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org