Howdy, >First off, we're running Apache 1.3.27 and Tomcat 4.1.17 with j2sdk1.4.1_01
4.1.17 really? Not 4.1.12/18/24/27 (the stable releases)? If possible, move to 4.1.27. >From everything I have read, it seemed natural set the -server flag, and >due >to some performance issues we were having, I increased the max/min memory >settings. I also get the impression that this creates issues with garbage >collection, which Im thinking could relate back to some of our DBCP >problems. That is unlikely, but possible. You'll need a bit more than an impression to debug GC-related issues, though ;) What specifically do you think is happening, and why do you think it's happening? One simple thing to do is remove -server and -Xms (keep -Xmx). That will make the JVM use its default and usually very stable GC algorithms. >Additionally, running the version of the JDK that I am, M$'s website shows >their JDBC driver compatible with up to 1.3, and I wonder if there is any >reason to think that some of the problems are related to running a higher >version than M$ says they support? That's also possible. It's the first thing M$ tech support would tell you: "you're running an unsupported driver/platform combination, update, retry, and call us back if you have a problem." Ticket closed as far as they're concerned. Can you get a later driver? Yoav Shapira 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
