Re: RMI do not response

Paulo Melo wrote:
> So, when i make a call from client, he do not throw a exception nor finally.

There are several things that you can do to look into this problem.  One is to
request a stack dump of the threads running in the JVM.  If the appserver can be
run from a terminal window, on unix, you can type CTRL-\ (which sends SIGQUIT)
at the terminal and you'll see a stack trace that shows you where all the
threads are so that you can make sure you don't have a deadlock condition.  On
windows, you have to run it from DOS window and type CTRL-BREAK (or FN-BREAK as
it is on my laptop).

Also, on JDK1.5, you can use JConsole to attach to running JVMs and see the
stack trace of each running thread, as well as check memory usage and other
things to make sure you aren't getting into an out of memory condition that is
causing excessive GC activity which will slow things down.

And finally, there is RMI debugging that you can turn on.  Look in the RMI
documentation for more information, but

        -Djava.rmi.server.exceptionTrace=true
        -Djava.rmi.server.logCalls=true

can be place on the command line of the JVM to get more information about what
is actually happening with RMI.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html