> Here's my work section, modeled after your example:
>
> public void execute(int num) throws SQLException {
> for (int i=0; i<num; i++) {
>
> parentCall.execute();
> // #1
> for (int j=0; j<9; j++) {
> childCall.execute();
> // #1
> }
> // #2
> }
> // #3
> conn.commit();
> }
In this loop are you using i or j to indicate what rows to operate on in
the stored procedure calls? If so there will be huge contention as each
thread will try to do the exact same things. Using clientNumber*num+i or
something like that would give a more realistic test if you're supposed to
be dividing up work between these threads.
Kris Jurka
