Re: RMI, fault tolerance and load balancing without tomcat

I have just finished a project where I had to migrate a legacy C++
project and get rid of certain buggy, ancient, unsupported components
for modern java-centric equivalents. The last step in this process was
replacing CORBA with JMS. I was against this but got overruled so
we're now using JMS. The app was typical request-response for which I
think CORBA was ok. In my document of where we are, were we want to go
and how we are going to get there, I said that replacing it with RMI
would be sub-optimal because of the lack of fault tolerance and load
balancing. This is one of the reasons that JMS was chosen - no RMI, no
CORBA, what does that leave for IPC?

So my question is, "how does one get fault tolerance and load
balancing with RMI?". The FT and LB that comes with tomcat cannot be
used because I want a solution that does not require the app to run
inside a servlet container. Indeed the app might not even be a
servlet. I think that RMI is much closer to CORBA than JMS for this
particular app. There are already issues with the JMS approach because
of having to twist things around to make an asynchronous mechanism
appear to be synchronous.