Hello,
 
Thank you, but how to find such operations ?!
 
I mean the application has about 50000 Source Code Lines.
 
Would it be the best to look at every class and remove the imports of 
 
org.w3c.dom.*
 
Then i would get every instance of a class in this package ?! so i would get 
every operation, then i could look in every method from where it was called => 
if not in a Runnable Queue ... found ?!
 
Or do you know something better ? 
 
Mit freundlichen Grüßen Michael Kerschbaum

 

DI (FH) Michael Kerschbaum

PKE Electronics AG

Zentrale Wien / Entwicklung

Computerstraße 6

A - 1101 Wien

TEL: +43 (0) 50 150 - 1210

[EMAIL PROTECTED]

www.pke.at <http://www.pke.at/>  

 

Aktiengesellschaft mit dem Sitz in Wien

Firmenbuchnummer 103264i

HG Wien, DVR 0159701

Johann Helf - Vorsitzender des Vorstandes

Bruno Faustka - Mitglied des Vorstandes

Christian Prelz - Vorsitzender des Aufsichtsrates

 

________________________________

Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 06. Oktober 2008 13:22
An: [email protected]
Cc: [email protected]
Betreff: Re: AW: How to create a RasterImageNode from BufferedImage



Hi Michael,

"Kerschbaum Michael " <[EMAIL PROTECTED]> wrote on 10/06/2008 04:13:36 AM:

> An Excexption like this 
>   
>  Batik-Err: Exception in thread "RunnableQueue-9" 
>  Batik-Err: java.util.ConcurrentModificationException
 [....] 
>  Batik-Err:    at 
> org.apache.batik.gvt.UpdateTracker.getDirtyAreas(UpdateTracker.java:71)

> looks like that somewhere the dom tree was manipulated outside off 
> the updateManager Thread ?! Is this correct ?! 

   This is correct.  The ConcurrentModificationException in the 
getDirtyAreas is almost certainly caused by updates outside 
of the UpdateManager thread. 

> And then something like that can happen ?! 
>   
> java.lang.IllegalStateException: RunnableQueue not started or has exited

> Because the UpdateManger died ? 

   Right again... 

> Is this correct ?! So if this would be correct i have to search for 
> maniplation of the domtree ?! 

   Right, somewhere you are changing the DOM outside of 
the UpdateManager thread. 

Reply via email to