You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by tyju tiui <jc...@yahoo.com> on 2006/11/18 21:13:54 UTC
Pooling Issue
I'm having problems setting up connection pooling with
comcat 5.5.2.0 and MySQL 5.0.24 using mysql
connector/J 5.0.
I've setup / populated a test database and verified
that I can login to the server/db using the specified
username/password/host found in the connection string.
My server.xml looks like this:
<!-- 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">
<!-- Comment these entries out to disable JMX MBeans
support used for the
administration web application -->
<Listener
className="org.apache.catalina.core.AprLifecycleListener"
/>
<Listener
className="org.apache.catalina.mbeans.ServerLifecycleListener"
/>
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
/>
<Listener
className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
<!-- 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.UserDatabase"
description="User database that can be updated
and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
</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 HTTP/1.1 Connector on port
8080 -->
<Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
redirectPort="8443" acceptCount="100"
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="gozilla, traviata"
compressableMimeType="text/html,text/xml"
-->
<!-- Define a SSL HTTP/1.1 Connector on port 8443
-->
<!--
<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
disableUploadTimeout="true"
acceptCount="100" scheme="https"
secure="true"
clientAuth="false" sslProtocol="TLS" />
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009"
enableLookups="false"
redirectPort="8443" 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"
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 AJP ie :
<Engine name="Standalone" defaultHost="localhost"
jvmRoute="jvm1">
-->
<!-- Define the top level container in our
container hierarchy -->
<Engine name="Catalina" defaultHost="localhost">
<!-- 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/examples/WEB-INF/classes/filters").
Request dumping is disabled by default.
Uncomment the following
element to enable it. -->
<!--
<Valve
className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- 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.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here
for now in case we
need to go back quickly -->
<!--
<Realm
className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- 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.catalina.realm.JDBCRealm"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test"
connectionPassword="test"
userTable="users"
userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles"
roleNameCol="role_name" />
-->
<!--
<Realm
className="org.apache.catalina.realm.JDBCRealm"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott"
connectionPassword="tiger"
userTable="users"
userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles"
roleNameCol="role_name" />
-->
<!--
<Realm
className="org.apache.catalina.realm.JDBCRealm"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users"
userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles"
roleNameCol="role_name" />
-->
<!-- Define the default virtual host
Note: XML Schema validation will not work
with Xerces 2.2.
-->
<Host name="localhost" 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
clusterName = a descriptive name for your
cluster, can be anything
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
mcastBindAddress = bind the multicast
socket to a specific address
mcastTTL = the multicast TTL if you want
to limit your broadcast
mcastSoTimeout = the multicast
readtimeout
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().getHostAddress()
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,removeAttribute
has been called.
false means to replicate
the session after each request.
false means that
replication would work for the following piece of
code: (only for SimpleTcpReplicationManager)
<%
HashMap map =
(HashMap)session.getAttribute("map");
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.
The deployer element can be used to deploy
apps cluster wide.
Currently the deployment only
deploys/undeploys to working members in the cluster
so no WARs are copied upons startup of a
broken node.
The deployer watches a directory
(watchDir) for WAR files when watchEnabled="true"
When a new war file is added the war gets
deployed to the local instance,
and then deployed to the other instances
in the cluster.
When a war file is deleted from the
watchDir the war is undeployed locally
and cluster wide
-->
<!--
<Cluster
className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
managerClassName="org.apache.catalina.cluster.session.DeltaManager"
expireSessionsOnShutdown="false"
useDirtyFlag="true"
notifyListenersOnReplication="true">
<Membership
className="org.apache.catalina.cluster.mcast.McastService"
mcastAddr="228.0.0.4"
mcastPort="45564"
mcastFrequency="500"
mcastDropTime="3000"/>
<Receiver
className="org.apache.catalina.cluster.tcp.ReplicationListener"
tcpListenAddress="auto"
tcpListenPort="4001"
tcpSelectorTimeout="100"
tcpThreadCount="6"/>
<Sender
className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
replicationMode="pooled"
ackTimeout="15000"
waitForAck="true"/>
<Valve
className="org.apache.catalina.cluster.tcp.ReplicationValve"
filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
<Deployer
className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
tempDir="/tmp/war-temp/"
deployDir="/tmp/war-deploy/"
watchDir="/tmp/war-listen/"
watchEnabled="false"/>
<ClusterListener
className="org.apache.catalina.cluster.session.ClusterSessionListener"/>
</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.catalina.authenticator.SingleSignOn"
/>
-->
<!-- 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.catalina.valves.AccessLogValve"
directory="logs"
prefix="localhost_access_log." suffix=".txt"
pattern="common"
resolveHosts="false"/>
-->
<!-- 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.
This access log implementation is
optimized for maximum performance,
but is hardcoded to support only the
"common" and "combined" patterns.
-->
<!--
<Valve
className="org.apache.catalina.valves.FastCommonAccessLogValve"
directory="logs"
prefix="localhost_access_log." suffix=".txt"
pattern="common"
resolveHosts="false"/>
-->
<!-- ********** Pooling Config ********** -->
<Context path="/DBTest" docBase="DBTest"
debug="5" reloadable="true"
crossContext="true">
<Logger
className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log."
suffix=".txt"
timestamp="true"/>
<Resource name="jdbc/TestDB"
auth="Container"
type="javax.sql.DataSource"
factory="org.apache.commons.dbcp.BasicDataSourceFactory"
maxActive="100"
username="rpd"
password="2wERk4rpd"
maxIdle="30"
maxWait="10000"
driverClassName="com.mysql.jdbc.Driver"
removeAbandoned="true"
url="jdbc:mysql://localhost:3306/phptest?autoReconnect=true"
/>
</Context>
<!-- ********** End Pooling ********** -->
</Host>
</Engine>
</Service>
</Server>
I'm using the sample web.xml and test.jsp found at:
http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-examples-howto.html
There error I'm getting is:
org.apache.jasper.JasperException: Unable to get
connection, DataSource invalid:
"org.apache.commons.dbcp.SQLNestedException: Cannot
create PoolableConnectionFactory (Server connection
failure during transaction. Due to underlying
exception: 'java.net.SocketException:
java.net.ConnectException: Connection refused'.
** BEGIN NESTED EXCEPTION **
java.net.SocketException
MESSAGE: java.net.ConnectException: Connection refused
STACKTRACE:
java.net.SocketException: java.net.ConnectException:
Connection refused
at
com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:276)
at
com.mysql.jdbc.Connection.createNewIO(Connection.java:2815)
at
com.mysql.jdbc.Connection.<init>(Connection.java:1531)
at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
at
org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
at
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
at
org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
at
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
at
org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(Unknown
Source)
at
org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(Unknown
Source)
at
org.apache.jsp.test_jsp._jspx_meth_sql_query_0(test_jsp.java:100)
at
org.apache.jsp.test_jsp._jspService(test_jsp.java:58)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
** END NESTED EXCEPTION **
Attempted reconnect 3 times. Giving up.)"
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Any help would be greatly appreciated.
____________________________________________________________________________________
Sponsored Link
Compare mortgage rates for today.
Get up to 5 free quotes.
Www2.nextag.com
---------------------------------------------------------------------
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
Re: Pooling Issue
Posted by David Smith <dn...@cornell.edu>.
Well that's a stumper. The connection refused exception implies that
nothing is listening on that port or the port is blocked by a firewall.
Is there any more to that exception like a root cause? Given you are
using the localhost interface, I doubt this has a bearing but would you
happen to have any iptables or other firewall software active? In short
is there anything in your system that might prevent the connection?
--David
tyju tiui wrote:
> Hi David,
>
> Thank you so much for the response and good advice.
> I verified that I was able to connect to MySQL using
> the command you suggested (via port 3306). I also
> removed the autoReconnect parameter and moved the
> pooling config out to Catalina/localhost/DBTest.xml. I
> restarted tomcat and I'm still having the same issue.
>
> Do you have any other ideas?
>
> Thanks again,
>
> Ty
>
>
>
> --- David Smith <dn...@cornell.edu> wrote:
>
>
>> For starters, you might want to make a copy of your
>> server.xml file for
>> documentation purposes and then drop all the
>> comments from the active
>> one. The documentation comments are excellent, but
>> they make the
>> serverl.xml near impossible to read.
>>
>> At any rate.... the exception is connection refused.
>> Are you sure your
>> MySQL server is listening on port 3306? Some
>> default configurations use
>> unix sockets exclusively -- something java JDBC
>> drivers can't do. Try
>> this from the same machine your server is on:
>>
>> mysql -h localhost -P 3306 -u rpd -p
>>
>> The above command forces mysql client to connect via
>> TCP/IP with userid
>> rpd and prompt for a password. If this works, then
>> we're looking at
>> something else. If this doesn't, reconfigure your
>> mysql server to
>> listen on tcp/ip port 3306 and try again.
>>
>> Some additional recommendations -- not directly
>> related to your issue,
>> but worth mentioning:
>>
>> The <Context ...> ... </Context> block should be in
>> it's own xml file
>> under conf/Catalina/localhost, named to match the
>> context of your webapp
>> -- DBTest.xml in your case. Avoid setting this in
>> server.xml as it
>> requires restarting the tomcat container every time
>> you want to make a
>> change to your webapp's config.
>>
>> Drop the autoReconnect=true from your database url.
>> It isn't
>> recommended by MySQL and doesn't make sense in a
>> database connection
>> pool anyway.
>>
>> --David
>>
>> tyju tiui wrote:
>>
>>> I'm having problems setting up connection pooling
>>>
>> with
>>
>>> comcat 5.5.2.0 and MySQL 5.0.24 using mysql
>>> connector/J 5.0.
>>>
>>> I've setup / populated a test database and
>>>
>> verified
>>
>>> that I can login to the server/db using the
>>>
>> specified
>>
>>> username/password/host found in the connection
>>>
>> string.
>>
>>> My server.xml looks like this:
>>>
>>>
>>>
>> <snipped here .... a lot of irrelevant stuff to
>> the issue at hand. />
>>
>>> <!-- ********** Pooling Config **********
>>>
>> -->
>>
>>> <Context path="/DBTest" docBase="DBTest"
>>> debug="5" reloadable="true"
>>> crossContext="true">
>>>
>>>
>>>
>>>
>> < snipped again...../>
>>
>>> <Resource name="jdbc/TestDB"
>>> auth="Container"
>>> type="javax.sql.DataSource"
>>>
>>>
>>>
> factory="org.apache.commons.dbcp.BasicDataSourceFactory"
>
>>> maxActive="100"
>>> username="rpd"
>>> password="2wERk4rpd"
>>> maxIdle="30"
>>> maxWait="10000"
>>>
>>> driverClassName="com.mysql.jdbc.Driver"
>>> removeAbandoned="true"
>>>
>>>
>>>
> url="jdbc:mysql://localhost:3306/phptest?autoReconnect=true"
>
>>> />
>>>
>>> </Context>
>>> <!-- ********** End Pooling ********** -->
>>>
>>> </Host>
>>>
>>> </Engine>
>>>
>>> </Service>
>>>
>>> </Server>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> I'm using the sample web.xml and test.jsp found
>>>
>> at:
>>
> http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-examples-howto.html
>
>>>
>>>
>>>
>>>
>>> There error I'm getting is:
>>>
>>> org.apache.jasper.JasperException: Unable to get
>>> connection, DataSource invalid:
>>> "org.apache.commons.dbcp.SQLNestedException:
>>>
>> Cannot
>>
>>> create PoolableConnectionFactory (Server
>>>
>> connection
>>
>>> failure during transaction. Due to underlying
>>> exception: 'java.net.SocketException:
>>> java.net.ConnectException: Connection refused'.
>>>
>>> ** BEGIN NESTED EXCEPTION **
>>>
>>> java.net.SocketException
>>> MESSAGE: java.net.ConnectException: Connection
>>>
>> refused
>>
>>> STACKTRACE:
>>>
>>> java.net.SocketException:
>>>
>> java.net.ConnectException:
>>
>>> Connection refused
>>> at
>>>
>>>
> com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
>
>>> at
>>>
>> com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:276)
>>
>>> at
>>>
>>>
> com.mysql.jdbc.Connection.createNewIO(Connection.java:2815)
>
>>> at
>>>
>>>
> com.mysql.jdbc.Connection.<init>(Connection.java:1531)
>
>>> at
>>>
>>>
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
>
>>> at
>>>
>>>
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
>
>>> at
>>>
>>>
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
>
>>> at
>>>
>>>
> org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
>
>>> at
>>>
>>>
> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
>
>>> at
>>>
>>>
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
>
>>> at
>>>
>>>
> org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(Unknown
>
>>> Source)
>>> at
>>>
>>>
> org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(Unknown
>
>>> Source)
>>> at
>>>
>>>
> org.apache.jsp.test_jsp._jspx_meth_sql_query_0(test_jsp.java:100)
>
>>> at
>>>
>>>
> org.apache.jsp.test_jsp._jspService(test_jsp.java:58)
>
>>> at
>>>
>>>
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
>
>>> at
>>>
>>>
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
>>> at
>>>
>>>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
>
>>> at
>>>
>>>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
>
>>> at
>>>
>>>
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
>
> === message truncated ===
>
>
>
>
> ____________________________________________________________________________________
> Sponsored Link
>
> $420k for $1,399/mo.
> Think You Pay Too Much For Your Mortgage?
> Find Out! www.LowerMyBills.com/lre
>
> ---------------------------------------------------------------------
> 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
Re: Pooling Issue
Posted by tyju tiui <jc...@yahoo.com>.
Hi David,
Thank you so much for the response and good advice.
I verified that I was able to connect to MySQL using
the command you suggested (via port 3306). I also
removed the autoReconnect parameter and moved the
pooling config out to Catalina/localhost/DBTest.xml. I
restarted tomcat and I'm still having the same issue.
Do you have any other ideas?
Thanks again,
Ty
--- David Smith <dn...@cornell.edu> wrote:
> For starters, you might want to make a copy of your
> server.xml file for
> documentation purposes and then drop all the
> comments from the active
> one. The documentation comments are excellent, but
> they make the
> serverl.xml near impossible to read.
>
> At any rate.... the exception is connection refused.
> Are you sure your
> MySQL server is listening on port 3306? Some
> default configurations use
> unix sockets exclusively -- something java JDBC
> drivers can't do. Try
> this from the same machine your server is on:
>
> mysql -h localhost -P 3306 -u rpd -p
>
> The above command forces mysql client to connect via
> TCP/IP with userid
> rpd and prompt for a password. If this works, then
> we're looking at
> something else. If this doesn't, reconfigure your
> mysql server to
> listen on tcp/ip port 3306 and try again.
>
> Some additional recommendations -- not directly
> related to your issue,
> but worth mentioning:
>
> The <Context ...> ... </Context> block should be in
> it's own xml file
> under conf/Catalina/localhost, named to match the
> context of your webapp
> -- DBTest.xml in your case. Avoid setting this in
> server.xml as it
> requires restarting the tomcat container every time
> you want to make a
> change to your webapp's config.
>
> Drop the autoReconnect=true from your database url.
> It isn't
> recommended by MySQL and doesn't make sense in a
> database connection
> pool anyway.
>
> --David
>
> tyju tiui wrote:
> > I'm having problems setting up connection pooling
> with
> > comcat 5.5.2.0 and MySQL 5.0.24 using mysql
> > connector/J 5.0.
> >
> > I've setup / populated a test database and
> verified
> > that I can login to the server/db using the
> specified
> > username/password/host found in the connection
> string.
> > My server.xml looks like this:
> >
> >
> <snipped here .... a lot of irrelevant stuff to
> the issue at hand. />
> > <!-- ********** Pooling Config **********
> -->
> > <Context path="/DBTest" docBase="DBTest"
> > debug="5" reloadable="true"
> > crossContext="true">
> >
> >
> >
> < snipped again...../>
> > <Resource name="jdbc/TestDB"
> > auth="Container"
> > type="javax.sql.DataSource"
> >
> >
>
factory="org.apache.commons.dbcp.BasicDataSourceFactory"
> > maxActive="100"
> > username="rpd"
> > password="2wERk4rpd"
> > maxIdle="30"
> > maxWait="10000"
> >
> > driverClassName="com.mysql.jdbc.Driver"
> > removeAbandoned="true"
> >
> >
>
url="jdbc:mysql://localhost:3306/phptest?autoReconnect=true"
> > />
> >
> > </Context>
> > <!-- ********** End Pooling ********** -->
> >
> > </Host>
> >
> > </Engine>
> >
> > </Service>
> >
> > </Server>
> >
> >
> >
> >
> >
> >
> >
> > I'm using the sample web.xml and test.jsp found
> at:
> >
>
http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-examples-howto.html
> >
> >
> >
> >
> >
> >
> > There error I'm getting is:
> >
> > org.apache.jasper.JasperException: Unable to get
> > connection, DataSource invalid:
> > "org.apache.commons.dbcp.SQLNestedException:
> Cannot
> > create PoolableConnectionFactory (Server
> connection
> > failure during transaction. Due to underlying
> > exception: 'java.net.SocketException:
> > java.net.ConnectException: Connection refused'.
> >
> > ** BEGIN NESTED EXCEPTION **
> >
> > java.net.SocketException
> > MESSAGE: java.net.ConnectException: Connection
> refused
> >
> > STACKTRACE:
> >
> > java.net.SocketException:
> java.net.ConnectException:
> > Connection refused
> > at
> >
>
com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
> > at
> com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:276)
> > at
> >
>
com.mysql.jdbc.Connection.createNewIO(Connection.java:2815)
> > at
> >
>
com.mysql.jdbc.Connection.<init>(Connection.java:1531)
> > at
> >
>
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
> > at
> >
>
org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
> > at
> >
>
org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
> > at
> >
>
org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
> > at
> >
>
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
> > at
> >
>
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
> > at
> >
>
org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(Unknown
> > Source)
> > at
> >
>
org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(Unknown
> > Source)
> > at
> >
>
org.apache.jsp.test_jsp._jspx_meth_sql_query_0(test_jsp.java:100)
> > at
> >
>
org.apache.jsp.test_jsp._jspService(test_jsp.java:58)
> > at
> >
>
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> > at
> >
>
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> > at
> >
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
> > at
> >
>
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> > at
> >
>
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
>
=== message truncated ===
____________________________________________________________________________________
Sponsored Link
$420k for $1,399/mo.
Think You Pay Too Much For Your Mortgage?
Find Out! www.LowerMyBills.com/lre
---------------------------------------------------------------------
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
Re: Pooling Issue
Posted by David Smith <dn...@cornell.edu>.
For starters, you might want to make a copy of your server.xml file for
documentation purposes and then drop all the comments from the active
one. The documentation comments are excellent, but they make the
serverl.xml near impossible to read.
At any rate.... the exception is connection refused. Are you sure your
MySQL server is listening on port 3306? Some default configurations use
unix sockets exclusively -- something java JDBC drivers can't do. Try
this from the same machine your server is on:
mysql -h localhost -P 3306 -u rpd -p
The above command forces mysql client to connect via TCP/IP with userid
rpd and prompt for a password. If this works, then we're looking at
something else. If this doesn't, reconfigure your mysql server to
listen on tcp/ip port 3306 and try again.
Some additional recommendations -- not directly related to your issue,
but worth mentioning:
The <Context ...> ... </Context> block should be in it's own xml file
under conf/Catalina/localhost, named to match the context of your webapp
-- DBTest.xml in your case. Avoid setting this in server.xml as it
requires restarting the tomcat container every time you want to make a
change to your webapp's config.
Drop the autoReconnect=true from your database url. It isn't
recommended by MySQL and doesn't make sense in a database connection
pool anyway.
--David
tyju tiui wrote:
> I'm having problems setting up connection pooling with
> comcat 5.5.2.0 and MySQL 5.0.24 using mysql
> connector/J 5.0.
>
> I've setup / populated a test database and verified
> that I can login to the server/db using the specified
> username/password/host found in the connection string.
> My server.xml looks like this:
>
>
<snipped here .... a lot of irrelevant stuff to the issue at hand. />
> <!-- ********** Pooling Config ********** -->
> <Context path="/DBTest" docBase="DBTest"
> debug="5" reloadable="true"
> crossContext="true">
>
>
>
< snipped again...../>
> <Resource name="jdbc/TestDB"
> auth="Container"
> type="javax.sql.DataSource"
>
> factory="org.apache.commons.dbcp.BasicDataSourceFactory"
> maxActive="100"
> username="rpd"
> password="2wERk4rpd"
> maxIdle="30"
> maxWait="10000"
>
> driverClassName="com.mysql.jdbc.Driver"
> removeAbandoned="true"
>
> url="jdbc:mysql://localhost:3306/phptest?autoReconnect=true"
> />
>
> </Context>
> <!-- ********** End Pooling ********** -->
>
> </Host>
>
> </Engine>
>
> </Service>
>
> </Server>
>
>
>
>
>
>
>
> I'm using the sample web.xml and test.jsp found at:
> http://tomcat.apache.org/tomcat-5.0-doc/jndi-datasource-examples-howto.html
>
>
>
>
>
>
> There error I'm getting is:
>
> org.apache.jasper.JasperException: Unable to get
> connection, DataSource invalid:
> "org.apache.commons.dbcp.SQLNestedException: Cannot
> create PoolableConnectionFactory (Server connection
> failure during transaction. Due to underlying
> exception: 'java.net.SocketException:
> java.net.ConnectException: Connection refused'.
>
> ** BEGIN NESTED EXCEPTION **
>
> java.net.SocketException
> MESSAGE: java.net.ConnectException: Connection refused
>
> STACKTRACE:
>
> java.net.SocketException: java.net.ConnectException:
> Connection refused
> at
> com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
> at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:276)
> at
> com.mysql.jdbc.Connection.createNewIO(Connection.java:2815)
> at
> com.mysql.jdbc.Connection.<init>(Connection.java:1531)
> at
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
> at
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
> at
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
> at
> org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
> at
> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
> at
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
> at
> org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.getConnection(Unknown
> Source)
> at
> org.apache.taglibs.standard.tag.common.sql.QueryTagSupport.doStartTag(Unknown
> Source)
> at
> org.apache.jsp.test_jsp._jspx_meth_sql_query_0(test_jsp.java:100)
> at
> org.apache.jsp.test_jsp._jspService(test_jsp.java:58)
> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
> at java.lang.Thread.run(Thread.java:595)
>
>
> ** END NESTED EXCEPTION **
>
>
> Attempted reconnect 3 times. Giving up.)"
>
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512)
>
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
>
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
>
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
>
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
>
>
>
>
>
>
>
>
>
> Any help would be greatly appreciated.
>
>
>
> ____________________________________________________________________________________
> Sponsored Link
>
> Compare mortgage rates for today.
> Get up to 5 free quotes.
> Www2.nextag.com
>
> ---------------------------------------------------------------------
> 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