jakarta-tomcat/6876: DRWatson - access violation ; java.exe or javaw.exe

[Ram <ra...@yahoo.com>]

>Number:         6876
>Category:       jakarta-tomcat
>Synopsis:       DRWatson - access violation ; java.exe or javaw.exe
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jakarta
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Nov 21 11:10:02 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     ramcohen@yahoo.com
>Release:        1.3
>Organization:
apache
>Environment:
tomcat3.1 ; nt4.0 sp 4 ; SQLServer7.0 desktop edt. 
jrun ;nt4.0 sp 4 ; SQLServer7.0 desktop edt. 
>Description:
I am getting a DrWatson, access violation when I run a simple servlet to connect to a DB of SQLServer7.0 desktop etd. I am using sun's jdbc-odbc bridge,
the method that is causing DRWatson is executeQuery(). I tried using JRun, DRWAtson in javaw.exe immediate. Using tomcat DRWatson after some time on a single thread, immediate on multiple thread. Possibly a prob with my DB, or the bridge. 
Note: executeQuery() is executed! yet, afterwards DRWatson appears and shuts down JRUN or TomCat.
>How-To-Repeat:
install SQLServer 7.0 Desktop, run a servlet that calls executeQuery(), using JRUN or Tomcat, running on NT4.0. 
>Fix:
tried several, none succeded
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]