This content has been marked as final. Show 3 replies
Why start it in a separate process? Just export it from the Tomcat JVM. Then you get whatever logging configuration Tomcat is already using.
We need to access some legacy code which is not thread safe in a in a multithreaded environment. To support this kind of functionality we exposed the legacy code as Remote interface and registering the implemented component to a RMI registry. so when ever multiple therads wanted to access this code it will create a RMI serever for that and access it remotely.
But that doesn't solve the thread safety problem! RMI specifically makes no guarantees about that. See the RMI Specification. And neither does running it in a separate JVM!