[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
