[ 
https://issues.apache.org/jira/browse/SANDESHA2-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743154#action_12743154
 ] 

Dave Parsons commented on SANDESHA2-197:
----------------------------------------

Hi Patrice,

Are you saying that the CreateSequenceResponse message is being sent 
asynchronously to the MC Anonymous address that is set in the replyTo & 
AcksTo of the createSequence message?  Also just to confirm is your client 
and server both using Sandesha for RM and are they both set at the same 
version level of 1.1?

If you want to send over the trace I can take a look and see if I can see 
anything out of the ordinary.

Regards,

Dave

Dave Parsons
Web Services Development
INTERNAL:  David Parsons1/UK/i...@ibmgb :: DE3F20 :: 246930
EXTERNAL:  [email protected] :: (01962) 816930
Mail Point 211, IBM Hursley Park, Winchester. SO21 2JN




From:
"patrice aubry (JIRA)" <[email protected]>
To:
[email protected]
Date:
13/08/2009 16:29
Subject:
[jira] Created: (SANDESHA2-197) CreateSequence response is actually sent 
to the anonymous makeconnection url (i.e. http//:docs.oasis-open.org/..... 
???



CreateSequence response is actually sent to the anonymous makeconnection 
url (i.e. http//:docs.oasis-open.org/..... ???
-----------------------------------------------------------------------------------------------------------------------

                 Key: SANDESHA2-197
                 URL: https://issues.apache.org/jira/browse/SANDESHA2-197
             Project: Sandesha2
          Issue Type: Bug
    Affects Versions: 1.3
         Environment: Windows XP, Java 1.6, Axis 1.4, Tomcat 6
            Reporter: patrice aubry
            Priority: Blocker


This may not be a bug.

I am testing the samples provided. The syncpingclient works fine (after a 
few updates) in W-RM 1.0 but not for WS-RM 1.1.

When using WS-RM 1.1,  the anonymous replyTo is not understood as such and 
is treated as an actual URL.
When a CreateSequence message is sent, the response is of course never 
received, with an UnknownHostException.

The debug log looks fine, in that the correct processing seems to take 
place.

What am I missing ?
Your help will be greatly appreciated.

Thanks in advance,




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









Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU







> CreateSequence response is actually sent to the anonymous makeconnection url 
> (i.e. http//:docs.oasis-open.org/..... ???
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SANDESHA2-197
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-197
>             Project: Sandesha2
>          Issue Type: Bug
>    Affects Versions: 1.3
>         Environment: Windows XP, Java 1.6, Axis 1.4, Tomcat 6
>            Reporter: patrice aubry
>            Priority: Blocker
>
> This may not be a bug.
> I am testing the samples provided. The syncpingclient works fine (after a few 
> updates) in W-RM 1.0 but not for WS-RM 1.1.
> When using WS-RM 1.1,  the anonymous replyTo is not understood as such and is 
> treated as an actual URL.
> When a CreateSequence message is sent, the response is of course never 
> received, with an UnknownHostException.
> The debug log looks fine, in that the correct processing seems to take place.
> What am I missing ?
> Your help will be greatly appreciated.
> Thanks in advance,

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

Reply via email to