Particularly problematic Oracle connection problem (Oracle 10g, Tomcat 6, Blojsom 3.2)
I'm attempting to get Blojsom 3.2 talking to my Oracle database (this is
completely setup fine, the problem appears to be a classloader issue of
some sort) in Tomcat 6 (6.0.16 to be precise).
I'm using a split CATALINA_BASE and CATALINA_HOME installation
(CATALINA_HOME isn't writable by the user that I'm running as), and have
put ojdbc14.jar and orai18n.jar in my $CATALINA_BASE/lib directory.
Furthermore, following suggestions about RUNNING.txt not being correct,
I've put the following line in my
$CATALINA_BASE/conf/catalina.properties file:
common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina
.base}/lib,${catalina.base}/lib/*.jar
This is replacing the existing definition of common.loader.
Here's what I've tried:
- Putting the .jar files nowhere (not in CATALINA_HOME, CATALINA_BASE,
or my webapp itself)
- Results in a ClassNotFoundException loading
oracle.jdbc.OracleDriver
- Putting the .jar files ANYwhere (in order of attempts, webapp's
WEB-INF/lib, CATALINA_BASE/lib, CATALINA_HOME/lib)
- Results in the following statement occurring in the logs:
Cannot create JDBC driver of class 'oracle.jdbc.OracleDriver' for
connect URL 'jdbc:oracle:thin@//fodevdbsx1.london:1521/fodev3.london'
This indicates to me that the Oracle driver is being loaded, but it's
being stopped from actually creating the instance for some reason.
The complication here is that Blojsom DOES NOT use, by default, JNDI
resources. Rather, it sets up its own DBCP DataSource in its
Spring+Hibernate configuration, which is what's failing here. This is
NOT a Resource problem. Just to make sure, when I removed the DBCP
implementation in blojsom, it failed, because it couldn't find the
catalina copies.
I can try to figure out a workaround for this, but I've spent about 6
hours on it thus far, and no matter what combination of property
changes, I can't figure out what precisely is stopping it from loading.
Has anybody experienced anything like this in the past either with
Blojsom or some other application which isn't using JNDI resources for
database connections using Tomcat 6?
I'm a relative newbie to Tomcat 6, but I've used Tomcat 4-5.5
extensively in the past.
Thanks a lot,
Kirk Wylie
--
This message may contain confidential, proprietary, or legally privileged
information. No confidentiality or privilege is waived by any transmission to
an unintended recipient. If you are not an intended recipient, please notify
the sender and delete this message immediately. Any views expressed in this
message are those of the sender, not those of any entity within the KBC
Financial Products group of companies (together referred to as KBC FP).
This message does not create any obligation, contractual or otherwise, on the
part of KBC FP. It is not an offer (or solicitation of an offer) of, or a
recommendation to buy or sell, any financial product. Any prices or other
values included in this message are indicative only, and do not necessarily
represent current market prices, prices at which KBC FP would enter into a
transaction, or prices at which similar transactions may be carried on KBC FP's
own books. The information contained in this message is provided as is,
without representations or warranties, express or implied, of any kind. Past
performance is not indicative of future returns.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Particularly problematic Oracle connection problem (Oracle 10g, Tomcat 6, Blojsom 3.2)
Summary: I am an idiot and posted to the mailing list far too early. Was a problem with my JDBC connection string (a typo basically). I think I got hung up too much on the classloading differences between Tomcat 5.x and Tomcat 6 and didn't look carefully enough at my own settings. Apologies for wasting people's time, Kirk Wylie -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: 15 February 2008 12:49 To: Tomcat Users List Subject: Re: Particularly problematic Oracle connection problem (Oracle 10g, Tomcat 6, Blojsom 3.2) Wylie, Kirk wrote: - Putting the .jar files ANYwhere (in order of attempts, webapp's WEB-INF/lib, CATALINA_BASE/lib, CATALINA_HOME/lib) - Results in the following statement occurring in the logs: Cannot create JDBC driver of class 'oracle.jdbc.OracleDriver' for connect URL 'jdbc:oracle:thin@//fodevdbsx1.london:1521/fodev3.london' Do you have a stack trace for this. Can you turn up the logging level and get one? This indicates to me that the Oracle driver is being loaded, but it's being stopped from actually creating the instance for some reason. Agreed. The complication here is that Blojsom DOES NOT use, by default, JNDI resources. Rather, it sets up its own DBCP DataSource in its Spring+Hibernate configuration, which is what's failing here. This is NOT a Resource problem. Just to make sure, when I removed the DBCP implementation in blojsom, it failed, because it couldn't find the catalina copies. If you are not using JNDI then you should be able to put the Oracle JARs in WEB-INF/lib. I'd also restore catalina.properties to the original to limit the changes. Has anybody experienced anything like this in the past either with Blojsom or some other application which isn't using JNDI resources for database connections using Tomcat 6? I have used DBCP directly in web-apps without a problem with 4, 5 and 6. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of any entity within the KBC Financial Products group of companies (together referred to as KBC FP). This message does not create any obligation, contractual or otherwise, on the part of KBC FP. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, prices at which KBC FP would enter into a transaction, or prices at which similar transactions may be carried on KBC FP's own books. The information contained in this message is provided as is, without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
