Java applications dump core when there is not enough swap space. Applications sometimes produce the following bus error:
not enough space
Workaround: Exit other applications running on the system or add more swap space. See the Solaris System Administration Guide for details on adding swap space.
Many X-requests in Java applications can cause a slow startup in 8-bit color (TrueColor or PseudoColor) environments. This is apparent on slower systems. A large part of the startup delay is due to the computation of an optimal dithered colormap by the awt library during initialization.
Workaround: Adjust the colormap size computed at initialization by using the environment variable VIRTCUBESIZE. Set it to a power of 2 between 4 and 32. The default value is 32.
setenv VIRTCUBESIZE 8
When you set the DISPLAY environment variable to a host other than the one running the virtual machine, underlined text in a network browser displays at a much slower rate than text that is not underlined.
Workaround: Do not use remote display.
Text rendering with JDK 1.2 is much slower than with JDK 1.1.7 and earlier releases, including rendering on platforms with Direct Graphics Access support (for example: cg6, ffb frame buffers).
Workaround: Keep socket writes to less than 64 kbytes.