I am experiencing the same problem (environment: tomcat). I choose to
initialize Java2D early during boot of the application server instead having a
memory later when it is being initialized by an app. This class is called as a
wrapper for the original tomcat bootstrap class.
This is only a workaround, I hope the two bugs that have been filed already
will be solved soon.
public class PlusBoot {
public static void main (String[] args) {
ImageIO.setUseCache(false);
// Configuration.getConfiguration();
Bootstrap.main(args);
}
}
[Message sent by forum member 'ahus1' (ahus1)]
http://forums.java.net/jive/thread.jspa?messageID=337065
===========================================================================
To unsubscribe, send email to lists...@java.sun.com and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
lists...@java.sun.com and include in the body of the message "help".
