Hi,
Maybe another approach will help. Can you write a little command-line
test program to do the import?  One that will read, parse the file, set
up the ImportManager, and do your DB work, all outside of tomcat.
Perhaps that will make the issue easier to pinpoint and then debug.
It's certainly easier to profile (using OptimizeIt or whatever profiler
you prefer) outside the servlet container.

On the other hand, if the program runs quickly and without memory leaks
outside of tomcat, we probably have a more serious tomcat issue at hand.

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Durham David Cntr 805CSS/SCBE [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, August 21, 2002 11:03 AM
>To: Tomcat Users List
>Subject: RE: Tomcat Crash
>
>
>
>> -----Original Message-----
>> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
>>
>> Did you try to get a new connection each time and not go through the
>> pool?  That would degrade performance significantly (although
>> you could
>> just get one connection at the beginning and use it until
>> you're done),
>> but maybe memory behavior will be better?
>
>       Just tested getting a new connection, the system will still
crash.
>I've noticed the smaller the file import, the longer it takes for
Tomcat to
>crash after I've done an import.  i.e.  a file with 12 lines in it will
>import successfully, then I can get maybe 20 more connections before
Tomcat
>crashes.  Where as a file with 50 lines in it will cause Tomcat to
crash
>immediately after the import, anymore lines than that and the import
will
>fail before the import completes.  The number of lines that will
succeed is
>variable.  Sometimes 50 lines will get imported, sometimes Tomcat will
>crash before I can import 50 lines.   BTW, Tomcat is not reporting any
>errors in the logs.
>
>Dave
>
>--
>To unsubscribe, e-mail:   <mailto:tomcat-user-
>[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:tomcat-user-
>[EMAIL PROTECTED]>

This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to