Why would a call to invokeBlocking() end up in
call.invokeNonBlocking() ?? If Axis want to complete both synch and
asynch calls as asynch calls internally, this should be transparant to
the user, who should not be botherd to provide a callback.
- Venkat
On 9/2/05, jayachandra <[EMAIL PROTECTED]> wrote:
> Hi!
>
> When I invoked a call.invokeBlocking() routine, internally it is simulated
> using invokeNonBlocking() using a call back mechanism. However, even though
> the server sent a valid response (this I verified with TCPmon) the call back
> class is not getting properly updated with the result. Is this a known
> issue? Can someone clarify this. The error I am getting is...
>
>
> Time out while waiting for the server to send the response
>
> at
> org.apache.axis2.clientapi.InOutMEPClient.invokeBlocking(InOutMEPClient.java:144)
>
> at
> org.apache.axis2.clientapi.Call.invokeBlocking(Call.java:89)
>
> at
> org.apache.axis2.saaj.SOAPConnectionImpl.call(SOAPConnectionImpl.java:72)
> which essentially is arising from the code block in InOutMEPClient.java
> which looks like follows.
> (Line Numbers 135 to 146 of InOutMEPClient.invokeBlocking() method) ::
>
> while (!callback.isComplete()) {
> //wait till the reponse arrives
> if (index++ < 20) {
> try {
> Thread.sleep(100);
> } catch (InterruptedException e) {
> throw new AxisFault(e);
> }
> } else {
> throw new
> AxisFault(Messages.getMessage("responseTimeOut")); << This is the reported
> error
> }
> }
>
> Any help in this regard will be much appreciated.
>
> Thanks
> Jayachandra
> --
> -- Jaya
