Next in thread → Next in month →

Re: [ws-rx-implement] Re: WSO2 Interop Endpoints

From
Doug Davis <>
Date
2006-10-18T11:33:46+00:00
ID
Thread
Re: [ws-rx-implement] Re: WSO2 Interop Endpoints
Yup - I agree it should timeout at some
point - I checked and it appears the timeout value was set to 0 (for testing
purposes) so its waiting forever - I'll set it to something a little smaller
:-)

W/o RX yes it responds immediately.

-Doug

Paul Fremantle <>

10/18/2006 07:27 AM

To

Doug Davis/Raleigh/IBM@IBMUS

cc

, 

Subject

[ws-rx-implement] Re: WSO2 Interop Endpoints

Doug

Here is an interesting question - whether this is RX related? but 

shouldn't it timeout at some point?

I'm guessing that without RX enabled it would respond immediately, even

without ReplyTo=none.

Paul

Doug Davis wrote:

>

> Chamikara,

>   on 2.2, can I get you to try it again but send me a note (or
ping me 

> thru IM - yahoo(duglin), aol(dug4work) - so I can clear my logs and

> see what's going on.

> For 1.3, I think the Ping hangs because its waiting for message #2.

>  The RM logic doesn't know the MEP and as such it needs to wait
for 

> the service to be run before it closes the socket.  Try setting
the 

> wsa:ReplyTo and wsa:FaultTo to "none" and I think it should
return 

> right away.

>

> thanks

> -Doug

>

>

>

> *Chamikara Jayalath <>*

>

> 10/18/2006 04:48 AM

> Please respond to

> 

>

>

>                  

> To

>                  Doug
Davis/Raleigh/IBM@IBMUS

> cc

>                  Paul
Fremantle <>

> Subject

>                  Re:
WSO2 Interop Endpoints

>

>

>

>                  

>

>

>

>

>

> Hi Doug,

>

> I fixed the MakeConnection Action issue. Could you try that again.

>

> I tried hitting your endpoint and could successfully interop 1.1,
1.2, 

> 1.4.

> (updated the status page).

>

> In scenario 1.3 my second Ping message (with MessageNo 3), hangs.
But all

> other messages get exchanged successfully.

>

> In the scenario 2.2 almost all the messages get exchanged. But I'm
not 

> getting the

> TerminateSequence message for the response sequence.

>

> See any reason for these issues?

>

> (Will try the other scenarios as well)

>

> Chamikara

>

>

> Doug Davis wrote:

>

> btw - if you get a chance can you try to hit our endpoint and update

> the status page?

> thanks

> -Doug

>

-- 

Paul Fremantle

VP/Technology and Partnerships, WSO2 

OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle



(646) 290 8050

"Oxygenating the Web Service Platform", www.wso2.com
Next in thread → Next in month →