Hmmm. I'm thinking I'm beginning to get a whiff of the issue.

Before, we would run multiple webapps and each had their own context file
that matched the webapps. Like for the one below, we had one called mo.xml.
We'd put all these in the CATALINA_HOME/conf/Catalina/localhost and it all
worked great.

With 6, I've dropped mo.xml into the conf directory directly since that
seemed to be what the docs recommended. Now, I'm thinking, I need to
integrate all this into context.xml.

Is this what you're suggesting?

BTW, I made sure the JDBC jar files are all in CATALINA_HOME/lib.

Thanks.

-----Original Message-----
From: Mark Shifman [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 16, 2007 1:31 PM
To: Tomcat Users List
Subject: Re: JDBC connection issue

I just upgraded from 5.5 to 6.0 without any problems.  My webapp was 
deployed as a war file
with the config.xml in the META-INF (the exact config for 5.5). The 
deployment does the
correct thing with the config.xml.

Make sure your jdbc library is in the CATALINA_HOME/lib dir.

I also was playing around with using realms for the manager and found I 
had to
put the manager's config.xml in the META-INF dir for things to work. I tried
moving the config.xml to conf/Catalina/localhost and ... ... the manager 
was undeployed.

mas





Hehl, Thomas wrote:
> I am testing our webapp under tomcat 6 after being under tomcat 5.5.
>
>  
>
> I have moved the following file from 5.5. into 6. I have placed it in the
> conf directory:
>
>  
>
> <Context path="/mo" docBase="mo" debug="0" reloadable="true"
> crossContext="true">
>
>  
>
> <Resource name="jdbc/mo" auth="Container" type="javax.sql.DataSource"
> maxActive="20" 
>
>  
>
> maxIdle="-1" maxWait="1000" 
>
>  
>
> username="informix"  password="xxxxxxx" 
>
>  
>
> driverClassName="com.informix.jdbc.IfxDriver"     
>
>
url="jdbc:informix-sqli://vaninfmx1:7101/jur_feds:INFORMIXSERVER=gs_jms9"/>
>
>  
>
> </Context>
>
>  
>
> This works under 5.5, but under 6.0, I get "Cannot create JDBC driver of
> class '' for connect URL 'null'
>
>  
>
> And
>
>  
>
> Could not obtain connection metadata.
>
>  
>
> I've googled, and most seem to feel that these errors are caused by an
issue
> in the context definition.
>
>  
>
> I've looked through the docs and find nothing that got changed between 5.5
> and 6.0 so I'm puzzled and trying here. Anyone?
>
>  
>
> Thanks.
>
>  
>
> Thom Hehl
> Sr. eJuror Architect
>
> * Office (859) 277-8800 x 144
>
> * [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>  
> ACS, Inc.
>
> Government Solutions
>
> 1733 Harrodsburg Road
> Lexington, KY 40504-3617
>
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient, please contact the
sender
> by reply e-mail and destroy all copies of the original message and notify
> sender via e-mail at [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>  or by telephone at 859-277-8800 ext.
144.
> Thank you.
>
>  
>
>
>   

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to