A couple of methods:
1. Most people I've seen end up stabbing in the dark with tons of
logging statements all over.
2. Some people change the JVM invocation parameters such that they can
use JPDA debuggers like BugSeeker from Karmira (http://www.karmira.com).
I start up Tomcat and then
Windows 2000 Server w/ SP2
Tomcat 4.0.1
Sun JDK 1.3.1
NetDirect JSQLConnect JDBC drivers
SQL Server 2000 w/ SP1
Runs pretty stable now ( 5 days so far with no crash), but I had to
switch to Sun's client hotspot JVM as the server hotspot JVM would crash
within 24 hours consistently. I may try
I certainly agree on this opinion! I got bloody knuckles from the MS
driver (really just OEM'd from Merant before they spun off). bigint
didn't work at all right out of the gate. How many other bugs are
lurking if such an obvious one made it through the extensive QA
process?
The JSQLConnect
Which JVM are you using?
On Windows 2K w/ SP2 I found that the Sun JDK 1.3.1 server hotspot JVM
crashed and burned running Tomcat 4.0.1 this way within 24 hours easily.
A few others emailed me about it also.
Switching to the Sun JDK 1.3.1 client hotspot JVM magically fixed this.
Now my server
