Katalma
asked on
Tomcat 5.5.x or 5.0.28 and JNDI - MySql JDBC DataSource
I am trying to use database connection pooling with Tomcat's
JNDI InitialContext implementation - with no luck.
I have a problem which is similar to
https://www.experts-exchange.com/questions/21526163/Tomcat-5-5-9-and-MySQL-Cannot-create-JDBC-driver-of-class-''-for-connect-URL-'null'.html
but its accepted answer didn't solve my problem.
The only difference is mysql is not on the localhost but it runs on a remote computer.
Tomcat runs on my WinXP (SP2), the MySql runs on a debian linux. I can connect to mysql from java without connection pooling. Java version is jdk1.5.0_02 (could it be the problem?).
I saw the http://tomcat.apache.org/tomcat-5.0-doc/jndi-resources-howto.html site, the http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-examples-howto.html site, and similar pages for Tomcat 5.5, and I tried the solution above too.
I always get this Exception:
# Caused by: javax.naming.NameNotFoundE
# org.apache.naming.NamingCo
# org.apache.naming.NamingCo
# org.apache.naming.Selector
# javax.naming.InitialContex
# hu.tigra.cvdb.database.Dat
It's strange because my Java code is:
...
Context initCtx = new InitialContext();
DataSource ds = (DataSource) initCtx.lookup("jdbc/CVDB"
...
But if I use http://localhost:8081/manager/resources on my computer, I can see that the global resource is created:
OK - Listed global resources of all types
jdbc/CVDB:org.apache.commo
UserDatabase:org.apache.ca
simpleValue:java.lang.Inte
This is my server.xml for tomcat 5.0.28, the per-application-web.xml (context.xml) and the web.xml for my application below. Maybe I forgot something? Is anything necessary (another property file or xml or anything)?
server.xml:
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<!-- Comment these entries out to disable JMX MBeans support -->
<!-- You may also configure custom components (e.g. Valves/Realms) by
including your own mbean-descriptor file(s), and setting the
"descriptors" attribute to point to a ';' seperated list of paths
(in the ClassLoader sense) of files to add to the default list.
e.g. descriptors="/com/myfirm/m
-->
<Listener className="org.apache.cata
debug="0"/>
<Listener className="org.apache.cata
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.x
</parameter>
</ResourceParams>
<Resource name="jdbc/CVDB" auth="Container"
type="javax.sql.DataSource
description="cvdb">
</Resource>
<ResourceParams name="jdbc/CVDB">
<parameter>
<name>factory</name>
<value>org.apache.commons.
</parameter>
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>
<parameter>
<name>username</name>
<value>katalma</value>
</parameter>
<parameter>
<name>password</name>
<value>valami</value>
</parameter>
<parameter>
<name>driverClassName</nam
<value>com.mysql.jdbc.Driv
</parameter>
<parameter>
<name>url</name>
<value>jdbc:mysql://192.16
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Catalina">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 5 documentation bundle for more detailed
instructions):
* If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on the port specified
during installation -->
<Connector
port="8081" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true
<!-- Note : To disable connection timeouts, set connectionTimeout value
to 0 -->
<!-- Note : To use gzip compression you could set the following properties :
compression="on"
compressionMinSize="2048"
noCompressionUserAgents="g
compressableMimeType="text
-->
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<!--
<Connector port="8443"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true
acceptCount="100" debug="0" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
-->
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector port="8009"
enableLookups="false" redirectPort="8443" debug="0"
protocol="AJP/1.3" />
<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector port="8082"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false"
acceptCount="100" debug="0" connectionTimeout="20000"
proxyPort="80" disableUploadTimeout="true
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- You should set jvmRoute to support load-balancing via JK/JK2 ie :
<Engine name="Standalone" defaultHost="localhost" debug="0" jvmRoute="jvm1">
-->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Catalina" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.4
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/ex
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.cata
-->
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.cata
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.cata
debug="0" resourceName="UserDatabase
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.cata
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.cata
driverName="org.gjt.mm.mys
connectionURL="jdbc:mysql:
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles"
-->
<!--
<Realm className="org.apache.cata
driverName="oracle.jdbc.dr
connectionURL="jdbc:oracle
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles"
-->
<!--
<Realm className="org.apache.cata
driverName="sun.jdbc.odbc.
connectionURL="jdbc:odbc:C
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles"
-->
<!-- Define the default virtual host
Note: XML Schema validation will not work with Xerces 2.2.
-->
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<!-- Defines a cluster for this node,
By defining this element, means that every manager will be changed.
So when running a cluster, only make sure that you have webapps in there
that need to be clustered and remove the other ones.
A cluster has the following parameters:
className = the fully qualified name of the cluster class
name = a descriptive name for your cluster, can be anything
debug = the debug level, higher means more output
mcastAddr = the multicast address, has to be the same for all the nodes
mcastPort = the multicast port, has to be the same for all the nodes
mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
in case of multiple ethernet cards.
auto means that address becomes
InetAddress.getLocalHost()
tcpListenPort = the tcp listen port
tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
has a wakup bug in java.nio. Set to 0 for no timeout
printToScreen = true means that managers will also print to std.out
expireSessionsOnShutdown = true means that
useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribu
false means to replicate the session after each request.
false means that replication would work for the following piece of code:
<%
HashMap map = (HashMap)session.getAttrib
map.put("key","value");
%>
replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
* Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
* Synchronous means that the thread that executes the request, is also the
thread the replicates the data to the other nodes, and will not return until all
nodes have received the information.
* Asynchronous means that there is a specific 'sender' thread for each cluster node,
so the request thread will queue the replication request into a "smart" queue,
and then return to the client.
The "smart" queue is a queue where when a session is added to the queue, and the same session
already exists in the queue from a previous request, that session will be replaced
in the queue instead of replicating two requests. This almost never happens, unless there is a
large network delay.
-->
<!--
When configuring for clustering, you also add in a valve to catch all the requests
coming in, at the end of the request, the session may or may not be replicated.
A session is replicated if and only if all the conditions are met:
1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
2. a session exists (has been created)
3. the request is not trapped by the "filter" attribute
The filter attribute is to filter out requests that could not modify the session,
hence we don't replicate the session after the end of this request.
The filter is negative, ie, anything you put in the filter, you mean to filter out,
ie, no replication will be done on requests that match one of the filters.
The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
ending with .gif and .js are intercepted.
-->
<!--
<Cluster className="org.apache.cata
managerClassName="org.apac
expireSessionsOnShutdown="
useDirtyFlag="true">
<Membership
className="org.apache.cata
mcastAddr="228.0.0.4"
mcastPort="45564"
mcastFrequency="500"
mcastDropTime="3000"/>
<Receiver
className="org.apache.cata
tcpListenAddress="auto"
tcpListenPort="4001"
tcpSelectorTimeout="100"
tcpThreadCount="6"/>
<Sender
className="org.apache.cata
replicationMode="pooled"/>
<Valve className="org.apache.cata
filter=".*\.gif;.*\.js;.*\
</Cluster>
-->
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across *all* web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.cata
debug="0"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.cata
directory="logs" prefix="localhost_access_l
pattern="common" resolveHosts="false"/>
-->
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.cata
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
</Host>
</Engine>
</Service>
</Server>
cvdbt.xml (META_INF/context.xml ):
<Context displayName="CVDB Application" docBase="cvdbt" path="/cvdbt"
workDir="work\Catalina\loc
debug="5" reloadable="true" crossContext="true">
<Manager className="org.apache.cata
</Manager>
<!--Resource name="jdbc/CVDB" auth="Container"
type="javax.sql.DataSource
driverClassName="com.mysql
maxActive="8" maxIdle="4"/-->
<ResourceLink global="jdbc/CVDB" name="jdbc/CVDB" />
</Context>
web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<!-- generated by Spindle, http://spindle.sf.net -->
<web-app>
<display-name>cvdbt</displ
<servlet>
<servlet-name>cvdbt</servl
<servlet-class>org.apache.
<load-on-startup>1</load-o
</servlet>
<servlet-mapping>
<servlet-name>cvdbt</servl
<url-pattern>/app</url-pat
</servlet-mapping>
<resource-ref>
<description>
Resource reference to a factory for java.sql.Connection
instances that may be used for talking to a particular
database that is configured in the cvdbt.xml file ($CATALINA_HOME/conf/Catal
</description>
<res-ref-name>
jdbc/CVDB
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
</web-app>
Any ideas? I would be glad, if someone could help me...
ASKER
mysql Ver 12.22 Distrib 4.0.24, for pc-linux-gnu (i386)
mysql-connector-java-3.1.1 2-bin.jar
It works without connection pooling. I can get conncetion this way:
Class.forName("com.mysql.j dbc.Driver ");
result = DriverManager.getConnectio n("jdbc:my sql://192. 168.66.101 :3306/cvdb ", "katalma", "valami");
Maybe you are right, I don't know.
But, I found a mistake in my JAVA code, present version is:
ctx = new InitialContext();
Context envCtx = (Context) ctx.lookup("java:comp/env" );
DataSource ds = (DataSource) (envCtx.lookup(CVDBConnStr ing));
result = ds.getConnection();
And it seems to be working. I'm sad because I found this bug after I' posted this question, but, maybe it was necessary :) And I'm sad because of my helpfull colleges, because they hadn't seen this, they were blind like me.
mysql-connector-java-3.1.1
It works without connection pooling. I can get conncetion this way:
Class.forName("com.mysql.j
result = DriverManager.getConnectio
Maybe you are right, I don't know.
But, I found a mistake in my JAVA code, present version is:
ctx = new InitialContext();
Context envCtx = (Context) ctx.lookup("java:comp/env"
DataSource ds = (DataSource) (envCtx.lookup(CVDBConnStr
result = ds.getConnection();
And it seems to be working. I'm sad because I found this bug after I' posted this question, but, maybe it was necessary :) And I'm sad because of my helpfull colleges, because they hadn't seen this, they were blind like me.
don't be too sad.
You can get your points refund.
regards,
fargo
You can get your points refund.
regards,
fargo
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Which version of mysql r u using?
r u using the correct jdbc driver class name??? It depends upon your mysql version, do check.
I know that the exception you are getting is different then what i m saying, but sometimes, problems are related.
regards,
fargo