Tom Lane wrote:
Edoardo Panfili <edoardo@xxxxxxxx> writes:
It seems that if I put some delay between calls to the servlet all goes
well. I can change lock level but ther is something wrong.
Obviously I am doiung something wrong. To unlock the tables is not
sufficient close the Statement and the Connection?
Um, possibly not, if you're using connection-pooling software ... and
even if you're not, I think closing the connection is asynchronous;
it'd be possible to establish a new connection before the old one has
terminated and released its locks.
Tnaks again.
Rather than closing the connection, I think you need to do something
explicit to commit your transaction.
I use connection.commit();
I spend many time to explain the bahaviour of the system:
I some occasions the system use another connection to retrieve some
information during the main connection. This explain the hangs but...
why sometimes the system works.
I do more tests.
Thanks a lot again
Edoardo
--
edoardo@xxxxxxxx
AIM: edoardopn
Jabber: edoardopa@xxxxxxxxxxxxxxx
tel:075 9142766
