Hello Josh, Thank you for your answer. You can have a look at the link that I posted by viewing a version from Google's cache ;) - http://209.85.129.132/search?q=cache:I-ejIOo-xEgJ:63.246.22.60/browse/CONF-15826+escherproperties+concurrent&cd=1&hl=de&ct=clnk&gl=de&client=firefox-a (try "escherproperties concurrent" with Google).
We got the concurrent issue when reading a document. I'll try to send a proper stacktrace or code sample to reproduce the error. You mentioned non-obvious internal side-effects: That corresponds to the link that I gave you above. Thanks, Christopher -----Ursprüngliche Nachricht----- Von: Josh Micich [mailto:[email protected]] Gesendet: Montag, 22. Juni 2009 19:35 An: POI Developers List Betreff: Re: Concurrency issues in EscherProperties Hello Christopher, For the most part, POI does not support multi-threaded access to object instances. This issue is not well addressed in the documentation, but I guess a simple rule would be that as long as all threads perform read operations, concurrent access should be supported. If you are having concurrency problems, it probably means that at least one of your threads has changed common data. The offending data modification may obvious from the external API, in which case it's probably best for the client code to manage synchronization. On the other hand, the external API methods you are calling may look 'read only' but have some non-obvious internal side-effect (like lazy initialisation), and in this case POI should probably be synchronized internally to manage this. There is not enough information to diagnose your problem. The link you posted is protected. Please post the relevant stack trace(s) and/or some sample code the reproduces the bug. regards, Josh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
