Reto wrote: > I have investigated this and have done some multithreaded tests with > AWTRenderer a few months ago. The conclusions can be found in the archives > of this list. > Summary: > - AWTRenderer and all subclasses of it (TIFFRenderer...) are NOT > threadsave. > - It is not threadsave because the underlaying AWT libs are not > threadsave. > It does not help to use different instances of REnderer, Driver , or > anything else. You need different VMs to run AWTRenderer concurrently. > - There is no simple way to adjust AWTRenderer to be threadsave. It > probabaly needs a complete redesign - I don't think it is even possible to > make an "AWTRenderer" threadsave, since it would have to be > written without > using AWT.
Yes, your comments are the ones that I referenced in my answer, and they were very helpful. The only thing that troubles me is that although it is well-documented that Swing classes are not thread-safe, I can find nothing similar for AWT, so I am hesitant to list that as the cause. For now, I have documented that the AWT Renderer should not be multi-threaded, but have not documented why. Victor Mote --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
