RMI Plug-in for Eclipse
version 2.0

RMI Spy - Classloading events

Class loading events tab displays all the classloading events generated by the RMI subsystem. For each event, it displays the standard timestamp and thread name columns and two additional columns that are specific to the loader events tab.

Class name column

The class name column displays the class name that is being loaded. For dynamic proxies, it lists the remote interfaces for which the proxy is being created. If the class could not be loaded the class name is prefixed by an exclamation mark "[!]":

Codebase context column

The codebase context column displays the codebase context that was used by this classloading event. The codebase context annotation is usually transmitted by the other side of an RMI call and usually it is what you've set by the codebase property. If the codebase is actually used for loading the class, the codebase context will be prefixed by a "[+]" mark. If the codebase was not used, the context will be prefixed by a "[-]" mark.

Example of classloading events that used codebase:


Example of dynamic proxy class-loading event that didn't require a codebase (although it was provided by the server):

© 2002-18 Genady Beryozkin, rmi-info@genady.net. Read our Privacy policy. Hosted on RimuHosting. Visit Javalobby.