Re: problem w/ serialization of java.rmi.Remote pointer across HTTP through firewall

> I built an HTTP proxy servlet to enable a local rmi
> app to communicate to a computing cluster on the other
> side of a Cisco Pix firewall. It works, with one
> caveat: if the local client makes a request whose
> return type includes a java.rmi.Remote reference, it
> takes literally 20 seconds to receive the data back
> from the proxy.

Have you tried generating a thread dump of the client
during the pause? Sounds like the hangup could be with
DGC, trying to make a dirty call back to the server. How
do the hostname/address and socket factory in the returned
stub relate to the ones in the original stub you're making
the call through? Do subsequent calls by the client through
the returned Remote reference work correctly, without delay?

- Bob

===========================================================================
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