From the line numbers, it looks like you're using Remoting 2.0.0. The notion
of connected changed from 2.0.0 to 2.2.0. I'm not sure what is happening,
but you might try upgrading to see of the problem goes away.
View the original post :
shdv wrote : [EMAIL PROTECTED] wrote : About the only thing can know for
sure is if get a CannotConnectException, the call never reached the server.
Anything else would be difficult to know for sure (i.e. if get SocketException,
can't be certain that call didn't make it to server).
|
|
In my case connection was established and several calls got through.
The scenario is:
1. Connect to server
2. DoSomething1
3. DoSomething2 and disconnect in the same moment due to networking issue
DoSomething2 fails with Exception being thrown.
I export POJO with RMI transport and see the
Disconnect was caused not by my code but by Remoting itself (detected by ping
or something else).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058170#4058170
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058170
Disconnect was caused not by my code but by Remoting itself (detected by ping
or something else).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058164#4058164
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058164
[EMAIL PROTECTED] wrote : About the only thing can know for sure is if get a
CannotConnectException, the call never reached the server. Anything else would
be difficult to know for sure (i.e. if get SocketException, can't be certain
that call didn't make it to server).
Why does
Maybe I can clarify a bit. The reason the remoting client declares that it
throws Throwable is that remoting will pass along the Throwable object thrown
from the server side hanlder. Since we don't know what type of exceptions the
server side handler might throw, we have to declare the most
That helps indeed :)
Thank you for the explanation.
I understand now.
Is there some way to determinate if the problem was before, during or after the
call was handled in the server?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4017822#4017822
Reply to the
About the only thing can know for sure is if get a CnnotConnectException, the
call never reached the server. Anything else would be difficult to know for
sure (i.e. if get SocketException, can't be certain that call didn't make it to
server).
View the original post :
Ok, that's all for my questions.
Thanks for the replies.
I wish this post help others as much as it helped me.
See ya.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4017853#4017853
Reply to the post :
Welcome to Remoting.
anonymous wrote :
| I wish to determinate if the problem ocurred:
| when the call was going to the server.
| when the request was being processed in the server.
| when the call was returning to the client.
|
You want to look at the particular Throwable that
Thank you very much for the reply, I really appreciate the help.
I think my original post wasn't clear (sorry about my poor english), I'll try
to put this as correctly as possible.
When you do a remote call or callback, a number of problems may happen.
The invoke() and invokeOneWay() methods
12 matches
Mail list logo
