> 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).
It shouldn't be significant, as the methods do very simple operations. I'd like Michael to try that, to see if it helps him. The thing is that you're probably not using the same service abstract implementation (it's AbstractSimpleService here), and that may be this class which would need some syncing. Also, the store (which extends the abstract service) should be able by itself to ensure thread safety, so that may also be why it works for you. > 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? I don't think it is here. The problem is an invalid transaction state being reported by the abstract service class. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
