On 5/23/2012 5:39 PM, Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David,
On 5/23/12 5:17 PM, David kerber wrote:
On 5/23/2012 4:57 PM, Mark Thomas wrote:
On 23/05/2012 21:53, David kerber wrote:
Any suggestions as to where to start looking for this error?
Ditch the ODBC-JDBC bridge driver and get a JDBC driver for the
database you are using. The ODBC-JDBC bridge is not recommended
for production use.
In general I agree, but that's easier said than done, and it has
been working quite reliably for several years until yesterday.
Is it tough to move to a Type 4 driver? I didn't think there was a
database these days that still required the ODBC bridge...
I don't think it's particularly difficult, but it will require some code
changes, and the DB manufacturer says it doesn't have as good of
performance as the ODBC driver. Not really an issue in this particular
app, because the db is only used for authentication and a few config
items, and not for ongoing processing.
If EXCEPTION_ACCESS_VIOLATION is what I think it is (SIGSEGV), then I
From what I've seen, it is.
would highly recommend that you run memtest86+ on this machine as soon
as you can. Barring JVM bugs (and a buggy JDBC->ODBC bridge could
certainly be the culprit), my experience has been that unexplained seg
faults usually mean that the hardware is starting to die (I've seen
independent CPU, memory, and motherboard failures cause this kind of
thing).
I just started a run of memtestPro for windows (can't take this server
out of production on no notice).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
