Ted FYI The latest Sandesha builds (and the upcoming 1.2 release) support RM 1.0 without a separate listener. There has been a lot of work to support this.
Paul On 5/10/07, Ted Jones <[EMAIL PROTECTED]> wrote:
Thanks Amila. I appreciate the input. I am using Dual channel since it appeared to be required per this thread: http://mail-archives.apache.org/mod_mbox/ws-sandesha-dev/200703.mbox/[EMAIL PROTECTED] Is this the case? I am using Sandesha2 1.1 with Axis2 1.1.1. I have verified your points outlined below. Everything appears correct. Martin - I will put together a reproducible test case and post ASAP. Thanks for your assistance. Ted ________________________________ From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 12:25 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning Are you using the Dual chanel mode or single chanel? if you set the setUseSeparateListener your request comes in a different http chanel than you send the request. Otherwise it comes in the same chanel. In the dual chanel model, What happens is your client starts a simple http server on your machine and set the ReplyTo addressing header to point to the stated server. So you have to make sure these things. 1. you must have engage the Addressing. (otherwise server won't be able to find the reply location) 2. client uses the port and the host name you have specified in the axis2.xml to start its simple http server and set this address to replyTo filed. So you have to use two seperate axis2.xml files for client and the server with different port numbers if you run them both in one machine. 3. if your server is in out side your firewall, the host name you specify in the client axis2.xml should be able to access from the out side the firewall. On 5/10/07, Martin Gainty <[EMAIL PROTECTED]> wrote: > Good Evening > > if you publish your wsdl we can run the client code > > Thanks > Martin-- > This email message and any files transmitted with it contain confidential > information intended only for the person(s) to whom this email message is > addressed. If you have received this email message in error, please notify > the sender immediately by telephone or email and destroy the original > message without making a copy. Thank you. > > ----- Original Message ----- > From: "Ted Jones" <[EMAIL PROTECTED]> > To: <axis-user@ws.apache.org> > Sent: Wednesday, May 09, 2007 7:10 PM > Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning > > > So, I'm guessing that the message is never reaching the server. Which > may explain why there is no logging? I can see in debug where the > Sandesha2 logic is hit and the message is sent but I never see any > sequences or other message traffic and my client is left polling forever > waiting for the callback to complete. > > Any other thoughts on what might be happening here or where else I can > look? > > Thanks, > Ted > > -----Original Message----- > From: Ted Jones [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 09, 2007 10:27 AM > To: axis-user@ws.apache.org > Subject: RE: [Axis2] WS-RM and Axis2 Asynch Client not Returning > > Thanks for all the responses. This is a great mailing list. > > I am not seeing any messages in TCPMON or in the logs. :-( > > Question: How can you configure TCPMON to capture messages sent to > SimpleHTTPServer? I get a port bind exception. > > Also, I cannot seems to get logging working with Sandesha2. If anyone > has it working, I would really appreciate a peek at their > log4j.properties. > > Thanks! > Ted > > -----Original Message----- > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 08, 2007 11:12 PM > To: axis-user@ws.apache.org > Subject: Re: [Axis2] WS-RM and Axis2 Asynch Client not Returning > > Ted Jones wrote: > > > I am using Sandesha2 with an asynch Axis2 client. Using the example > > that comes with Sandesha2 (the asynch echo client), the onComplete() > > method of my callback is never hit. It appears the response is not > > returning. > > > > Any ideas? > > Did you try capturing message sequences with TCPMON and chek the message > sequence? > > Also, have a look into the server and client logs. > > Samisa... > > > --------------------------------------------------------------------- > 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] > > > --------------------------------------------------------------------- > 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] > > -- Amila Suriarachchi, WSO2 Inc.
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
