When it comes to finding fonts, Java modifies its fontpath, adding additional
font directories from the local file system. Java then uses the Xlib XSetFontPath to tell the X server about these new font directories.
When Java is run in environments like XTerminals or 3rd party
X-Emulators, this process takes an extremely long time and eventually fails with
error messages, because these fonts are not local to the X server and java never
finds the fonts it needs. Normally you would be able to work around missing font problems by setting up a Font Server. However, when it comes to F3 and
type1 fonts, you cannot set up a Font Server due to bug #4041562 which causes
the Font Server to crash when you try to get it to serve F3 and type1 fonts.
Regardless of this particular problem, Java as any other XClient should not be
modifying its fontpath to begin with, rather, it should use the XServer as
configured by the user to obtain required fonts.

Solaris 2.6 Server, Solaris JDK 1.2.1. Clients are NCD XTerminals and PC's running Hummingbird Exceed.