thanx for reply
web try your solution but we still face the same problem
i don't guess this is the problem that's because :-
1 - in our web application we don't use updatable resultSet
we make update by issuing (update,delete,insert) transaction using
executeUpdate() method not by ResultSet method ( we use ResultSet only
for selection) .
2 - we don't make any modification on the client side
they still have Ingres II 3.0.2(int.lnx/105) on linux machine and
IngresII 9.0.4 (Su9.us5/105) on solaris and this applications work fine when
connected to IngresII in AIX but when we changed to Ingres 2006 on
solaris the problem appear.
3 - we try to solve the problem by upgrading to Ingres 2006 on the
client side but we have very bad performance so we back to the old
installtion.
4 - the problem appear only when we have heavy load when regular load
the applications work fine and the update statements successed
5 - in some situation when the user make 2 or 3 refersh the code
successed and the update operation is performed
we will be so glad for any more help
thanx all
regard
akaleek
---------------------------------
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games. _______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users
