I've solved my previous problem.And now I get the same error like yours.
On Dec 19, 2007 3:27 PM, Alberto Patino <[EMAIL PROTECTED]> wrote:
> I'm trying to do the same thing you want to do but I having a
> different message error: (Debug enabled)
>
> [DEBUG] Exit: InMemoryTransaction::enlist
> [DEBUG] Enter: InMemoryStorageManager::removeMessageContext, key:
> urn:uuid:818835A043FB6125F01198050445672
> [DEBUG] Exit: InMemoryStorageManager::removeMessageContext, key:
> urn:uuid:818835A043FB6125F01198050445672
> [DEBUG] Entry: OutInAxisOperationClient$SyncCallBack::onError,
> java.lang.Exception: Sandesha2 sender thread has not received a valid
> CreateSequnceResponse
> [DEBUG] Exit: OutInAxisOperationClient$SyncCallBack::onError
> [DEBUG] Exit: SenderWorker::run
>
> The error is: "Sandesha2 sender thread has not received a valid
> CreateSequnceResponse"
>
> I'm tracking the error in the SenderWorker.java file,
> checkForSyncResponses function:
>
>
> } catch (Exception e) {
>
> String message =
> SandeshaMessageHelper.getMessage(SandeshaMessageKeys.noValidSyncResponse);
> if (msgCtx != null &&! msgCtx.isServerSide() &&
> (Sandesha2Constants.SPEC_2005_02.Actions.ACTION_CREATE_SEQUENCE.equals(
> msgCtx.getSoapAction())
>
> ||Sandesha2Constants.SPEC_2007_02.Actions.ACTION_CREATE_SEQUENCE.equals(
> msgCtx.getSoapAction()))
> ){
> // We have not received a valid createSequnce reponse
> for the request we send so we need to terminate the seunce here
> return false;
> } else {
> if (log.isWarnEnabled())
> log.warn(message, e);
> }
>
> I'm not sure why the code is looking for ACTION_CREATE_SEQUENCE
> instead of ACTION_CREATE_SEQUENCE_RESPONSE!
>
>
> Any ideas?
>
> ( I have read the link in http://wso2.org/library/1027 but I realized
> the changes suggested in the article are already incorporated in the
> sandesha 1.3 module.xml file)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
