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 "Manjula Peiris (JIRA)" <ji...@apache.org> on 2007/11/21 05:37:43 UTC

[jira] Commented: (SANDESHA2C-34) when rm_ping client fails to run again correctly the data base need clean up.

    [ https://issues.apache.org/jira/browse/SANDESHA2C-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544163 ] 

Manjula Peiris commented on SANDESHA2C-34:
------------------------------------------

I have fixed this for MYSQL case. Need to check for sqlite.

> when rm_ping client fails to run again correctly the data base need clean up.
> -----------------------------------------------------------------------------
>
>                 Key: SANDESHA2C-34
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2C-34
>             Project: Sandesha2/C
>          Issue Type: Bug
>         Environment: Linux+MySQL
>            Reporter: Manjula Peiris
>            Priority: Critical
>
> In rm_ping clinet the user does not create a SequenceKey . so when creating InternalSequenceId it uses only the endpoint address. So if one invocation fails  during the second invocation the same internalsequenceId is used. This can be solved by providing a Sequencekey as done in other sandesha2/c samples.

-- 
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