Hi Benjamin, This is scenario is correct as per the RM requirements. Here are the messages in exchange
Client EPM C Server EPM S C -> CreateSequenceRequest -- Msg No1 in the attachment S- > CreateSequenceResponse -- This message can be seen only in the client side. This cannot be captured by putting the soap monitor in the server side response path as Sandesha will not use this path, if the request message has the wsa:ReplyTo not anonymous. Please refer the WS-RM Spec. C- > Web Service Request - This is the Msg No 2 in the attachement S -> CreateSequenceRequest - To the client. This message is also not there and cannot be captured in the server side. Response is sent in a separate sequence in Sandesha and this is inline with the WS-RM Spec. C- > CreateSequenceResponse as a reply to the above message and you have it in Msg No 3 S -> Acknowledgement message to the initial request and it has also not been captured. C- > TerminateSequence and it is the Msg No 4 in the attachment S -> Response back to clinet using the new sequence created. This is not captured by the SOAP monitor C- > Acknowledgement to this response and this is the last message in the attachment S- >TerminateSequence and this is also not captured. A complete explaination about this scenario can be found in the following documents. You can also change these behaviors as well. http://www-128.ibm.com/developerworks/webservices/library/ws-apache-sand/ http://ws.apache.org/sandesha/userguide.html Thanks, Jaliya ----- Original Message ----- From: "Benjamin Schmeling" <[EMAIL PROTECTED]> To: "Jaliya Ekanayake" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Wednesday, October 26, 2005 3:46 AM Subject: Re: Sequence Identifier inconsistent? > It is a kind of request/response scenario. I have written a WS called > ReliabilityService with an operation AddExactlyOnceSemantics which takes > a String as an argument and returns this String again. > This ws is called in a reliable sequence with sandesha. > Why should there be two CreateSequence ? > > I've added the full messages of my soap monitor as an attachement. > The relevant part of my server-config.wsdd is attached, too. > > Thanks, > > Benjamin > >> Hi Benjamin, >> >> I think you are testing the request/response scenario (echo example) >> is this correct? >> >> If it is the case, then there are two create sequence messages that >> should appear in your soap monitor. >> One going from Client EPM to the server EPM before sending requests >> One from Sever EPM to the Client EPM before sending the responses. >> >> Check whether you are capturing all the messages in the communication. >> According to your configuration the CreateSequenceResponse for the >> first message may come in the same HTTP connection and you may have >> missed that in the SOAP monitor. Check this and let me know. >> >> Since we can see a terminate sequence with the correct Sequence ID I >> think those two messages corresponds to the first sequence and the >> last two corresponds to the second sequence that is used to send the >> responses. >> >> Configuring the SOAP monitor to capture all the messages is bit tricky >> and we normally use two SOAP monitors to check the request path and >> the response path. >> >> Let me know if this is not the case that you are experiencing. >> >> Thanks, >> >> Jaliya >> >> >> ----- Original Message ----- From: "Benjamin Schmeling" >> <[EMAIL PROTECTED]> >> To: <[email protected]> >> Sent: Tuesday, October 25, 2005 10:34 AM >> Subject: Sequence Identifier inconsistent? >> >> >>> Hi, >>> >>> I'm a bit confused about the sequence identifiers and the order my >>> soapmonitor is showing the messages: >>> >>> 1. a createsequence is sent >>> 2. the message to the called ws is sent with sequence element and >>> identifier uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66 >>> >>> 3. TerminateSequence is sent with id = >>> uuid:c12e71a0-4569-11da-84b9-bb6c79ed7b66 >>> 4. CreateSequenceResponse is sent with id = >>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360 >>> 5. SequenceAknoledgement is sent with >>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360 >>> >>> According to the specification, the CreateSequenceResponse carries >>> the Identifier for the created Sequence, but that differs: >>> c12e71a0-4569-11da-84b9-bb6c79ed7b66 != >>> uuid:c2cf9e80-4569-11da-b585-a6cf34b28360 >>> >>> Benjamin >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> >> > > -------------------------------------------------------------------------------- > <service name="RMService" provider="Handler"> > <requestFlow> > <handler type="soapmonitor"/> > <handler > type="java:org.apache.sandesha.ws.rm.handlers.RMServerRequestHandler"/> > <handler > type="java:org.apache.axis.message.addressing.handler.AddressingHandler"/> > </requestFlow> > <responseFlow> > <handler type="soapmonitor"/> > </responseFlow> > <parameter name="allowedMethods" value="*"/> > <parameter name="scope" value="request"/> > <parameter name="className" > value="org.apache.sandesha.client.RMService"/> > <parameter name="handlerClass" > value="org.apache.sandesha.ws.rm.providers.RMClientProvider"/> > </service> > <service name="ReliabilityService" provider="Handler"> > <requestFlow> > <handler type="soapmonitor"/> > <handler > type="java:org.apache.sandesha.ws.rm.handlers.RMServerRequestHandler"/> > <handler > type="java:org.apache.axis.message.addressing.handler.AddressingHandler"/> > </requestFlow> > <responseFlow> > <handler type="soapmonitor"/> > </responseFlow> > <parameter name="allowedMethods" value="*"/> > <parameter name="scope" value="request"/> > <parameter name="className" > value="de.tud.bpelreliability.ws.ReliabilityWS"/> > <parameter name="handlerClass" > value="org.apache.sandesha.ws.rm.providers.RMProvider"/> > </service> -------------------------------------------------------------------------------- > <!-- FIRST --> > > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"; > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";> > <soapenv:Header> > <wsa:MessageID > soapenv:mustUnderstand="0">uuid:df8496c0-45fa-11da-b553-a736a375bcda</wsa:MessageID> > <wsa:To > soapenv:mustUnderstand="0">http://localhost:8080/axis/services/ReliabilityService</wsa:To> > <wsa:Action > soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action> > <wsa:From soapenv:mustUnderstand="0"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:From> > <wsa:ReplyTo soapenv:mustUnderstand="0"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:ReplyTo> > </soapenv:Header> > <soapenv:Body> > <wsrm:CreateSequence> > <wsrm:AcksTo> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsrm:AcksTo> > </wsrm:CreateSequence> > </soapenv:Body> > </soapenv:Envelope> > > <!-- SECOND --> > > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";> > <soapenv:Header> > <wsa:MessageID > soapenv:mustUnderstand="1">uuid:df953890-45fa-11da-b553-a736a375bcda</wsa:MessageID> > <wsa:To > soapenv:mustUnderstand="1">http://localhost:8080/axis/services/ReliabilityService</wsa:To> > <wsa:Action > soapenv:mustUnderstand="1">urn:wsrm:addExactlyOnceSemantics</wsa:Action> > <wsa:From soapenv:mustUnderstand="1"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:From> > <wsa:ReplyTo soapenv:mustUnderstand="1"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:ReplyTo> > <wsrm:Sequence soapenv:mustUnderstand="1" > xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm";> > > <wsrm:Identifier>uuid:e0e7d040-45fa-11da-a3e1-b698cdd2adae</wsrm:Identifier> > <wsrm:MessageNumber>1</wsrm:MessageNumber> > <wsrm:LastMessage/> > </wsrm:Sequence> > </soapenv:Header> > <soapenv:Body> > <ns1:addExactlyOnceSemantics > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:ns1="ReliabilityService"> > <message xsi:type="xsd:string" xmlns="">message</message> > </ns1:addExactlyOnceSemantics> > </soapenv:Body> > </soapenv:Envelope> > > <!-- THIRD --> > > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"; > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";> > <soapenv:Header> > <wsa:MessageID > soapenv:mustUnderstand="1">uuid:e43d3cd0-45fa-11da-b553-a736a375bcda</wsa:MessageID> > <wsa:To > soapenv:mustUnderstand="1">http://localhost:8080/axis/services/ReliabilityService</wsa:To> > <wsa:Action > soapenv:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence</wsa:Action> > <wsa:From soapenv:mustUnderstand="1"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:From> > </soapenv:Header> > <soapenv:Body> > <wsrm:TerminateSequence> > > <wsrm:Identifier>uuid:e0e7d040-45fa-11da-a3e1-b698cdd2adae</wsrm:Identifier> > </wsrm:TerminateSequence> > </soapenv:Body> > </soapenv:Envelope> > > <!-- FOURTH --> > > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"; > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";> > <soapenv:Header> > <wsa:MessageID > soapenv:mustUnderstand="1">uuid:e4873e20-45fa-11da-b553-a736a375bcda</wsa:MessageID> > <wsa:To > soapenv:mustUnderstand="1">http://localhost:8080/axis/services/ReliabilityService</wsa:To> > <wsa:Action > soapenv:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</wsa:Action> > <wsa:From soapenv:mustUnderstand="1"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:From> > <wsa:RelatesTo > RelationshipType="http://schemas.xmlsoap.org/ws/2004/08/addressing"; > soapenv:mustUnderstand="1" > xmlns:http="wsa">uuid:e34c7430-45fa-11da-a3e1-b698cdd2adae</wsa:RelatesTo> > </soapenv:Header> > <soapenv:Body> > <wsrm:CreateSequenceResponse> > > <wsrm:Identifier>uuid:e4873e20-45fa-11da-b553-a736a375bcda</wsrm:Identifier> > </wsrm:CreateSequenceResponse> > </soapenv:Body> > </soapenv:Envelope> > > <!-- FIFTH --> > > <?xml version="1.0" encoding="utf-8"?> > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"; > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";> > <soapenv:Header> > <wsa:MessageID > soapenv:mustUnderstand="1">uuid:e6155830-45fa-11da-b553-a736a375bcda</wsa:MessageID> > <wsa:To > soapenv:mustUnderstand="1">http://localhost:8080/axis/services/ReliabilityService</wsa:To> > <wsa:Action > soapenv:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement</wsa:Action> > <wsa:From soapenv:mustUnderstand="1"> > > <wsa:Address>http://192.168.2.2:9090/axis/services/RMService</wsa:Address> > </wsa:From> > <wsrm:SequenceAcknowledgement soapenv:mustUnderstand="1"> > <wsrm:AcknowledgementRange Upper="1" Lower="1"/> > > <wsrm:Identifier>uuid:e4873e20-45fa-11da-b553-a736a375bcda</wsrm:Identifier> > </wsrm:SequenceAcknowledgement> > </soapenv:Header> > <soapenv:Body/> > </soapenv:Envelope> > -------------------------------------------------------------------------------- > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
