Eran Chinthaka wrote:
hang on, I'm not allowing you to escape like that :).
I just did a small fix to the code now. Can u please check whether
your non-blocking scenario with separate listeners runs now ? Thilina
also had the same problem.
-- Chinthaka
jayachandra wrote:
Yes guys!
the application i was testing erroneously set its useSeperateListener
to true. I've changed it, and things are running fine now.
Thanks for all your help!
Bye
Jaya
On 9/2/05, *Eran Chinthaka* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Jaya,
Please see my comments below.
jayachandra wrote:
> Hi!
>
> When I invoked a call.invokeBlocking() routine, internally it is
> simulated using invokeNonBlocking() using a call back mechanism.
invokeBlocking() will use invokeNonBlocking() if you send and receive
using two different instances of transports. In the other case,
meaning
when you use the same transport to send and receive, we are not using
invokeNonBlocking() for invokeBlocking case. Just a small
clarification ;).
Regards,
Chinthaka
--
-- Jaya
Chinthaka is right. Even when you set to use duel channel your code
should work. But make sure if you are using invokeBlocking() or
invokeNonBloking() with duel channel, for the time being not to call
"call.close()". It will cause the trouble.
Saminda
