RE: Issues with WSRM 1.1 "single channel" messaging

"Scott Came" <[email protected]>
Newsgroups gmane.comp.apache.webservices.fx.devel
Message-ID <[email protected]>
Thanks for your reply, David.

Method 2 doesn't work for me either...here are the equivalent messages
when I remove the offer...

<?xml version='1.0' encoding='UTF-8'?>

   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

      <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">

 
<wsa:To>http://127.0.0.1:9763/axis2/services/RMSampleService</wsa:To>

 
<wsa:MessageID>urn:uuid:F113383CC2A2BEB5621220799461827</wsa:MessageID>

 
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsmc/200702/MakeConnection<
/wsa:Action>

      </soapenv:Header>

      <soapenv:Body>

         <wsmc:MakeConnection
xmlns:wsmc="http://docs.oasis-open.org/ws-rx/wsmc/200702">

 
<wsmc:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=
urn:uuid:F113383CC2A2BEB5621220799461660</wsmc:Address>

         </wsmc:MakeConnection>

      </soapenv:Body>

   </soapenv:Envelope>

 

Then...

<?xml version='1.0' encoding='UTF-8'?>

   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

      <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">

 
<wsa:To>http://127.0.0.1:9763/axis2/services/RMSampleService</wsa:To>

         <wsa:ReplyTo>

 
<wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=u
rn:uuid:F113383CC2A2BEB5621220799461660</wsa:Address>

         </wsa:ReplyTo>

 
<wsa:MessageID>urn:uuid:F113383CC2A2BEB5621220799461677</wsa:MessageID>

 
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence<
/wsa:Action>

      </soapenv:Header>

      <soapenv:Body>

         <wsrm:CreateSequence
xmlns:wsrm="http://docs.oasis-open.org/ws-rx/wsrm/200702">

            <wsrm:AcksTo>

               <wsa:Address
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.
org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:F113383CC2A2BEB5621220799461
660</wsa:Address>

            </wsrm:AcksTo>

         </wsrm:CreateSequence>

      </soapenv:Body>

   </soapenv:Envelope>

 

Then two of these (identical but for the MessageID in the header)...

<?xml version='1.0' encoding='UTF-8'?>

   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

      <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">

 
<wsa:To>http://127.0.0.1:9763/axis2/services/RMSampleService</wsa:To>

 
<wsa:MessageID>urn:uuid:F113383CC2A2BEB5621220799464850</wsa:MessageID>

 
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsmc/200702/MakeConnection<
/wsa:Action>

      </soapenv:Header>

      <soapenv:Body>

         <wsmc:MakeConnection
xmlns:wsmc="http://docs.oasis-open.org/ws-rx/wsmc/200702">

 
<wsmc:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=
urn:uuid:F113383CC2A2BEB5621220799461660</wsmc:Address>

         </wsmc:MakeConnection>

      </soapenv:Body>

   </soapenv:Envelope>

 

Then the first message again, then 4 of the second, etc...

Thanks again for your help!

--Scott

-----Original Message-----
From: David Illsley [mailto:[email protected]] 
Sent: Saturday, September 06, 2008 5:10 AM
To: Scott Came
Cc: [email protected]
Subject: Re: Issues with WSRM 1.1 "single channel" messaging

 

I suspect the problem occurs because the Offer endpoint address

differs from the WS-A ReplyTo address, though I don't know why that's

happening. Does Method 2 work for you (it omits the offer)?

David

 

On Fri, Sep 5, 2008 at 7:42 PM, Scott Came <[email protected]>
wrote:

> I have been trying to get the examples included in this article

> (http://wso2.org/library/1092) working, but am having trouble.

> 

> I've deployed the RMSampleService exactly as it comes from the
Sandesha2

> distribution (I downloaded the src distro and built it myself using
maven.)

> I modified the UserguideEchoClient class as attached, adding the
relevant

> lines from the article (linked above).  I don't want to set

> useSeparateListener(true), since as the article suggests, this can
raise

> issues with firewalls.  This is especially an issue in my
security-conscious

> community.  So, what I'm after is using the same transport channel,
either

> method 1 or method 2 under "WSRM 1.1" in the article.

> 

> Incidentally, before specifying WSRM 1.1, the client and server work
exactly

> as expected (with RM 1.0).

> 

> When I specify WSRM 1.1, the client hangs.  I run it through TCPMon
(port

> 9763, forwarding to Axis on 8080), and what I see is the following
sequence

> of messages:

> 

> <?xml version='1.0' encoding='UTF-8'?>

> 

>    <soapenv:Envelope

> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

> 

>       <soapenv:Header
xmlns:wsa="http://www.w3.org/2005/08/addressing">

> 

> 

> <wsa:To>http://127.0.0.1:9763/axis2/services/RMSampleService</wsa:To>

> 

> 

>
<wsa:MessageID>urn:uuid:DA7CB5DE7E858547DE1220502299733</wsa:MessageID>

> 

> 

>
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsmc/200702/MakeConnection<
/wsa:Action>

> 

>       </soapenv:Header>

> 

>       <soapenv:Body>

> 

>          <wsmc:MakeConnection

> xmlns:wsmc="http://docs.oasis-open.org/ws-rx/wsmc/200702">

> 

> 

>
<wsmc:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=
urn:uuid:DA7CB5DE7E858547DE1220502299582</wsmc:Address>

> 

>          </wsmc:MakeConnection>

> 

>       </soapenv:Body>

> 

>    </soapenv:Envelope>

> 

> Then:

> 

> <?xml version='1.0' encoding='UTF-8'?>

> 

>    <soapenv:Envelope

> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

> 

>       <soapenv:Header
xmlns:wsa="http://www.w3.org/2005/08/addressing">

> 

> 

> <wsa:To>http://127.0.0.1:9763/axis2/services/RMSampleService</wsa:To>

> 

>          <wsa:ReplyTo>

> 

> 

>
<wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=u
rn:uuid:DA7CB5DE7E858547DE1220502299582</wsa:Address>

> 

>          </wsa:ReplyTo>

> 

> 

>
<wsa:MessageID>urn:uuid:DA7CB5DE7E858547DE1220502299599</wsa:MessageID>

> 

> 

>
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsrm/200702/CreateSequence<
/wsa:Action>

> 

>       </soapenv:Header>

> 

>       <soapenv:Body>

> 

>          <wsrm:CreateSequence

> xmlns:wsrm="http://docs.oasis-open.org/ws-rx/wsrm/200702">

> 

>             <wsrm:AcksTo>

> 

>                <wsa:Address

>
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.
org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:DA7CB5DE7E858547DE1220502299
582</wsa:Address>

> 

>             </wsrm:AcksTo>

> 

>             <wsrm:Offer>

> 

> 

>
<wsrm:Identifier>urn:uuid:DA7CB5DE7E858547DE1220502299453</wsrm:Identifi
er>

> 

>                <wsrm:Endpoint>

> 

>                   <wsa:Address

>
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
08/addressing/anonymous</wsa:Address>

> 

>                </wsrm:Endpoint>

> 

>             </wsrm:Offer>

> 

>          </wsrm:CreateSequence>

> 

>       </soapenv:Body>

> 

>    </soapenv:Envelope>

> 

> Then two of these (identical):

> 

> <?xml version='1.0' encoding='UTF-8'?>

> 

>    <soapenv:Envelope

> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

> 

>       <soapenv:Header
xmlns:wsa="http://www.w3.org/2005/08/addressing">

> 

> 

> <wsa:To>http://127.0.0.1:9763/axis2/services/RMSampleService</wsa:To>

> 

> 

>
<wsa:MessageID>urn:uuid:DA7CB5DE7E858547DE1220502302756</wsa:MessageID>

> 

> 

>
<wsa:Action>http://docs.oasis-open.org/ws-rx/wsmc/200702/MakeConnection<
/wsa:Action>

> 

>       </soapenv:Header>

> 

>       <soapenv:Body>

> 

>          <wsmc:MakeConnection

> xmlns:wsmc="http://docs.oasis-open.org/ws-rx/wsmc/200702">

> 

> 

>
<wsmc:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=
urn:uuid:DA7CB5DE7E858547DE1220502299582</wsmc:Address>

> 

>          </wsmc:MakeConnection>

> 

>       </soapenv:Body>

> 

>    </soapenv:Envelope>

> 

> Then another CreateSequence message like the one above, then four

> MakeConnection messages, then a CreateSequence, and so on
exponentially.

> Each message has zero-length content in the http response.  Each
response

> message has a "202 Accepted" status in it.

> 

> Any idea what might be going wrong?

> 

> Thanks much for any assistance you can provide.

> 

> --Scott

> 

> Scott Came

> 

> Director, Systems and Technology

> 

> SEARCH--The National Consortium for Justice Information and Statistics

> 

> (916) 212-5978

> 

> (916) 392-2550 x311

> 

> [email protected]

> 

> ---------------------------------------------------------------------

> To unsubscribe, e-mail: [email protected]

> For additional commands, e-mail: [email protected]

>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.