Hi Ajis, after looking at the trace I cannot see something weird, and/or unusual, aside that there is never a 'commit' call in your servlet/bean which will result in updates being kind of 'pending'.
So I assume there is a state originated in your application, which results in some deadlock or similar phenomen. I can only recommend here to make a 'SELECT * FROM LOCKSTATISTICS' in case when this happens, and carefully look on the output of this. I think that the insert/update on your 'services' table will not be committed, and thus the next read on the same row will see the pending update and will not be able to establish the read lock on that row. The reason why this did not so much happen when the pooling is off may simply be that a connection is the closed, and thus the stuff is rolled back and released 'automatically'. You might have lost some updates in this case, however, but no lock persisting. Regards Alexander Schr�der > -----Original Message----- > From: ajit_cus [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 09, 2002 12:08 PM > To: Schroeder, Alexander > Subject: RE: Bug in sap JDBC drivers and Jboss+SAP > > > Hi, > I attach a sample database trace. Note that my application > stalls and I can see row_exclusive locks in domain.locks > using sqlstudio. The locks persist for a long time. Went > through the trace and the autocommit setting is not always > true when executing queries. > Any assistance will be much appreciated. > Thanks, > Ajit > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
