1. Only the first of your problems can have it's cause in the JDBC driver. The JDBC-ODBC Bridge add one extra layer to the db communication. We made good expierences with the WebLogic JDBC Driver from BEA. (One major drawback: it's quite expensive) 2. The other problems look like issues of the servlet engine or configuration errors. > -----Ursprüngliche Nachricht----- > Von: Tomcat [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 21. März 2001 07:57 > An: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Betreff: Re: JDBC Driver > > In that case....if free implementations are not good > enough....can you all > please suggest us a good commercial JDBC driver to connect to > MS SQL 7, which would be worth its money. > <snip/> > 1. High CPU utilization. (Jrun service needs to be restarted) > 2. If sevlets are changed , the changes dont get effected in Jrun. > 3. JSP sessions do not work. <snip/>
