Newbie question... pointers needed

Question

Hi all,
Environment: Weblogic 6.1 SP2 Sun Solaris, Oracle 8.1.7
We've a large table where we need to assure that only one person at time
updates certains rows of it.
Currently we're using direct connections from the client with "select for
update" but we are suffering from the performance penalty of establishing
these connections instead of using connection pools... and this is driving
weblogic to a halt. Also there are a lot of connections to the database and
some of them might be stalled from killed clients
What's the best way to implement this type of code efficiently?
TIA,
Pedro Ortigão

Answer 1

My suggestion would be to use a connection pool, but I am not sure I
understand you situation well enough to come to that conclusion.
If you want to have only One person update a row at time. My suggestion,
and this is just one idea, would be to create a Singleton Class that has a
Synchronized list (or hashtable, or what ever would be easiest) of row keys
that are being updated. Only one user would be able to lock and unlock
a row at a time, but I don't think this will be a problem unless it takes a
long time to add something to your list of locked rows.
public class LockedRows
private LockedRows()//can't be instantiated outside this class
public static boolean isRowLocked(int rowId)
//if the rowId is in the list return true
//else return false
public static synchronized lockRow(int rowId)
//add to your list
public static synchronized unlockRow(int rowId)
//remove from your list or tree or hashtable
just an idea.
"newsgroups.bea.com" <[email protected]> wrote in message
news:[email protected]..
Hi all,
Environment: Weblogic 6.1 SP2 Sun Solaris, Oracle 8.1.7
We've a large table where we need to assure that only one person at time
updates certains rows of it.
Currently we're using direct connections from the client with "select for
update" but we are suffering from the performance penalty of establishing
these connections instead of using connection pools... and this is driving
weblogic to a halt. Also there are a lot of connections to the databaseand
some of them might be stalled from killed clients
What's the best way to implement this type of code efficiently?
TIA,
Pedro Ortigão