tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atta, Jayadevan" <JA...@activehealth.net>
Subject Re: Update Tomcat 5 -> 6 .. JDBC driver problem
Date Fri, 01 May 2009 16:09:37 GMT
The post below from Daniel Steel helped me migrate from Tomcat 4 to Tomcat 6



Thanks,



Jayadevan Atta

Java Developer

-------------------------------------------------------------------------------------



if we configure the url / db access as JNDI resource in the context  files, then the \

implementation has changed betwen tomcat 5 and tomcat6.  not sure about tomcat 5.5..  \

  in tomcat6, it is





<Context ...>

  ...

  <Resource name="jdbc/EmployeeDB" auth="Container"

            type="javax.sql.DataSource" username="dbusername" password="dbpassword"

            driverClassName="org.hsql.jdbcDriver" url="jdbc:HypersonicSQL:database"

            maxActive="8" maxIdle="4"/>

  ...

</Context>



in tomcat 5,







<Context ...>

  ...

  <Resource name="jdbc/EmployeeDB" auth="Container"

            type="javax.sql.DataSource"/>

  <ResourceParams name="jdbc/EmployeeDB">

    <parameter>

      <name>username</name>

      <value>dbusername</value>

    </parameter>

    <parameter>

      <name>password</name>

      <value>dbpassword</value>

    </parameter>

    <parameter>

      <name>driverClassName</name>

      <value>org.hsql.jdbcDriver</value>

    </parameter>

    <parameter>

      <name>url</name>

      <value>jdbc:HypersonicSQL:database</value>

    </parameter>

    <parameter>

      <name>maxActive</name>

      <value>8</value>

    </parameter>

    <parameter>

      <name>maxIdle</name>

      <value>4</value>

    </parameter>

  </ResourceParams>

  ...

</Context>



thanks

dan







David Smith <dns4@cornell.edu> wrote:  That's good info, but only barely related to
\

the question at hand and  they said they had it working in tomcat 5.5.23 -- just \

failing in tomcat  6.  Given it works in one version of tomcat and not another, I \

highly  doubt the mysql jdbc url is at fault.  The OP needs to post portions of

their configuration (context.xml, web.xml, server.xml) before any

further diagnosis can be done.



--David



Martin Gainty wrote:

> MySQL Connector/J doc says

>

> "The JDBC URL format for MySQL Connector/J is as follows,

> with items in square brackets ([, ]) being optional:

> jdbc:mysql://[host][,failoverhost...][:port]/[database] »

> [?propertyName1][=propertyValue1][&propertyName2][=propertyValue2]...

>

> If the hostname is not specified, it defaults to 127.0.0.1.

> If the port is not specified, it defaults to 3306, the default port

> number for MySQL servers.

> jdbc:mysql://[host:port],[host:port].../[database] »

> [?propertyName1][=propertyValue1][&propertyName2][=propertyValue2]...

>

> If the database is not specified, the connection will be made with

> no default database.

>

> M--

> This email message and any files transmitted with it contain confidential

> information intended only for the person(s) to whom this email message is

> addressed.  If you have received this email message in error, please

> notify

> the sender immediately by telephone or email and destroy the original

> message without making a copy.  Thank you.

>

> ----- Original Message ----- From: "gregory hans"

> To: "Tomcat Users List"

> Sent: Friday, June 29, 2007 9:37 AM

> Subject: Re: Update Tomcat 5 -> 6 .. JDBC driver problem

>

>

> > i using tomcat6 right now and i put my jdbc in my lib directory and

> > that's okay. can you post your error to me so i can figure what's

> > going on.

> >

> > David Smith  wrote:  In tomcat 6, the new

> > common/lib is simply lib as I understand it. Could

> > you post your config? The error you originally posted typically

> > indicates a misconfiguration as opposed to not being able to find the

> > driver class.

> >

> > --David

> >

> > Rene Guenther wrote:

> > > Alas, still the same error.

> > >

> > > So you think, that I get this error because tomcat isnt able to find

> > > the .jar file with the MySQL driver? Maybe something changed between

> > > Tomcat 5 and 6 related to ?

> > >

> > > Regards

> > > René

> > >

> > > On Thu, 28 Jun 2007 18:37:21 +0800

> > > "Allen å­T" wrote:

> > > > Put your jars into: *apache-tomcat-6.x.x/lib* will be just fine.

> > > >

> > > >

> > > > 2007/6/28, Rene Guenther :

> > > > >

> > > > > Thanks for your reply. Unfortunately I am still getting

> > > > > the same error with tomcat 6.0.13

> > > > >

> > > > > Regards

> > > > > René

> > > > >

> > > > > On Thu, 28 Jun 2007 02:34:10 -0700 (PDT)

> > > > > gregory hans wrote:

> > > > > > try to put your jdbc in your web application

> > > > > > (WEB-INF/LIB/). stop the service first, put the jdbc then

> > > > > > start again...

> > > > > >

> > > > > > Rene Guenther wrote:

> > > > > > Hello,

> > > > > >

> > > > > > I am getting the following exception with tomcat 6.0.13:

> > > > > >

> > > > > > Cannot create JDBC driver of class '' for connect URL

> > > > > > 'null'

> > > > > >

> > > > > > This exception I dont get with tomcat 5.5.23

> > > > > >

> > > > > > I put the mysql jdbc driver (version 5.x) into

> > > > > > apache-tomcat-x.x.x/common/lib

> > > > > >

> > > > > > Anyone knows what the problem could be?

> > > > > >

> > > > > > (OS: Linux Debian, Java Version 1.5)

> > > > > >

> > > > > > Regards

> > > > > > René

> > > > > >

> > > > > >

> > > > > >

> > > > > ---------------------------------------------------------------------

> > > > > > To start a new topic, e-mail: users@tomcat.apache.org

> > > > > > To unsubscribe, e-mail:

> > > > > > users-unsubscribe@tomcat.apache.org

> > > > > > For additional commands, e-mail:

> > > > > > users-help@tomcat.apache.org

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > > ---------------------------------

> > > > > > Don't pick lemons.

> > > > > > See all the new 2007 cars at Yahoo! Autos.

> > > > >

> > > > >

> > > > > ---------------------------------------------------------------------

> > > > > To start a new topic, e-mail: users@tomcat.apache.org

> > > > > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

> > > > > For additional commands, e-mail: users-help@tomcat.apache.org

> > > > >

> > > > >

> > > >

> > > >

> > > > --

> > > > Sincerely yours å­T

> > >

> > >

> > > ---------------------------------------------------------------------

> > > To start a new topic, e-mail: users@tomcat.apache.org

> > > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

> > > For additional commands, e-mail: users-help@tomcat.apache.org

> > >

> >

> >

> > ---------------------------------------------------------------------

> > To start a new topic, e-mail: users@tomcat.apache.org

> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

> > For additional commands, e-mail: users-help@tomcat.apache.org

> >

> >

> >

> >

> > ---------------------------------

> > TV dinner still cooling?

> > Check out "Tonight's Picks" on Yahoo! TV.

>

>

> ---------------------------------------------------------------------

> To start a new topic, e-mail: users@tomcat.apache.org

> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

> For additional commands, e-mail: users-help@tomcat.apache.org

>





---------------------------------------------------------------------

To start a new topic, e-mail: users@tomcat.apache.org

To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org

For additional commands, e-mail: users-help@tomcat.apache.org







________________________________
IMPORTANT WARNING: Information contained in this email is intended for the use of the individual
to whom it is addressed, and may contain information that is privileged, confidential, and
exempt from disclosure under applicable law. If you are not the intended recipient, or the
employee or agent responsible for delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution, or copying of this communication is
STRICTLY FORBIDDEN. If you have received this communication in error, please notify us immediately
by return email and delete this document. Thank you.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message