Re: SV: [Wrapper-user] JDBC - MSSQL - SqlDumpExceptionHandler

[Leif M. <le...@ta...>]

Mattias,
    I saw that the first time you posted it.  But I don't see anything 
other than possible
problems with the jtds code or your java application.  You also didn't 
answer any
of my questions.  They were asked so I try to narrow down whether or not 
this
is an issue that has anything to do with the Wrapper.

Leif

Mattias Ternert wrote:

>Leif
>
>I have recieved support from jTDS forum. I tried to post it to the wrapper user list. Se answer below FYI,
>
> "have recieved support on this issue from jTDS-forums. For anyone that has interest read below,
>
>"Mattias, 
>
>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. 
>
>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". 
>
>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. 
>
>Alin.""
>
>-----Ursprungligt meddelande-----
>Från: wra...@li...
>[mailto:wra...@li...]För Leif Mortenson
>Skickat: den 11 februari 2005 12:26
>Till: wra...@li...
>Ämne: Re: [Wrapper-user] JDBC - MSSQL - SqlDumpExceptionHandler
>
>
>Mattias,
>    Looking at this, I don't see anything that would hint at it being 
>caused by the Wrapper.
>It sounds like a known Microsoft bug.  What happens when this error 
>occurs?  Does the
>JVM crash?  Or does it just show up in the logs and continue to 
>function.   If the JVM is
>crashing?  Is the Wrapper correctly restarting your JVM?
>
>Leif
>
>Mattias Ternert wrote:
>
>  
>
>>Hi
>>
>>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,
>>
>>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.
>>
>>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:
>>
>>http://support.microsoft.com/kb/839523
>>http://support.microsoft.com/kb/295114/EN-US/
>>
>>However we do not use stored procuders and our customers have not 
>>upgraded from MS-SQL7 to MS-SQL2000 so I´m 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´m 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.
>>
>>Sincerely Mattias
>>
>>
>>    
>>