Jukka, Your level of understanding of transaction processing is truly remarkable.
If you actually read the blog entry (after taking the blindfolds off your eyes) you would see that in fact in this case reported, JackRabbit did the unthinkable of using the same connection across threads while the connection was already active performing a transaction (autocommit=false) on behalf of another thread. This is not a JXInsight/Java codified standard this is an industry standard in transaction processing. By the way there are many other entries on the blog that show even concurrency at the statement level across threads with results be closing inadvertently by other threads. For your information these were a real world customer (not anymore) that performed some standard benchmarking with a high enough load and had corruption problems both at the database and in memory data structures. http://jira.jboss.com/jira/browse/JBPORTAL-1187 regards, William Jukka Zitting wrote: > > Hi, > > On 10/3/07, Peter Travas <[EMAIL PROTECTED]> wrote: >> I've hit this page: http://blog.jinspired.com/?p=40 when reading about >> JSR >> on http://www.infoq.com/articles/spring-modules-jcr >> [...] >> Has this issue been already addressed? If so, in which version (bug id >> reference)? >> It sounds quite serious, I think that you should post a reply on this >> thread >> because it sounds scary. > > There was some discussion about that on TSS some time ago, see the > comments on http://www.theserverside.com/news/thread.tss?thread_id=45763. > > It seems that most of the issues raised by JXInsight were just cases > where the Jackrabbit code actually works correctly but doesn't follow > the JDBC/J2EE practices as codified in JXInsight. For example one of > the central practices that JXInsight seems to worry about is not using > a single JDBC connection from multiple different threads. This would > most likely be a big problem if the threads were accessing the > connection concurrently, but in Jackrabbit's case such access is > normally explicitly synchronized - a crucial fact that the JXInsight > analysis doesn't notice. > > So far we've yet to see a real-world bug report related to the issues > raised in the blog entries you referred to, so I don't consider them > too serious even if these are real problems. I'd certainly welcome > someone to dig deeper to the results. There seems to be a free > developer version of the JXInsight tool available, if someone is > interested. > > BR, > > Jukka Zitting > > -- View this message in context: http://www.nabble.com/Is-this-issue-resolved--tf4561381.html#a13099553 Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
