Pessimistic Lock in Web Application
4566May 21 2003 — edited May 27 2003I am going to state all of this the best I know how and maybe this will allow me to formulate a better question if needed.
My team is designing a web application that will be a COTS integration along with custom written java screens.
The current system has approximately 500 users, with up to 300 concurrent sessions. However there would probably be less than 50 updating data at one time.
The custom java screens will be used to input structured data into our 9i Database. We are planning on using 9iAS as our application Server also. These screens will not be the only way to manipulate the data. There will be processes running and of course maintenance going on that may modify data. We want to use stateless sessions as much as possible, primarily viewing data, but when a user goes to update a record we, especially me, want to have a pessimistic lock to protect the data. Our current test environment consists of 4 Dell Poweredge servers. They each have 1 gig of ram and one 2GHZ proccessor. One is running linux with 9i, One running on windows 2000 server with 9iAS. The other two are to be used for an external webserver and project machine and the other is for GIS. Production machines will be at least double he size.
I have seen BC4J discussed when researching this and wondered what part this plays in locking rows?
What is the best way to accomplish the database lock?
Given others experience what kind of performance issues am I going to have?
Sorry for the rambling, but if anyone has any insight I would appreciate it greatly.