I agree we should provide better error reporting for the client... there are actually different possible causes, 1) operation not currently available 2) operation timed out (meaning, message was picked up but reply didn't come) 3) process failed during operation I suggest filing an enhancement request.
alex On Fri, Mar 13, 2009 at 5:40 AM, Rafal Rusin <[email protected]> wrote: > I have a following process: > <receive1 operation1 correlationSet1/> > <reply1/> > <wait 10min./> > <receive2 operation2 correlationSet1/> > <reply2/> > > When I send a message for operation2 during wait, I get timeout. > Shouldn't it be some fault exception like "no such operation" without > any delay instead? > > I'm attaching an example with soapUI test case. > > Regards, > -- > Rafał Rusin > http://www.touk.pl > http://www.mimuw.edu.pl/~rrusin <http://www.mimuw.edu.pl/%7Errusin> >
