Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts

Friday, March 30, 2012

Microsoft SQL Server 2005 JDBC Driver 1.1 on Solaris

hi,

Does MS2005 JDBC Driver 1.1 support integrated security on Solaris and if so
how?

Thanks,
MarcMOn Apr 24, 10:44 am, "Marc Melancon" <mmela...@.bmc.comwrote:

Quote:

Originally Posted by

hi,
>
Does MS2005 JDBC Driver 1.1 support integrated security on Solaris and if so
how?
>
Thanks,
MarcM


There's no such thing as integrated security between Solaris and MS.

Microsoft SQL Server 2005 JDBC Driver

Hi, will there be a Windows Mobile edition of this driver, so that is possible to connect to SQL Everywhere on a Pocket PC from Java ME apps?

Best regards.

Luca

Luca:

There are currently no plans for a Java ME JDBC driver for SQL Everywhere but we evaluate customer demand on a regular basis. If you have a particular scenario that you think is especially compelling feel free to reply to this forum or mail me directly (shelbyg at microsoft dot com).

-shelby

Shelby Goerlitz

Microsoft SQL Server Data Programmability

Microsoft SQL Server 2005 JDBC Driver

Hi, will there be a Windows Mobile edition of this driver, so that is possible to connect to SQL Everywhere on a Pocket PC from Java ME apps?

Best regards.

Luca

Luca:

There are currently no plans for a Java ME JDBC driver for SQL Everywhere but we evaluate customer demand on a regular basis. If you have a particular scenario that you think is especially compelling feel free to reply to this forum or mail me directly (shelbyg at microsoft dot com).

-shelby

Shelby Goerlitz

Microsoft SQL Server Data Programmability

Microsoft SQL Server 2005 JDBC Driver

I'm getting the following exception when attempting to connect to SQL Server 2005 using Microsoft's new JDBC driver:

com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect

The help docs suggest checking connectivity using telnet. So attempting to connect via telnet to 127.0.0.1:1433 generates:

Could not open connection to the host, on port 23: Connect failed.

So I try to start telnet:

net start telnet

I get the following error message:

The service cannot be started either because it is disabled or because it has no enables devices associated with it.

Can anyone help?

Thanks

It seems that the TCP protocols is not enabled on your SQL Server.

You may need to enable TCP and *restart* SQL Server.

An article on how to do it for SQL Express is at http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx. The steps are similar for any other edition of SQL Server 2005.

|||

Thanks Peter; TCP/IP was enabled,I must have broken something else during my experimentation with Telnet. I reinstalled the OS and it worked OK.

Duncan

sql

Wednesday, March 28, 2012

Microsoft SQL Server 2000 JDBC Driver issue

I was wondering if anybody has run into the following problem with ms's
jdbc driver. We're using cursors in our app - when we create a
java.sql.Statement object in the app, we're indicating that we want the
corresponding ResultSet object to have a TYPE_FORWARD_ONLY cursor.
We've noticed when we do this that if the app executes a query with
'UNION's in it, it never gets a ResultSet back from the server (I've
noticed on the SQL server profiler that it stays stuck doing the 'exec
sp_cursoropen' call). If we change the resultSetType to
TYPE_SCROLL_INSENSITIVE then the query returns in no time.
Any ideas?
Thanks.
--Yogesh
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
joe wrote:

> I was wondering if anybody has run into the following problem with ms's
> jdbc driver. We're using cursors in our app - when we create a
> java.sql.Statement object in the app, we're indicating that we want the
> corresponding ResultSet object to have a TYPE_FORWARD_ONLY cursor.
> We've noticed when we do this that if the app executes a query with
> 'UNION's in it, it never gets a ResultSet back from the server (I've
> noticed on the SQL server profiler that it stays stuck doing the 'exec
> sp_cursoropen' call). If we change the resultSetType to
> TYPE_SCROLL_INSENSITIVE then the query returns in no time.
If you can show an example of your code, it'll help.
If you do a trivial query like "select * from sysdatabases UNION select * from sysdatabases"
that hangs?
thanks
Joe

> Any ideas?
> Thanks.
> --Yogesh
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
sql

Friday, March 23, 2012

Microsoft OLE DB Provider for ODBC Drivers error 8007000e

Microsoft OLE DB Provider for ODBC Drivers error '8007000e'
[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

I recieve this error every time I execute SQL statement form ASP page on an Access database.
Could any one help me diagnosing this problem and how to avoid seeing such error messages.

ThanksI FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p|||Originally posted by Khalid
I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p

I have this problem (about access database sending "Resources Exceeded Error") my largest table has 350,000+ Registers. Might this be causing the problem? I tried deleteing 10,000 registers aout of the table but it didn't work.

It just happened after more than 1 year of mu application running perfectly fine.

You can see the error in: http://www.citaris.com/checarplayer.jhtml

Please let me know if you need any other information.

Best regards and thank you very much,.

Alexis.
acastanares@.yahoo.com|||Originally posted by Khalid
I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p Khalid, can you help me out? I've been getting this error for a few weeks now. Thanks|||Khalid,
It would be most helpful if you'd post the solution here, rather than make everyone who has this problem email you for it.

VRWL :rolleyes:

Originally posted by Khalid
I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p|||I received lately a lot of emails asking about this famous error problem.
this is my solution I have discovered:

ASP is full of bugs, as I discovered lately, but these bugs can be solved by writing code.

My problem was due to Database connections, it seem to me I was doing the perfect thing, opening connections, recordsets, executing queries and finally I destroy every object I create.

THE PROBLEM
===========
If you open only one connection (as I used to do), and run more than one query or recordsets at the same time, what is happening? ASP does not allow you to run more than one query through the same connection at the same time, (though it seems that it is working) so how come? Since ASP does not allow that, it creates its own connections to run the further queries you are executing, and after you are done with them, ASP is not destroying the connections it creates. If you are not destroying your connection objects as well, so you are helping the problem to come up.

WHAT IS HAPPENING
==================
unclosed objects will create a resource leak in memory, and as the times goes, more objects are not closed, and more memory resources are consumed until it reaches to the maximum. And guess what, the famous message will show up! :rolleyes:

SOLUTION
=========
-Define a connection for every query by its own.
-Create you connection object and destroy them your self, don't let ASP do any thing by its self. :D

Hope this information be helpful for every body.

Cheers

;)|||Yes but... Why if i have two servers, one with a single PIII 500 Mhz and 256 Mb Ram and other with Dual PIII 1 ghz an 1 Gb Ram... with the same web page and with the same Operatin System, I got the problem in the Dual PIII and not in the oldest server?|||Hi,
after reading an article, I am using a jdbc:odbc bridge with an excel file setup as a user dsn. This is to import and export from our java applciation and jdbc database to excel. On XP and 2003 server machines, there is no problem. However, on 2000 server machines, they all get 'system resources exceeded' message and fail to do anything.

Can anyone help with identifying the underlying problem and recommend a solution ? Is there a a buggy MS component or something that needs updating? HELP!!!

thanks in advance,
Neil|||iamneil
As I have described previously, you are getting this message because your application is causing memory leak. This happens due to many causes, I have discovered that in my ASP application, IIS is opening more connections when I try to run more than SQL statement at the same time on one connections, so IIS is creating its own connections and it is not closing those connections when done with them.
If the application is working on heavy traffic those unclosed connections will be consuming the resource of the system untill it reaches the maxium.

So try to find out where is your bug that causes a memory leak.

Check out your application and tell me more about it.

Good luck|||Need Help with this issue.

Pretty Sure that the Problem is that there is a Memory Leak within the Page. It randomly just started Popping Up Non-Stop about Temporary Disk Space.

But here's where I need help - I'm a new webmaster at one of AAA Auto Clubs Divisions, and the Previous webmaster loved ASP Scripting. I personally favor PHP, because I have more experience with it.

But The Employees Here need to get this working up and running ASAP -

It's Pretty Obvious that The Script Used is from ASP Calendar -- But I can't just simply Download another Version of ASP Calendar and Overwrite the File because the Files Have Been Modified to Work Better for the Employees Uses.

Here Is the Exact Error Message I Am Receiving

Microsoft OLE DB Provider for ODBC Drivers error '8007000e'
[Microsoft][ODBC Microsoft Access Driver] Not enough space on temporary disk.
/Calendar/calendar.asp, line 222

Here is the Coding For calendar.asp



--
6 hours trying to find what this error code was from, how it was happening, and trying to find the resource to fix it was Extremely Frustrating.

So if you can help in anyway, it will be greatly appreciated. Plus if you throw in some Educational snippits (comments in the code) of What this part of the script does and what this part of the script does. It would help tremondously!|||<!-- #include file ="dsn.asp" -->
<!-- #include file="adovbs.inc" -->
<%
' Name: ASP Calendar
' Author: Manohar Kamath
' Version: 1.0
' Copyright Manohar Kamath. Original calendar copyright Wrox Press
%>
<%
' catch department and status name from login page
Dim Dept, intStat, strEvents
Dept=Request("Dept")
intStat=Request("intStat")
strEvents=""
%>
<%
'------------------
' This function finds the last date of the given month
'------------------
Function GetLastDay(intMonthNum, intYearNum)
Dim dNextStart
If CInt(intMonthNum) = 12 Then
dNextStart = CDate( "1/1/" & intYearNum)
Else
dNextStart = CDate(intMonthNum + 1 & "/1/" & intYearNum)
End If
GetLastDay = Day(dNextStart - 1)
End Function

'----------------------
' This routine prints the individual table divisions for days of the month
'----------------------
Sub Write_TD(sValue, sClass)
Response.Write " <TD ALIGN='RIGHT' WIDTH=14% HEIGHT=80 VALIGN='top' CLASS='" & sClass & "'> " & sValue & "</TD>" & vbCrLf
End Sub

' Constants for the days of the week
Const cSUN = 1, cMON = 2, cTUE = 3, cWED = 4, cTHU = 5, cFRI = 6, cSAT = 7

' Get the name of this file
sScript = Request.ServerVariables("SCRIPT_NAME")

' Check for valid month input
If IsEmpty(Request("MONTH")) OR NOT IsNumeric(Request("MONTH")) Then
datToday = Date()
intThisMonth = Month(datToday)
ElseIf CInt(Request("MONTH")) < 1 OR CInt(Request("MONTH")) > 12 Then
datToday = Date()
intThisMonth = Month(datToday)
Else
intThisMonth = CInt(Request("MONTH"))
End If

' Check for valid year input
If IsEmpty(Request("YEAR")) OR NOT IsNumeric(Request("YEAR")) Then
datToday = Date()
intThisYear = Year(datToday)
Else
intThisYear = CInt(Request("YEAR"))
End If

strMonthName = MonthName(intThisMonth)
datFirstDay = DateSerial(intThisYear, intThisMonth, 1)
intFirstWeekDay = WeekDay(datFirstDay, vbSunday)
intLastDay = GetLastDay(intThisMonth, intThisYear)

' Get the previous month and year
intPrevMonth = intThisMonth - 1
If intPrevMonth = 0 Then
intPrevMonth = 12
intPrevYear = intThisYear - 1
Else
intPrevYear = intThisYear
End If

' Get the next month and year
intNextMonth = intThisMonth + 1
If intNextMonth > 12 Then
intNextMonth = 1
intNextYear = intThisYear + 1
Else
intNextYear = intThisYear
End If

' Get the last day of previous month. Using this, find the sunday of
' last week of last month
LastMonthDate = GetLastDay(intLastMonth, intPrevYear) - intFirstWeekDay + 2
NextMonthDate = 1

' Initialize the print day to 1
intPrintDay = 1

%>

<html>
<head>
<meta HTTP-EQUIV="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Vacation Schedule</title>
<style TYPE="text/css">
TD.NON {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#C0C0C0; font-weight :normal;}
TD.TOP {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#0000FF; font-weight :bold;}
TD.Some {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :normal;}

A.NOEVENT:Link {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :normal; text-decoration: none;}
A.NOEVENT:Visited {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :normal; text-decoration: none;}

A.EVENT:Link {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :bold; text-decoration: none;}
A.EVENT:Visited {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :bold; text-decoration: none;}

A.NORMAL:Link {font-family :Verdana, Arial; font-size :12px; color :#0000FF; font-weight :normal; text-decoration: none;}
A.NORMAL:Visited {font-family :Verdana, Arial; font-size :12px; color :#0000FF; font-weight :normal; text-decoration: none;}
</style>
</head>

<body LEFTMARGIN="3" BGCOLOR="#FFFFFF" TEXT="#000000">
<p> </p>
<h2 align="center">Vacation Schedule Calendar</h2>
<h3 align="center"><%=Dept %></h3>
<p align=center><a href="http://links.10026.com/?link=default.asp">Choose a different department/branch</a></p>
<FORM ACTION="<% =sScript%>?Dept=<% =Dept %>&intStat=<% =intStat %>" METHOD=GET >
<font face="Verdana, Arial" size="2">

<div align="center">Select month and year:
<SELECT NAME=MONTH>
<OPTION VALUE=1 SELECTED>Jan
<OPTION VALUE=2>Feb
<OPTION VALUE=3>Mar
<OPTION VALUE=4>Apr
<OPTION VALUE=5>May
<OPTION VALUE=6>Jun
<OPTION VALUE=7>Jul
<OPTION VALUE=8>Aug
<OPTION VALUE=9>Sep
<OPTION VALUE=10>Oct
<OPTION VALUE=11>Nov
<OPTION VALUE=12>Dec
</SELECT>
<SELECT NAME=YEAR>
<option value="2006" selected>2006</option>
</SELECT>
<input type="hidden" name="Dept" value=<% =Dept %>>
<input type="hidden" name="intStat" value=<% =intStat %>>
<input type="submit" name="Submit" value="Go!">
<! INPUT TYPE="Image" NAME="" src="http://pics.10026.com/?src=images/go.gif" BORDER="0" WIDTH="35" HEIGHT="20">
</div>
</font>
</FORM>
<table ALIGN="CENTER" BORDER="1" CELLSPACING="0" CELLPADDING="2" BGCOLOR="White" BORDERCOLOR="Gray" width="75%">
<tr><td>
<table BORDER="1" CELLPADDING="1" CELLSPACING="0" BGCOLOR="#FFFFFF" width="100%">
<tr HEIGHT="18" BGCOLOR="Silver">
<td WIDTH="14%" HEIGHT="18" ALIGN="LEFT" VALIGN="MIDDLE">
<div align="center"><a href="http://links.10026.com/?link=<% =sScript%>?month=<% =IntPrevMonth %>&year=<% =IntPrevYear %>&Dept=<% =Dept %>&intStat=<% =intStat %>"><img src="http://pics.10026.com/?src=images/prev.gif" WIDTH="14" HEIGHT="14" BORDER="0" ALT="Previous Month"></a></div>
</td>
<td WIDTH="*" COLSPAN="5" ALIGN="CENTER" VALIGN="MIDDLE" CLASS="SOME"><font size=+1><b>
<% = strMonthName & " " & intThisYear %>
</b> </font></td>
<td WIDTH="14%" HEIGHT="18" ALIGN="RIGHT" VALIGN="MIDDLE">
<div align="center"><a href="http://links.10026.com/?link=<% =sScript %>?month=<% =IntNextMonth %>&year=<% =IntNextYear %>&Dept=<% =Dept %>&intStat=<% =intStat %>"><img src="http://pics.10026.com/?src=images/next.gif" WIDTH="14" HEIGHT="14" BORDER="0" ALT="Next Month"></a></div>
</td>
</tr>
<tr>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Sunday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Monday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Tuesday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Wednesday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Thursday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Friday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Saturday</td>
</tr>

<%

' Initialize the end of rows flag to false
EndRows = False
Response.Write vbCrLf

' Loop until all the rows are exhausted
Do While EndRows = False

' Start a table row
Response.Write " <TR>" & vbCrLf
' This is the loop for the days in the week
For intLoopDay = cSUN To cSAT
' If the first day is not sunday then print the last days of previous month in grayed font
If intFirstWeekDay > cSUN Then
Write_TD LastMonthDate, "NON"
LastMonthDate = LastMonthDate + 1
intFirstWeekDay = intFirstWeekDay - 1
' The month starts on a sunday
Else
' If the dates for the month are exhausted, start printing next month's dates
' in grayed font
If intPrintDay > intLastDay Then
Write_TD NextMonthDate, "NON"
NextMonthDate = NextMonthDate + 1
EndRows = True
Else
' If last day of the month, flag the end of the row
If intPrintDay = intLastDay Then
EndRows = True
End If

dToday = CDate(intThisMonth & "/" & intPrintDay & "/" & intThisYear)

' Open a record set of schedules
Set Rs = Server.CreateObject("ADODB.RecordSet")

sSQL = "SELECT * FROM tEvents WHERE " & _
"Start_Date =#" & dToday & "# " & _
"AND (Dept='" & Dept & _
"' OR Dept='all')" & _
" ORDER BY Start_Date"

' Open the RecordSet with a static cursor. This cursor provides bi-directional navigation
Rs.Open sSQL, sDSN, adOpenStatic, adLockReadOnly, adCmdText

If NOT Rs.EOF Then

bEvents = True
Do While NOT Rs.EOF

' build list of events for day
'If logged in as manager or during initial entry period, include delete option, else display only names
If intStat = 2 AND Rs("Dept") <> "all" Then
strEvents = strEvents & Rs("Event_Title") & "<a href='delete.asp?Event_ID=" & Rs("Event_ID") & "&Dept=" & Dept & "&intStat=" & intStat & "'><font size=-2 color=red>DEL</font></a><br>"
Else
strEvents = strEvents & Rs("Event_Title") & "<br>"
End If

Rs.MoveNext

Loop

Else

bEvents = False

End If

Rs.Close
Set Rs = Nothing

' If the event flag is not raise for that day, print it in a plain font
If bEvents = False Then
Write_TD intPrintDay, "SOME"
Else
Write_TD intPrintDay & "<br>" & strEvents, "SOME"
strEvents = ""

End If

End If


' Increment the date. Done once in the loop.

intPrintDay = intPrintDay + 1
'clear list of events
strEvents = ""
End If

' Move to the next day in the week

Next
Response.Write " </TR>" & vbCrLf

Loop

%>
</table>
</td></tr>
</table>|||I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p

I experiencing the same problem I can not find the solution. Please let me know how to solve

Microsoft ODBC Sql server driver Communication Link Failure

I get the message Microsoft [ODBC Sql server driver]communication link failure error message in my VB 6 application with MSDE engine. This error does not happen often.
My connection string is as below.

"Provider=MSDASQL;Driver={SQL Server};Server=" & mSvrName & ";DATABASE=cnsClient;uid=uid;pwd=pwd"

Please help.Were you able to figure out a solution? It seems like a ODBC specific error more than a MSSQL one. I get the same error when trying execute queries against a DB2 database.

Microsoft ODBC sql driver cannot generate sspi context

Hi,
I am facing a connection error occasionally. Im using MSDE2000a and
Dbamgr2k. The connection seems to have the following error
occasionally. Can anyone of u help me to troubleshoot this problem?
thank you.
Connection Failed
SQLState: 'HY000'
SQL Server Error: 1364
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
Regards,
JustinJustin wrote:
> Hi,
> I am facing a connection error occasionally. Im using MSDE2000a and
> Dbamgr2k. The connection seems to have the following error
> occasionally. Can anyone of u help me to troubleshoot this problem?
> thank you.
> Connection Failed
> SQLState: 'HY000'
> SQL Server Error: 1364
> [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
> Regards,
> Justin
>
Are you connecting with a Windows account in a domain? If so, the machine r
unning SQL Server may have lost connection
to the domain controller and can't authenticate your account credentials. S
earch MS support.|||Thanx Ed Enstrom for your reply. I don't really get what you meant.
Maybe i should elaborate more on this. The pc is a standalone pc, OS is
xp pro, database using msde2000a. The error comes out from no where.
There are times which im able to connect to the sql server but
sometimes it shows the error of microsoft odbc sql server cannot
generate sspi context. Should i connect using the "sa" or by "trusted
NT connection" in dbamgr2k'
p/s: sorry, im a newbie here. thanx for your patience.
regards,
justin|||What Ed means by "Search MS support" is to search the MSDN and/or TechNet,
including the KB. I searched an old version of the MSDN for "Cannot generate
SSPI context" and got one result that says that the "native error will
contain the Win32 error code".
"Justin" <justin@.smsit.com.my> wrote in message
news:1135235596.227999.154030@.z14g2000cwz.googlegroups.com...
> Thanx Ed Enstrom for your reply. I don't really get what you meant.

Microsoft JDBC Driver XA Problem

Hi,
I have applied XA support via the dll and script...but now I got the
following error. Anyone can point me a direction to fix this?
Thanks,
j-
20:44:06 [tyrex.resource.n3-db] [main] [transaction server is recovering] []
[] ERROR - Failed to create connection for default user
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]xa_open (0) returns -3
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown
Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.exec uteUpdate(Unknown Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.open(Unknown Source)
at com.microsoft.jdbcx.base.BaseXAConnection.<init>(U nknown Source)
at com.microsoft.jdbcx.base.BaseXADataSource.getXACon nection(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerDataSource. getXAConnection(Unknown
Source)
at
tyrex.resource.jdbc.ConnectionPool.createPooledCon nection(ConnectionPool.java:841)
at
tyrex.resource.jdbc.ConnectionPool.completeInit(Co nnectionPool.java:256)
at
tyrex.resource.jdbc.ConnectionPool.<init>(Connecti onPool.java:222)
at
tyrex.resource.jdbc.DataSourceConfig.createResourc e_(DataSourceConfig.java:237)
at
tyrex.resource.ResourceConfig.createResource(Resou rceConfig.java:390)
at tyrex.resource.Resources.getResource(Resources.jav a:235)
at
tyrex.tm.impl.TransactionServerImpl.recover(Transa ctionServerImpl.java:582)
at
com.intalio.n3.common.tyrex.TyrexModule.initialize (TyrexModule.java:130)
at
com.intalio.n3.common.module.ModulesManager.initia lizeModule(ModulesManager.java:373)
at
com.intalio.n3.common.module.ModulesManager.initia lizeAllModules(ModulesManager.java:263)
at com.intalio.n3.Main.start(Main.java:454)
at com.intalio.n3.Main.main(Main.java:239)
20:44:09 [tyrex.resource.n3-db] [main] [null] [] [] ERROR - Failed to create
connection for default user java.sql.SQLException: [Microsoft][SQLServer
2000 Driver for JDBC][SQLServer]xa_open (0) returns -3
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown
Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.exec uteUpdate(Unknown Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.open(Unknown Source)
at com.microsoft.jdbcx.base.BaseXAConnection.<init>(U nknown Source)
at com.microsoft.jdbcx.base.BaseXADataSource.getXACon nection(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerDataSource. getXAConnection(Unknown
Source)
at
tyrex.resource.jdbc.ConnectionPool.createPooledCon nection(ConnectionPool.java:841)
at
tyrex.resource.jdbc.ConnectionPool.completeInit(Co nnectionPool.java:256)
at
tyrex.resource.jdbc.ConnectionPool.<init>(Connecti onPool.java:222)
at
tyrex.resource.jdbc.DataSourceConfig.createResourc e_(DataSourceConfig.java:237)
at
tyrex.resource.ResourceConfig.createResource(Resou rceConfig.java:390)
at tyrex.resource.Resources.getResource(Resources.jav a:235)
at
tyrex.tm.impl.TransactionServerImpl.recover(Transa ctionServerImpl.java:626)
at
com.intalio.n3.common.tyrex.TyrexModule.initialize (TyrexModule.java:130)
at
com.intalio.n3.common.module.ModulesManager.initia lizeModule(ModulesManager.java:373)
at
com.intalio.n3.common.module.ModulesManager.initia lizeAllModules(ModulesManager.java:263)
at com.intalio.n3.Main.start(Main.java:454)
at com.intalio.n3.Main.main(Main.java:239)
20:44:10 [n3.common.module] [main] [null] [] [] WARN - Failed the initialize
module 'TransactionManager'
20:44:10 [n3.common.module] [main] [null] [] [] FATAL - ModulesManager
tyrex.resource.ResourceException: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]xa_open (0) returns -3
at
tyrex.resource.jdbc.ConnectionPool.<init>(Connecti onPool.java:225)
at
tyrex.resource.jdbc.DataSourceConfig.createResourc e_(DataSourceConfig.java:237)
at
tyrex.resource.ResourceConfig.createResource(Resou rceConfig.java:390)
at tyrex.resource.Resources.getResource(Resources.jav a:235)
at
tyrex.tm.impl.TransactionServerImpl.recover(Transa ctionServerImpl.java:582)
at
com.intalio.n3.common.tyrex.TyrexModule.initialize (TyrexModule.java:130)
at
com.intalio.n3.common.module.ModulesManager.initia lizeModule(ModulesManager.java:373)
at
com.intalio.n3.common.module.ModulesManager.initia lizeAllModules(ModulesManager.java:263)
at com.intalio.n3.Main.start(Main.java:454)
at com.intalio.n3.Main.main(Main.java:239)
Jay Shen wrote:
> Hi,
> I have applied XA support via the dll and script...but now I got the
> following error. Anyone can point me a direction to fix this?
> Thanks,
> j-
> 20:44:06 [tyrex.resource.n3-db] [main] [transaction server is recovering] []
> [] ERROR - Failed to create connection for default user
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
> JDBC][SQLServer]xa_open (0) returns -3
> at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Hi Jay,
Seems, that you haven't started the DTC (Distributed Transaction
Coordinator) service. This service is installed during the
MS SQL Server 2000 installation but with start type 'manual'.
BTW: which user do you use to connetc to the database ? If you don't
use sa (which would be a good idea) have in mind, that XA recovery is
only allowed for a system administrator. To allow all users to perform
XA recovery, you have to add the EXEC permission to PUBLIC for the
stored procedure xp_jdbc_recover (part of extended stored procedures) in
the master database.
Best,
Manfred
|||Thanks a lot, Manfred.
I did apply the suggestion to grant the rights. But for some reason, I am
still getting the same errors...weird...
"Manfred Rosenboom" <marochess@.gmx.de> wrote in message
news:d3dpcu$d6c$1@.nntp.fujitsu-siemens.com...
> Jay Shen wrote:
> Hi Jay,
> Seems, that you haven't started the DTC (Distributed Transaction
> Coordinator) service. This service is installed during the
> MS SQL Server 2000 installation but with start type 'manual'.
> BTW: which user do you use to connetc to the database ? If you don't
> use sa (which would be a good idea) have in mind, that XA recovery is
> only allowed for a system administrator. To allow all users to perform
> XA recovery, you have to add the EXEC permission to PUBLIC for the stored
> procedure xp_jdbc_recover (part of extended stored procedures) in the
> master database.
> Best,
> Manfred
|||| From: "Jay Shen" <jay_shen@.msn.com>
| References: <eGLZClkPFHA.248@.TK2MSFTNGP15.phx.gbl>
<d3dpcu$d6c$1@.nntp.fujitsu-siemens.com>
| Subject: Re: Microsoft JDBC Driver XA Problem
| Date: Mon, 11 Apr 2005 14:13:59 -0700
| Lines: 38
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Response
| Message-ID: <eTZJittPFHA.4004@.TK2MSFTNGP15.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: adsl-67-113-30-33.snfc21.pacbell.net 67.113.30.33
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP15.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:1029
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| Thanks a lot, Manfred.
|
| I did apply the suggestion to grant the rights. But for some reason, I am
| still getting the same errors...weird...
|
| "Manfred Rosenboom" <marochess@.gmx.de> wrote in message
| news:d3dpcu$d6c$1@.nntp.fujitsu-siemens.com...
| > Jay Shen wrote:
| >> Hi,
| >>
| >> I have applied XA support via the dll and script...but now I got the
| >> following error. Anyone can point me a direction to fix this?
| >> Thanks,
| >>
| >> j-
| >>
| >> 20:44:06 [tyrex.resource.n3-db] [main] [transaction server is
recovering]
| >> [] [] ERROR - Failed to create connection for default user
| >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
| >> JDBC][SQLServer]xa_open (0) returns -3
| >> at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
| > Hi Jay,
| >
| > Seems, that you haven't started the DTC (Distributed Transaction
| > Coordinator) service. This service is installed during the
| > MS SQL Server 2000 installation but with start type 'manual'.
| >
| > BTW: which user do you use to connetc to the database ? If you don't
| > use sa (which would be a good idea) have in mind, that XA recovery is
| > only allowed for a system administrator. To allow all users to perform
| > XA recovery, you have to add the EXEC permission to PUBLIC for the
stored
| > procedure xp_jdbc_recover (part of extended stored procedures) in the
| > master database.
| >
| > Best,
| > Manfred
|
|
|
Are you using the sqljdbc.dll and driver .jar files that come with JDBC
SP3? Did you test with the actual SA account and see the same problem?
You can capture a SQL Profiler trace (with all Errors and Warnings events
and all data columns) and see if you are truly getting a permissions issue
on the execution of the extended stored procedures.
Aside from that, ensure that MSDTC is started and that XA is enabled.
Check the registry key HKLM\Software\Microsoft\MSDTC\Security. The Value
name is XATransactions, and it is a REG_DWORD value. A value of 0 means XA
transactions are disabled. A non-zero value means they are enabled. If
you have to change this from 0 to 1, restart the SQL Server service and
MSDTC service.
If the above information does not resolve the issue, post the Java code and
table definition that you use to reproduce the problem.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Wednesday, March 21, 2012

Microsoft JDBC driver support connection pooling out of the box

Hi,
I'm pretty new to JDBC so bare with me.
If using Jdbc outside of an application/J2ee server with the Microsoft
Jdbc driver what is teh correct procedure/code for ensuring
connections are pooled.
I've seen quite a few posts about this but to be honest mostly of
little use.
A code snippet would be great.
Some of my colleagues have saud you don't get pooling without a
application/J2ee server , is this correct?
Regards
John Harkin wrote:

> Hi,
> I'm pretty new to JDBC so bare with me.
> If using Jdbc outside of an application/J2ee server with the Microsoft
> Jdbc driver what is teh correct procedure/code for ensuring
> connections are pooled.
> I've seen quite a few posts about this but to be honest mostly of
> little use.
> A code snippet would be great.
> Some of my colleagues have saud you don't get pooling without a
> application/J2ee server , is this correct?
> Regards
Some drivers will offer an internal poooing feature, which can be
useful for long-running applications that use lots of connections,
opening and closing them frequently. If the app is short-lived,
or just opens connections and keeps them until it exits, then
pooling won't help.
In any case, the free MS driver has no internal connection pooling.
Joe Weinstein at BEA

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...
>

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
Brian Luo wrote:

> 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
Hi. For the MS driver, you should avoid using setQueryTimeout() in middleware
because it will spawn a separate thread to enforce that for every statement.
This will play havoc with a JVM that is trying to multiplex a fixed number
of system threads to do enterprise-level loads and work.
It is certainly possible that MS's next driver version will fix this issue
but it doesn't hurt to ask MS to verify that...
For a WebLogic environment, is there any reason not to use WebLogic's
drivers? Particularly for our 8.1 versions, you will get a thoroughly superior
driver for MS SQLServer. I do understand that in our older WebLogic versions,
our jDriver is efficient, but frozen at the JDBC 1.0 level. If you cannot upgrade
to 8.1, the easiest fix is to use a third-party driver. I would recommend
DataDirect.
Joe Weinstein at BEA
|||Thanks. It seems a rather inefficient way to implement query timeout
mechanism at per statement level. It could be done either at per connection
level or even better, only one timeout thread per JVM.
Ironically, the 3.0 DataDirect driver had a similar problem . Not a surprise
because MS and DataDirect drivers are of the same origin. We worked with BEA
to get the problem fixed in the 3.3.0047 version.
The primary reason for us not using DataDirect (or other third party driver)
is business reason. Also, using drivers embedded in WebLogic/WebSphere impose
various restrictions for our product.
Your suggestion is a good one though. We should avoid to setQueryTimeout()
whenever possible. For example, if it is already 0 (default), we should avoid
setting it.
Thanks,
Brian
"Joe Weinstein" wrote:

> Brian Luo wrote:
>
> Hi. For the MS driver, you should avoid using setQueryTimeout() in middleware
> because it will spawn a separate thread to enforce that for every statement.
> This will play havoc with a JVM that is trying to multiplex a fixed number
> of system threads to do enterprise-level loads and work.
> It is certainly possible that MS's next driver version will fix this issue
> but it doesn't hurt to ask MS to verify that...
> For a WebLogic environment, is there any reason not to use WebLogic's
> drivers? Particularly for our 8.1 versions, you will get a thoroughly superior
> driver for MS SQLServer. I do understand that in our older WebLogic versions,
> our jDriver is efficient, but frozen at the JDBC 1.0 level. If you cannot upgrade
> to 8.1, the easiest fix is to use a third-party driver. I would recommend
> DataDirect.
> Joe Weinstein at BEA
>
>
|||Brian Luo wrote:

> Thanks. It seems a rather inefficient way to implement query timeout
> mechanism at per statement level. It could be done either at per connection
> level or even better, only one timeout thread per JVM.
> Ironically, the 3.0 DataDirect driver had a similar problem . Not a surprise
> because MS and DataDirect drivers are of the same origin. We worked with BEA
> to get the problem fixed in the 3.3.0047 version.
> The primary reason for us not using DataDirect (or other third party driver)
> is business reason. Also, using drivers embedded in WebLogic/WebSphere impose
> various restrictions for our product.
> Your suggestion is a good one though. We should avoid to setQueryTimeout()
> whenever possible. For example, if it is already 0 (default), we should avoid
> setting it.
Glad to help. By JDBC spec, it *is* zero by default.
Joe Weinstein at BEA
[vbcol=seagreen]
> Thanks,
> Brian
> "Joe Weinstein" wrote:
>
|||You are absolutely correct. And that's why I said we should avoid setting it
if the value is 0 (in our product).
Thanks,
Brian
"Joe Weinstein" wrote:

>
> Brian Luo wrote:
>
> Glad to help. By JDBC spec, it *is* zero by default.
> Joe Weinstein at BEA
>
>
|||Brian Luo wrote:

> You are absolutely correct. And that's why I said we should avoid setting it
> if the value is 0 (in our product).
Ok, but I can't imagine that the driver is so broken as to spawn a thread if
setQueryTimeout() is called with a zero value. I believe the problem only occurs
when there is a selected query timeout, and my only hope is that you can
limit any of your customers from causing it to be called with any non-zero
value until MS provides a free driver that has the same sort of fix as the
one you got through BEA.
Joe
[vbcol=seagreen]
> Thanks,
> Brian
> "Joe Weinstein" wrote:
>
|||I didn't really believe it but it is true, unfortunately. We have a parameter
in our product to set query timeout value. In our performance tests, we
always set it to 0. With WebLogic's jDriver, we never had any problem. But
with MS or older version of DataDirect, we always ran into OOM errors with
BaseQueryTimeoutEnforcer.
Thanks,
Brian
"Joe Weinstein" wrote:

>
> Brian Luo wrote:
>
> Ok, but I can't imagine that the driver is so broken as to spawn a thread if
> setQueryTimeout() is called with a zero value. I believe the problem only occurs
> when there is a selected query timeout, and my only hope is that you can
> limit any of your customers from causing it to be called with any non-zero
> value until MS provides a free driver that has the same sort of fix as the
> one you got through BEA.
> Joe
>
>
|||Brian Luo wrote:

> I didn't really believe it but it is true, unfortunately. We have a parameter
> in our product to set query timeout value. In our performance tests, we
> always set it to 0. With WebLogic's jDriver, we never had any problem. But
> with MS or older version of DataDirect, we always ran into OOM errors with
> BaseQueryTimeoutEnforcer.
> Thanks,
> Brian
Yow! Well, ok then. The bug is even worse, but we at least have a partial workaround...
thanks for the heads-up.
Joe
[vbcol=seagreen]
> "Joe Weinstein" wrote:
>
|||The Microsoft SQL Server 2000 JDBC driver doesn't spawn a new thread if
the query timeout is left at its default value (zero). However, if
setQueryTimeout is set -- even to explicitly set the value to zero --
then a thread will be spawned.
We will make the fix to have the driver never spawn a new thread in the
zero case -- default or explicit.
-shelby
Shelby Goerlitz
Microsoft SQL Server
"Joe Weinstein" <joeNOSPAM@.bea.com> wrote in message
news:joeNOSPAM@.bea.com:[vbcol=seagreen]
> Brian Luo wrote:
>
>
> Yow! Well, ok then. The bug is even worse, but we at least have a partial
> workaround...
> thanks for the heads-up.
> Joe
>
>
>
>
>
>
>
|||The timer threads are not necessary. TCP/IP timeouts could be used just
as well. Other JDBC drivers do it. At the least, what could be done is
have a single timeout thread throughout the app. That thread could then
interrupt any of the working threads.
Alin,
The jTDS Project.

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 a
s
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 LuoYou 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 i
s
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/commun...rver.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" <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/commun...rver.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" <BrianLuo@.discussions.microsoft.com> wrote in message
> news:134481F8-0146-443F-9D38-1C84E84BFE8D@.microsoft.com...
>sql

microsoft jdbc driver for SQL Server 7.0

Hi,
I need a Microsft jdbc driver to connect Microsoft SQL
Server 7.0 . I can find a driver Microsoft 2000 jdbc
driver through which I can access Microsoft SQL Server
2000 but not 7.0.
I do not like to go for a third party driver..
Thank you in advance,
Hanson.
Third party solution is what you will likely have to get. You can pay for one
or just get a free one that works really well:
http://jtds.sourceforge.net/
Good luck.
Yuval
"Hanson" wrote:

> Hi,
> I need a Microsft jdbc driver to connect Microsoft SQL
> Server 7.0 . I can find a driver Microsoft 2000 jdbc
> driver through which I can access Microsoft SQL Server
> 2000 but not 7.0.
> I do not like to go for a third party driver..
> Thank you in advance,
> Hanson.
>
|||"Hanson" <rarockia@.chn.cognizant.com> wrote in message
news:4d7001c4804e$40294f30$a601280a@.phx.gbl...
> Hi,
> I need a Microsft jdbc driver to connect Microsoft SQL
> Server 7.0 . I can find a driver Microsoft 2000 jdbc
> driver through which I can access Microsoft SQL Server
> 2000 but not 7.0.
> I do not like to go for a third party driver..
> Thank you in advance,
> Hanson
The Microsoft JDBC driver was designed specifically for SQL Server 2000. As
was mentioned before, you will have to consider an alternative solution if
you wish to connect to SQL Server 7.0.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security..