Microsoft JDBC Driver Performance Degradation

We have been using Microsoft SQL Server JDBC Driver 2.2.0040 in our products
to connect to SQL Server 2000 Standard Edition SP3 (8.00.760). Our
functional testing went fine but we have run into serious performance
degradation under simulated heavy loads.
Our server crashed with OutOfMemory errors due to the inability to create
new native threads for the BaseQueryTimeoutEnforcer class in the JDBC driver
library. Right before crashing, we saw high thread counts went from 150 to as
high as 490. Thread counts were variable, so the thread count would decrease
and increase over time, until the last thread count reported 489 just before
crashing.
Total GC time was much higher as well due mostly to incremental GC times
that were almost 3x that of the benchmarked WebLogic's jDriver.
Correspondingly, response times were much higher.
I wonder if anyone else has experienced such problems.
Thanks,
Brian Luo
You better post this in microsoft.public.sqlserver.jdbcdriver
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Brian Luo" <Brian Luo@.discussions.microsoft.com> wrote in message
news:4652D65A-5666-41E3-9245-A572FEF907B8@.microsoft.com...
> We have been using Microsoft SQL Server JDBC Driver 2.2.0040 in our
> products
> to connect to SQL Server 2000 Standard Edition SP3 (8.00.760). Our
> functional testing went fine but we have run into serious performance
> degradation under simulated heavy loads.
> Our server crashed with OutOfMemory errors due to the inability to create
> new native threads for the BaseQueryTimeoutEnforcer class in the JDBC
> driver
> library. Right before crashing, we saw high thread counts went from 150 to
> as
> high as 490. Thread counts were variable, so the thread count would
> decrease
> and increase over time, until the last thread count reported 489 just
> before
> crashing.
> Total GC time was much higher as well due mostly to incremental GC times
> that were almost 3x that of the benchmarked WebLogic's jDriver.
> Correspondingly, response times were much higher.
> I wonder if anyone else has experienced such problems.
> Thanks,
> Brian Luo
|||Thanks for the info. Unfortunately, microsoft.public.sqlserver.jdbcdriver is
not listed as a managed newsgroup.
"Gert E.R. Drapers" wrote:

> You better post this in microsoft.public.sqlserver.jdbcdriver
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
> Copyright ? SQLDev.Net 1991-2004 All rights reserved.
> "Brian Luo" <Brian Luo@.discussions.microsoft.com> wrote in message
> news:4652D65A-5666-41E3-9245-A572FEF907B8@.microsoft.com...
>
>
|||Yes it is a managed newsgroup, see:
http://www.microsoft.com/sql/communi...r.jdbcdri ver
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Brian Luo" <BrianLuo@.discussions.microsoft.com> wrote in message
news:134481F8-0146-443F-9D38-1C84E84BFE8D@.microsoft.com...[vbcol=seagreen]
> Thanks for the info. Unfortunately, microsoft.public.sqlserver.jdbcdriver
> is
> not listed as a managed newsgroup.
> "Gert E.R. Drapers" wrote:
|||True, but please note that only "managed" customers (i.e. MSDN subscribers
posting using a registered alias) are guaranteed a response and you're not
posting from a registered alias. Even then, this is not the proper newsgroup
for this topic so even if somebody from the MSDN team does respond, which
isn't likely, they'll simply tell you that this is an off-topic post and
needs to be posted to the proper newsgroup even though it's not a managed
newsgroup and you won't get a response to your post. In short, if you
require a response from Microsoft on this topic, I think you're going to
have to open up a case with Product Support. Sorry!
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to the newsgroups only, thanks.
"Brian Luo" <BrianLuo@.discussions.microsoft.com> wrote in message
news:134481F8-0146-443F-9D38-1C84E84BFE8D@.microsoft.com...[vbcol=seagreen]
> Thanks for the info. Unfortunately, microsoft.public.sqlserver.jdbcdriver
> is
> not listed as a managed newsgroup.
> "Gert E.R. Drapers" wrote:
|||Correction, not managed as in the MSDN sense, sorry my bad. Anyhow the
jdbcdriver newsgroup is the best place to post this.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:%23WTUBI38EHA.1692@.TK2MSFTNGP10.phx.gbl...
> Yes it is a managed newsgroup, see:
> http://www.microsoft.com/sql/communi...r.jdbcdri ver
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Brian Luo" <BrianLuo@.discussions.microsoft.com> wrote in message
> news:134481F8-0146-443F-9D38-1C84E84BFE8D@.microsoft.com...
>