Hi,
I checked out this bug, however, this was submitted against batik 1.6 and not batik 1.7. Checked out the source of UpdateManager in batik 1.7 and the code is quite different than the one that produced the bug in batik 1.6. Thanks! Leo _____ Archie Cobbs Thu, 19 Jul 2007 08:22:26 -0700 Possibly this is the same bug as http://issues.apache.org/bugzilla/show_bug.cgi?id=40681 _____ From: Leo Lim [mailto:[EMAIL PROTECTED] Sent: Friday, July 20, 2007 10:00 AM To: '[email protected]' Subject: Re: IllegalStateException Hi, I'm currently not doing any resize of the canvas. Strangely however, I added a Thread.sleep(1000) right after the call to setDocument(null) to allow more time for propagation to the DOM tree and the Exception did not occur any longer. Thanks! Leo _____ Hi Leo, Leo Lim <[EMAIL PROTECTED]> wrote on 07/18/2007 09:42:47 AM: > I'm currently using Batik 1.7 and was calling m_svgCanvas.setDocument(null) > to clear my svg canvas. Found out that this exception occurs intermittently. First off Batik does have at least one race condition in this general area, however your stack trace doesn't look like this. > While this method is executing, it is possible that the user could click my > "Cancel" button and call this method again. Is this because, I called > the nullification of the document before the previous one ran its course? Do you have code that resizes the canvas? It looks like someone is trying to resize the canvas while it is shutting down. > Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException > : RunnableQueue not started or has exited > at org.apache.batik.util.RunnableQueue.invokeLater(Unknown Source) > at org.apache.batik.swing.svg.AbstractJSVGComponent. > updateRenderingTransform(Unknown Source) > at org.apache.batik.swing.gvt.AbstractJGVTComponent$1. > componentResized(Unknown Source) > at java.awt.AWTEventMulticaster.componentResized( > AWTEventMulticaster.java:142)
