[Wrapper-user] VB: JDBC - MSSQL - SqlDumpExceptionHandler

[Mattias T. <Mat...@mi...>]

I have recieved support on this issue from jTDS-forums. For anyone that =
has interest read below,

"Mattias,=20

It might have to do with stored procedures. By default jTDS uses =
temporary stored procedures for PreparedStatements, i.e. it creates one =
for each PreparedStatement then uses it for each execution.=20

If you have PreparedStatements that update TEXT fields in a table that =
has an INSTEAD OF trigger defined on them, this just might be it. If =
that's the case, the workaround is simple: just specify another value =
for the "prepareSQL" parameter (I wuold recommend 2). See the jTDS FAQ ( =
<http://jtds.sourceforge.net/faq.html> ) for more information on =
"prepareSQL".=20

Just in case, upgrading to the last version of jTDS might be a good =
idea. We're not only doing new releases to gain visibility, there are a =
big number of bug fixes and new features in each new version.=20

Alin."


>  -----Ursprungligt meddelande-----
> Fr=E5n: 	Mattias Ternert =20
> Skickat:	den 9 februari 2005 12:47
> Till:	'wra...@li...'
> =C4mne:	 JDBC - MSSQL - SqlDumpExceptionHandler
>=20
>=20
> Hi
>=20
> I have an application that run 4 services implemented with Wrapper =
(Version 3.1.0). Three of the services are executed idependently of each =
other but they all depend on one service which executes Logging&Alarm =
functionality. This service depends on JDBC to insert records in a =
MS-SQLserver. We use the jTDS-0.8.rc1 JDBC driver.  Some of our =
customers have experienced situations where this service has failed with =
this message in the service log,=20
>=20
> Error in Alarm Manager, code 5010: SQL error:0 - =
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005 =
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
>=20
> I have tried to do an analysis of this problem and are not quiet sure =
what is causing this; are own code, MS-SQL server itself, the JDBC =
driver or the service-Wrapper. I found this information from Microsoft =
regarding the exception:
>=20
> http://support.microsoft.com/kb/839523
> http://support.microsoft.com/kb/295114/EN-US/
>=20
> However we do not use stored procuders and our customers have not =
upgraded from MS-SQL7 to MS-SQL2000 so I=B4m not sure if this applies to =
us. I have also tried to search info about this on jTDS project homepage =
but have not found anything that directly applies to this. So as a last =
act I=B4m asking if there are anyone here that have experienced this and =
if so how they solved it. My actions will be to update jTDS, service =
wrapper and MS-SQL to latest versions to see if this will help.
>=20
> Sincerely Mattias
>=20
>=20