I'm not sure I understand the question. The server sides on both machines are always on - the model is created/opened once when the server side is started. The http requests are processed separately - there is no session stored for http connection.
Alex -----Original Message----- From: Marco Neumann [mailto:[email protected]] Sent: Sunday, March 10, 2013 17:42 To: [email protected] Subject: Re: Two tdb instances using same data files they are non static connections? On Sun, Mar 10, 2013 at 11:40 AM, Alex Shapiro <[email protected]> wrote: > There is an external lock mechanism we use to prevent concurrent write. There > are simply no write requests that we allow to process in the same time. > > Alex > > > > -----Original Message----- > From: Marco Neumann [mailto:[email protected]] > Sent: Sunday, March 10, 2013 16:01 > To: [email protected] > Subject: Re: Two tdb instances using same data files > > how do you guarantee that there are no concurrent read/writes on the files in > the current setup? > > On Sun, Mar 10, 2013 at 9:33 AM, Alex Shapiro <[email protected]> > wrote: >> Generally there is a web services on each machine that passes the requests >> to tdb. >> We are using "TDBFactory.createModel(shared_files_dir_location)" to open a >> model. >> All the manipulations are done with "model" object. >> Yes, I know that this is a bad idea :-) We are working on this. >> >> Alex >> >> >> >> -----Original Message----- >> From: Marco Neumann [mailto:[email protected]] >> Sent: Sunday, March 10, 2013 15:20 >> To: [email protected] >> Subject: Re: Two tdb instances using same data files >> >> how do you access the tdb databases? in general it's a bad idea to grant >> access to the files to more than one client. >> >> >> >> >> On Sun, Mar 10, 2013 at 9:12 AM, Alex Shapiro <[email protected]> >> wrote: >>> Hi, >>> We have 2 tdb instances (2 JVMs on separate machines) that access the same >>> data files on shared location. No simultaneous WRITE operations are >>> allowed. The question is whether we should reset/update/close and open >>> again the model on second JVM after WRITE operation was executed on first >>> one? If the answer is yes - how do we do this? >>> We have an "old" version of tdb - 0.8.9. >>> >>> Thanks in advance, >>> >>> Alexander Shapiro >>> Software Engineer >>> dbMotion Ltd. >>> www.dbMotion.com >>> >>> >> >> >> >> -- >> >> >> --- >> Marco Neumann >> KONA >> >> > > > > -- > > > --- > Marco Neumann > KONA > > -- --- Marco Neumann KONA
