Hello, We believe that we have solved all multi user related problems in Tamino WebDAV Server (which relies on the latest beta). We are not using the Slide Store cache and obey the token.isForceStoreEnlistment() flag (this is necessary for our sync. Of the low level caches). To my opinion the upper layers do not need synchronization (this would decrease performance too). I believe this is a problem of the Oracle store and/or the JDBC connection. Does the Oracle store open a distinct connection for each webdav command/thread?
Best regards Juergen -----Original Message----- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 07.54 AM To: Slide Developers List Subject: Re: Bug 3935 - was Re: [VOTE] Slide 1.0 final > Hi Remy, > > > Here's a recipe which i suspect will work: > > - set up say 10 threads each of which gets content (we're using the > JDBCDescriptor store with Oracle, and the FileContentStore), over and > over. The content we've been doing this with is several hundred kb. > > - while this is happening, store something in Slide - again, content of > several hundred kb. perhaps 30% of the time, Slide will crash. > > Note that Slide works fine for us unless there's a high load and at the > same time, writing content occurs. > > Over the next few days, I'll try to write a simple class which > reproduces the problem - at present, we use a load testing tool to > produce the problem. Given the description, it really looks to me like a race condition. At this point, I think we should try to sync everything transaction related and see what happens. Could you try and add a synchronized keyword to all the methods in AbstractSimpleService and try again ? It probably would be worth trying to sync the transaction manager methods too. The transaction itself doesn't need to be synced, since there's a 1-1 mapping between the transaction object and the thread. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
