Return-Path: 
 <tomcat-user-return-48854-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 39455 invoked by uid 500); 28 Sep 2001 01:47:52 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
list-help: <mailto:tomcat-user-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
list-post: <mailto:tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 39442 invoked from network); 28 Sep 2001 01:47:52 -0000
Message-ID: <003701c147bf$8b6e1ea0$25cc8780@uchicago.edu>
From: "Matt Fisher" <mjf@press.uchicago.edu>
To: <tomcat-user@jakarta.apache.org>
Subject: Re: Tomcat 3.2.2 crashes with JDBC
Date: Thu, 27 Sep 2001 20:47:34 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I take that back. Maybe I am seeing bugs in J-Netdirect's JDBC drivers.

The OutOfMemory errors occur most often in connection with classes in the
JSQLConnect package, e.g.:

  Root cause:
  java.lang.OutOfMemoryError
     at com.jnetdirect.jsql.t.a(Unknown Source)
     etc.

But sometimes they occur in connection with other things, e.g.:

  Root cause:
  java.lang.OutOfMemoryError
     at java.lang.StringBuffer.append(Unknown Source)
     at sqlUtilities.makeXMLFromCurrentRow(sqlUtilities.java, Compiled Code)

The latter method, makeXMLFromCurrentRow(), is one of our custom methods.

Incidentally, it did not help to stop Tomcat, increase the memory allocation by
setting the TOMCAT_OPTS environment variable, and restart Tomcat. We gave it 512
megs, of which only a small fraction seemed to be used. The performance meter
showed only a slight increase in memory use during stress testing.

Seems like some compartment within that 512 megs is being set to a ridiculously
low default. I wonder what that might be....

I'll contact J-Netdirect, but if anyone can think of another angle to try, I'd
appreciate your advice. The setup again is Tomcat 3.2.1, Apache 1.3.20, Windows
2000 Server, SQL Server 2000 database, JSQLConnect and JSQLOptionalAPI.

 - Matt
----- Original Message -----
From: "Matt Fisher" <mjf@press.uchicago.edu>
To: <tomcat-user@jakarta.apache.org>
Sent: Thursday, September 27, 2001 12:51 PM
Subject: Re: Tomcat 3.2.2 crashes with JDBC


> Pransanth wrote:
>
> <<So can you help me with where I can find the right driver . Also, could you
> suggest the best driver i could use for MS SQL 2000. I will shortly be
migrating
> to SQL 2000 from MS access.>>
>
> If you can afford a commercial JDBC driver, see: http://www.j-netdirect.com
>
> There are no doubt other vendors of quality drivers. However, J-Netdirect's
> JSQLConnect and JDBCOptionalAPI are the only ones I have used. These jar files
> work well with Tomcat 3.2 and SQL Server 2000. I have not encountered any
bugs.
>
>  - Matt Fisher
>
>