EJBs are built on top of RMI. Both imply Java clients and beans. If your clients need to be written in something else (e.g., .NET, PHP, etc.) go with web services or something else that speaks a platform-agnostic wire protocol, like HTTP or XML over HTTP or SOAP. If you choose RMI, you don’t need … Read more
Well, based on the definition of: A deadlock is a situation wherein two or more competing actions are each waiting for the other to finish. I would say that the answer is no – sure a thread can sit there waiting indefinitely for something, however unless two competing actions are waiting for each other it … Read more
Contrary to common belief JMX/RMI doesn’t need to open all these ports. You can actually force them to be same which will mean that at the end of the day you’ll only need to punch one hole in the firewall (if firewall is your concern). Try setting System Properties: com.sun.management.jmxremote.port com.sun.management.jmxremote.rmi.port to the same value!! … Read more
RPC is C based, and as such it has structured programming semantics, on the other side, RMI is a Java based technology and it’s object oriented. With RPC you can just call remote functions exported into a server, in RMI you can have references to remote objects and invoke their methods, and also pass and … Read more