September 2002
Intermediate to advanced
608 pages
14h 20m
English
RMI seems to frequently take common problems and obfuscate their cause with unusual error methods. This may become greatly improved in the JDK 1.4 release, where the stack trace for RMI failures will include both server-side and client-side method calls. With JDK 1.3.1 and prior, only the client's stack trace is seen, and frequently it's difficult to discern what problem on the server could have resulted in the error seen on the client. Table 15.3 lists just a few of these problems that I encountered during development of these examples.
| Problem | Cause |
|---|---|
| Null pointer exception | A class could not be created, perhaps due to leaving something out of a distribution JAR file. Perhaps ... |
Read now
Unlock full access