but makes other requests wait even though there are 50 processes allocated
to handle connection requests.
[System]
SAPDB v7.3.0.34 (w/ corresponding JDBC driver)
SuSE v8.1
Java v1.4.1_01
Tomcat v4.1.18
[Background]
I have two jsp webapps that access a single sapdb instance but each with a
different user account that own their respective application database
objects.
***One app uses SSL and the other does not.***
[Issues]
One process seems to be handling 99.9% of all the service requests. This
holds true even when other requests are waiting to be serviced while this
one process is busy.
A second problem is that it seems that read queries are locking down tables.
I may be mistaken but we have one table that is huge and whenever an
intensive query is ran it locks out other users wanting to access the table
with a read query.
Any advice on parameters to tweak, etc. would be appreciated.
Thanks,
Kevin
"Those who would give up essential liberty to purchase a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, 1759
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
