Hi!

I had similar problems with Sybase ASE 11.9.2 some time ago. The problem was
with my app (mixed between autocommit settings and ejb-jar.xml settings to
each method).

I've used SapDB with JBoss (2.4.4 and 3.0) without problems some time ago
(sorry, I've no config file anymore - I even don't use JBoss anymore for
little projects, and I'll be careful to use in large ones. Don't blame me. I
love Java, but EJB are too complex to "let's see code running, don't
project" way of majority brazilian companies).

Just my2c.

Edson Richter


----- Original Message -----
From: "ajit_cus" <[EMAIL PROTECTED]>
To: "Schroeder, Alexander" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, October 09, 2002 8:46 AM
Subject: RE: Locked Tables (was Bug in sap JDBC drivers and Jboss+SAP?)


> Hi,
> >>>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.
> I don't switch the pooling of. I use a pooling class written by me.
>   My pool class maintains 45-60 connection and never closes a connection.
It only removes connections that are closed by the db server due to session
timeouts and gets a new connection for those. The dbtrace when using my
connection pool does not show any calls to get/setautocommit().
> My app runs perfectly with this class.no updates are lost because all
queries are executed with autocommit set on by default. (I have checked
this--> all updates,deletes,inserts are immediately reflected in  sqlstudio
when using my connection pool and by the way I never see a lock in the
domain.locks either(assume its due to autocommit)).The same application/same
code works with both oracle/postgreSQL JBOSS3.0 connection pooling so I'm
sure something is broke in SAPDB+JBOSS3.0.
> I haven't been able to locate anyone else using
JBOSS3.0+SAPDB+connectionpooling.Also I noticed that Jboss.org does not have
a sapdb connection pool sample xml for JBOSS 3.0+.They only have a SAP DB
connection source.
> What I don't understand is why the jboss transaction manager is setting
autocommit to false when executing some of my own queries and why it does
not do this consistently? (I make no request for beginning/ending a
transaction.)
>    I would like to use jboss connection pool but will continue to use my
own connection pooling until someone finds a fix.
> -Ajit
>
>
> -----Original Message-----
> From: Schroeder, Alexander [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 09, 2002 4:54 PM
> To: ajit_cus; Sapdb. General@Listserv. Sap. Com
> Subject: Locked Tables (was Bug in sap JDBC drivers and Jboss+SAP?)
>
> 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
>
>


---
Email foi verificado quanto a exist�ncia de virus antes de seu envio, e n�o
h� virus.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.394 / Virus Database: 224 - Release Date: 03/10/2002


_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to