Hi James,
Yes, if the client thread doesn't sleep, as the call to execute() is
nonblocking, the thread dies before it can create a SOAP envelope and ship
it out. That is why we do not see any SOAP requests in the SOAP monitor. So
"sleeping" is essential even for sending the request :)
I was waiting for some of the developers to confirm this being a bug to
file a JIRA. Not sure if Sathija already filed it.
-Nirmit
"Bessette, James
M."
<[EMAIL PROTECTED] To
s.com> <axis-user@ws.apache.org>
cc
08/15/2006 11:08
AM Subject
RE: [Axis2 1.0] Asynchronous
doc/lit, no output.
Please respond to
[EMAIL PROTECTED]
he.org
I have experienced the same issue using the generated code. I can
understand making the client sleep to receive the request and response.
But based on my experience and the experience of others, it appears if
the thread does not sleep at all, the request never makes it to the
server. Has anyone logged a JIRA issue on this? Can anyone from the
Axis 2 team confirm our findings?
Thanks
James Bessette
-----Original Message-----
From: Sathija Pavuluri [mailto:[EMAIL PROTECTED]
Sent: Monday, August 14, 2006 5:24 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2 1.0] Asynchronous doc/lit, no output.
Ajith, Nirmit,
This is indeed for Axis2 1.0.
When I tried the nightlies(8/14/06) I ran into even bigger problems. The
web services did not even get deployed properly.
Something about method not found error for
javax.xml.stream.XMLOutputFactory.newInstance(ClassLoader) method not
found.
Not sure if its just me or others who have had problems with today's
nightly.
I'll try again tomorrow.
Anyway, for now I reverted back to my previous libraries and tried the
same thing that Nirmit mentioned below.
With sufficient sleep(5000), I could send the request and get response
back. And the callback methods got invoked too!
Nirmit, you might want to sequentially increase your sleep time and try.
Once the req and res are sent I dont see why the callbacks shouldnt get
invoked.
Thanks,
Sathija.
> Hi Ajith, Sathija,
>
> I partly figured out the problem.
>
> As the userguide shows, with asynchronous clients, the calling thread
> must do a Thread.sleep(). But in the generated code, I do not see any
> Thread.sleep().
>
> So, I put a Thread.sleep(1000) in the generated test client's
> testStart<method name> method, and then I saw a SOAP request/response
> in SOAPMonitor. However, my callback methods were not invoked!! So, I
> still haven't figured out how to receive the response. I gave up and
> started using synchronous clients instead.
>
> -Nirmit
>
>
>
>
> "Ajith Ranabahu"
> <[EMAIL PROTECTED]
> mail.com>
> To
> axis-user@ws.apache.org
>
> 08/14/2006 04:25
> cc PM
>
>
> Subject
>
> Re: [Axis2 1.0] Asynchronous
>
> Please respond to doc/lit, no output.
> [EMAIL PROTECTED]
>
> he.org
>
>
>
>
>
>
>
>
>
> Hi,
> Is this for 1.0 ? Can you guys try with the latest nightlies ?
>
> Ajith
>
> On 8/14/06, Sathija Pavuluri <[EMAIL PROTECTED]> wrote:
>> Hi Nirmit,
>>
>> I am running an async call in Axis2 1.0 using generated code in a
>> similar scenario as yours and seeing the exact same problem.
>> Nothing is SOAP monitor unlike other sync calls. Looks like the
>> request was never made.
>> But I see no errors either.
>>
>> The async call goes thru in one case, when my test program also
>> invokes a sync call. At that time, I see the req/res for the async
>> call too. But when I run it by itself, nothing happens.
>>
>> Have you been able to figure out the problem?
>>
>> Thanks,
>> Sathija.
>>
>>
>>
>>
>>
>> >Hi,
>>
>> >I am trying to invoke a doc/lit service with an asynchronous (two
> transport
>> >connections) client. I started from a WSDL and generated client side
>> and server side code with Axis databinding, along with a junit test.
>>
>> >However, when I run the test, I do not get any output, no
>> >exceptions,
> and
>> >no callbacks from the server. Also, SOAPMonitor does not show any
>> request/response message. My SOAPMonitor works with other clients.
>> Where did the call go?
>>
>> >I am really confused why this is happening. Has anyone tried clients
> with
>> >callbacks?
>>
>> >Thanks,
>>
>> >-Nirmit
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Ajith Ranabahu
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
