Hi Deepal and Martin,
Thank you for your suggestion and explanation.
I could see that an additional java process was started and thought that was
the problem.
I made the following tests using both your async client and the Axis2
nonblockingdual
Test1
opts.setUseSeparateListener(true);
AxisCallback callBack
- the callback works, but the process hangs with an additional java
process active
Test2
//// opts.setUseSeparateListener(true);
AxisCallback callBack
- the callback is not called, and the client waits forever.
Test3
opts.setUseSeparateListener(true);
Callback callback
- the callback works, but the process hangs with an additional java
process active
Test4
//// opts.setUseSeparateListener(true);
Callback callback
- the callback works OK and the client terminates OK
-----------------
Nonblocking async does work, but only with the older class Callback.
The Axis2 dual sample enable a listener. It is not clear what this sample
is demonstrating.
Thanks for the help.
Rick
Rick
On Nov 30, 2007 7:19 AM, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > It appears that a thread or process is still active.
> >
> > Is this correct?
> >
> yes thats what happen when you do an invocation using two channel case,
> in that case Axis2 start a server at the client side and send that as
> the address to server to which that should reply.
> And though Axis2 start the server automatically it is is not going to
> stop that , so that is why you can see the thread is till running.
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
