I thought we had all that pick crap killed off in the early 80s, I suppose your supporting the Lynx browser as well! 1) the JDBC-ODBC bridge is not a production piece of code. You should never consider deploying with it in place. Therefore, I would suggest that you get a real database driver (and a real database for that matter, but you have legacy data I'm sure), and test with it. 2) The servlet is unlikely to be the problem. Write a standalone java app, that performs whatever query is passed into it as an argument, and test the query that way. Utilize any JDBC wrapper code your real app uses (connection pools, etc.). This will test your JDBC wrapper code on down, and verify that your query is working as you would expect. If this program is returning your query faster than the servlet, then you can consider the servlet's performance to be an issue, but not until this program is executing faster than the servlet. Also, realize that caching will effect your performance, so if you execute this program after executing the servlet, your tests will be invalidated. 3) Logging/Tracing/Debugging messages are key. Your application is going to break, but with good logs, you will be able to determine what caused the problem and fix it. At a minimum we trace every method that is entered. This gives you an idea what method caused the problem. If you have this level of logging/tracing messages, and you timestamp all of them (as I do, all configurable of course), then you can identify what method is causing the performance bottleneck. In all cases, my performance bottlenecks so far have been related to the database, not the servlet engine. Of course, I'm using a different servlet engine than you are using. 4) If you really think it's the servlet engine, I would suggest trying one that has worked very well in the past for others, and is free. Not as a new deployment strategy, but as a test bed to verify that one servlet engine is able to run your servlet correctly and the other has the problem. The one I'd suggest you using is Apache with either JServ or JRun (not the pro edition, were just testing here). I personally use Apache w/ JRun. It's configuration was a bit easier when we were first getting started, and we have had no reason to change yet. 5) I find it hilarious that you cannot get JRun Pro to install correctly. JRun installed out of the box with Apache no problems! As for the docs, the ones that come with JRun are sufficient for me, what are you looking for? I can't speak for the technical support, as I have had no need for it yet (I assume JRun is not supported, but it hasn't needed to be yet, so I'm safe). If it's so annoying, change platforms to one that works (I gave you two above). I'd be a hell of a lot more annoyed at working with pick in the first place than at working with a java and servlets. Brian -----Original Message----- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 29, 1999 6:44 PM To: [EMAIL PROTECTED] Subject: Connecting to a PICK database using JDBC-ODBC bridge from a Servlet I am connecting to a PICK database using the JDBC-ODBC bridge from my servlet. I am having major speed issues. This is my first servlet project and the queries take up to 10 minutes to process. Sometimes, my browser times out before they are done. Has anyone else done something similar and can help out? Also, we are using JRun Pro w/ IIS 4. I still can't get it installed properly. The docs are terrible!! Also, the company offers tech support over the phone w/ 72 hour turnaround. 72 hours??? This is very annoying. ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
