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 "Dave Parsons (JIRA)" <ji...@apache.org> on 2008/07/01 15:02:44 UTC
[jira] Created: (SANDESHA2-166) MC polling doesn't start until
after the createSeqResponse has been processed
MC polling doesn't start until after the createSeqResponse has been processed
------------------------------------------------------------------------------
Key: SANDESHA2-166
URL: https://issues.apache.org/jira/browse/SANDESHA2-166
Project: Sandesha2
Issue Type: Bug
Reporter: Dave Parsons
Attachments: Poll4CreateSeqResponse.patch
MC polling doesn't start until after the createSeqResponse has been processed. This causes problems for certain implementations of RM. For instance the Oracle implementation sends all responses on the backchannels of MC's and our IBM RM Client implementation expects the createSeqResponse to come back on the back channel of a createSeq and not on the back channel of a MC. Therefore we wouldn't have started polling and the createSeqResponse will never come back.
--
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] Updated: (SANDESHA2-166) MC polling doesn't start until
after the createSeqResponse has been processed
Posted by "Dave Parsons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Parsons updated SANDESHA2-166:
-----------------------------------
Attachment: Poll4CreateSeqResponse.patch
> MC polling doesn't start until after the createSeqResponse has been processed
> ------------------------------------------------------------------------------
>
> Key: SANDESHA2-166
> URL: https://issues.apache.org/jira/browse/SANDESHA2-166
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Dave Parsons
> Attachments: Poll4CreateSeqResponse.patch
>
>
> MC polling doesn't start until after the createSeqResponse has been processed. This causes problems for certain implementations of RM. For instance the Oracle implementation sends all responses on the backchannels of MC's and our IBM RM Client implementation expects the createSeqResponse to come back on the back channel of a createSeq and not on the back channel of a MC. Therefore we wouldn't have started polling and the createSeqResponse will never come back.
--
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] Updated: (SANDESHA2-166) MC polling doesn't start until
after the createSeqResponse has been processed
Posted by "Dave Parsons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Parsons updated SANDESHA2-166:
-----------------------------------
Description: MC polling doesn't start until after the createSeqResponse has been processed. This causes problems for sandesha2. For instance the Oracle implementation sends all responses on the backchannels of MC's and sandesha2 Client implementation expects the createSeqResponse to come back on the back channel of a createSeq and not on the back channel of a MC. Therefore we wouldn't have started polling and the createSeqResponse will never come back. (was: MC polling doesn't start until after the createSeqResponse has been processed. This causes problems for certain implementations of RM. For instance the Oracle implementation sends all responses on the backchannels of MC's and our IBM RM Client implementation expects the createSeqResponse to come back on the back channel of a createSeq and not on the back channel of a MC. Therefore we wouldn't have started polling and the createSeqResponse will never come back.)
> MC polling doesn't start until after the createSeqResponse has been processed
> ------------------------------------------------------------------------------
>
> Key: SANDESHA2-166
> URL: https://issues.apache.org/jira/browse/SANDESHA2-166
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Dave Parsons
> Attachments: Poll4CreateSeqResponse.patch
>
>
> MC polling doesn't start until after the createSeqResponse has been processed. This causes problems for sandesha2. For instance the Oracle implementation sends all responses on the backchannels of MC's and sandesha2 Client implementation expects the createSeqResponse to come back on the back channel of a createSeq and not on the back channel of a MC. Therefore we wouldn't have started polling and the createSeqResponse will never come back.
--
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: (SANDESHA2-166) MC polling doesn't start until
after the createSeqResponse has been processed
Posted by "Andrew Gatford (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Gatford resolved SANDESHA2-166.
--------------------------------------
Resolution: Fixed
Fixed in 673385
> MC polling doesn't start until after the createSeqResponse has been processed
> ------------------------------------------------------------------------------
>
> Key: SANDESHA2-166
> URL: https://issues.apache.org/jira/browse/SANDESHA2-166
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Dave Parsons
> Attachments: Poll4CreateSeqResponse.patch
>
>
> MC polling doesn't start until after the createSeqResponse has been processed. This causes problems for sandesha2. For instance the Oracle implementation sends all responses on the backchannels of MC's and sandesha2 Client implementation expects the createSeqResponse to come back on the back channel of a createSeq and not on the back channel of a MC. Therefore we wouldn't have started polling and the createSeqResponse will never come back.
--
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