|
From: Mattias T. <Mat...@mi...> - 2005-02-11 12:19:25
|
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,=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: wra...@li... [mailto:wra...@li...]F=F6r Leif Mortenson Skickat: den 11 februari 2005 12:26 Till: wra...@li... =C4mne: Re: [Wrapper-user] JDBC - MSSQL - SqlDumpExceptionHandler Mattias, Looking at this, I don't see anything that would hint at it being=20 caused by the Wrapper. It sounds like a known Microsoft bug. What happens when this error=20 occurs? Does the JVM crash? Or does it just show up in the logs and continue to=20 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=20 > (Version 3.1.0). Three of the services are executed idependently of=20 > each other but they all depend on one service which executes=20 > Logging&Alarm functionality. This service depends on JDBC to insert=20 > records in a MS-SQLserver. We use the jTDS-0.8.rc1 JDBC driver. Some=20 > of our customers have experienced situations where this service has=20 > failed with this message in the service log, > > Error in Alarm Manager, code 5010: SQL error:0 -=20 > 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=20 > what is causing this; are own code, MS-SQL server itself, the JDBC=20 > 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=20 > upgraded from MS-SQL7 to MS-SQL2000 so I=B4m not sure if this applies = to=20 > us. I have also tried to search info about this on jTDS project=20 > 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=20 > experienced this and if so how they solved it. My actions will be to=20 > update jTDS, service wrapper and MS-SQL to latest versions to see if=20 > this will help. > > Sincerely Mattias > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |