ruxit has long understood how to track RMI calls to and from your JVMs, but RMI calls can be tricky and not every call is interesting. Plus, due to the easy nature of producing and misusing RMI calls, you can easily end up with a million of them. With this in mind, we’ve taken great care to not bloat your services views with hundreds of RMI services. We only show a single RMI service per application server. Now we’re extending this visibility even further, showing you all important exposed RMI services via their classes and methods. You can now analyze each and every RMI method in your system separately.