You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jerry Malcolm <te...@malcolms.com> on 2017/01/06 15:35:17 UTC

LogAbandoned Stack Trace?

I'm getting "too many connections" errors.  I'm pretty sure I am 
configured with enough connections that I shouldn't run out.  So I'm 
assuming I'm leaving some connections open.  I have LogAbandoned="true" 
in my jdbc resource statements.  The doc says TC will log a stack trace 
of abandoned connections.  But I don't see any stack traces.  Would they 
be in stderr, stdout, catalina log?  Or is it that I'm actually not 
getting any abandoned?

Thx.


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


Re: LogAbandoned Stack Trace?

Posted by Phil Steitz <ph...@gmail.com>.
On 1/10/17 12:48 PM, Christopher Schultz wrote:
> Phil,
>
> On 1/8/17 5:41 PM, Phil Steitz wrote:
> > On 1/6/17 3:44 PM, Jerry Malcolm wrote:
> >> On 1/6/2017 4:30 PM, Christopher Schultz wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
> >>>
> >>> Jerry,
> >>>
> >>> On 1/6/17 10:35 AM, Jerry Malcolm wrote:
> >>>> I'm getting "too many connections" errors.
> >>> Where?
> >>>
> >>> Can you provide an exact error message and, better yet, a
> >>> stack trace?
> >>>
> >>>> I'm pretty sure I am configured with enough connections that
> >>>> I shouldn't run out.  So I'm assuming I'm leaving some
> >>>> connections open.
> >>> That's a good assumption.
> >>>
> >>>> I have LogAbandoned="true" in my jdbc resource statements.
> >>>> The doc says TC will log a stack trace of abandoned
> >>>> connections.  But I don't see any stack traces.  Would they
> >>>> be in stderr, stdout, catalina log? Or is it that I'm
> >>>> actually not getting any abandoned?
> >>> Which db connection pool are you using? Standard (DBCP-based)
> >>> or tomcat-pool? A full (sanitized) <Resource> configuration
> >>> would help.
> >>>
> >>> - -chris
> >>>
> >> Chris, Stack trace follows.  It looks like it may be mySQL
> >> that's rejecting the connection.  But even if that's the case,
> >> it's probably because I'm not closing some connections, which
> >> should still generate a logAbandoned stack trace, correct?  I
> >> believe I'm using dbcp.  Not doing anything fancy... Just
> >> defining data source resources in the context file:
> >>
> >> <Resource testOnBorrow="true" validationQuery="SELECT 1"
> >> name="jdbc/cis" auth="Container" type="javax.sql.DataSource"
> >> maxTotal="100" maxIdle="30" maxWaitMillis="10000"
> >> removeAbandoned="true" removeAbandonedTimeout="60"
> >> logAbandoned="true" username="xxxxxxxx" password="xxxxxxx"
> >> driverClassName="com.mysql.jdbc.Driver"
> >> url="jdbc:mysql://localhost:3306/xxxxxxxxxx" />
> > In dbcp 2, the "removeAbandoned" config option was replaced by
> > removedAbondonedOnBorrow and removeAbandonedOnMaintenance.  You
> > need to set one of these to true the get abandoned connection
> > cleanup to work.  See [1].
>
> > |Phil
>
> > [1]
> > http://commons.apache.org/proper/commons-dbcp/configuration.html
>
> +1
>
> Jerry never said what version of Tomcat he was using... I was assuming
> a DBCP 1.x-based version given his configuration.

From the stack trace, you can see dbcp2 in the package names.  I am
correct in assuming that tomcat does not kindly
s/removeAbandoned/removeAbandonedOnBorrow, right?

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



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


Re: LogAbandoned Stack Trace?

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Phil,

On 1/8/17 5:41 PM, Phil Steitz wrote:
> On 1/6/17 3:44 PM, Jerry Malcolm wrote:
>> On 1/6/2017 4:30 PM, Christopher Schultz wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>>> 
>>> Jerry,
>>> 
>>> On 1/6/17 10:35 AM, Jerry Malcolm wrote:
>>>> I'm getting "too many connections" errors.
>>> Where?
>>> 
>>> Can you provide an exact error message and, better yet, a
>>> stack trace?
>>> 
>>>> I'm pretty sure I am configured with enough connections that
>>>> I shouldn't run out.  So I'm assuming I'm leaving some
>>>> connections open.
>>> That's a good assumption.
>>> 
>>>> I have LogAbandoned="true" in my jdbc resource statements.
>>>> The doc says TC will log a stack trace of abandoned
>>>> connections.  But I don't see any stack traces.  Would they
>>>> be in stderr, stdout, catalina log? Or is it that I'm
>>>> actually not getting any abandoned?
>>> Which db connection pool are you using? Standard (DBCP-based)
>>> or tomcat-pool? A full (sanitized) <Resource> configuration
>>> would help.
>>> 
>>> - -chris
>>> 
>> Chris, Stack trace follows.  It looks like it may be mySQL
>> that's rejecting the connection.  But even if that's the case,
>> it's probably because I'm not closing some connections, which
>> should still generate a logAbandoned stack trace, correct?  I
>> believe I'm using dbcp.  Not doing anything fancy... Just
>> defining data source resources in the context file:
>> 
>> <Resource testOnBorrow="true" validationQuery="SELECT 1" 
>> name="jdbc/cis" auth="Container" type="javax.sql.DataSource" 
>> maxTotal="100" maxIdle="30" maxWaitMillis="10000" 
>> removeAbandoned="true" removeAbandonedTimeout="60" 
>> logAbandoned="true" username="xxxxxxxx" password="xxxxxxx" 
>> driverClassName="com.mysql.jdbc.Driver" 
>> url="jdbc:mysql://localhost:3306/xxxxxxxxxx" />
> In dbcp 2, the "removeAbandoned" config option was replaced by 
> removedAbondonedOnBorrow and removeAbandonedOnMaintenance.  You
> need to set one of these to true the get abandoned connection
> cleanup to work.  See [1].
> 
> |Phil
> 
> [1]
> http://commons.apache.org/proper/commons-dbcp/configuration.html

+1

Jerry never said what version of Tomcat he was using... I was assuming
a DBCP 1.x-based version given his configuration.

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYdTqkAAoJEBzwKT+lPKRYE3IP/27WYTjNJMy9zKO6/0EGKH7C
SNhRRlz+uFWZsgVLlHHX1DVMnjBKRcfQBVqRPWflUe4LYWxVFxBAHuZ+luOBtZJp
4WgFBaroj/D8PQUKPkoetAN8iQU/BZ8Axn64bOp4WmaREyoS+vCkUiyRP6+a5Uve
wEjYATrNBGe4ISQQ5rpqHHR4XHNvY0xSXWtopkgowp2Y3ykyae+6SPlufK4CYf7n
m09YJszTc1sqCPQ1kCrbi0CVtF2RPOPqE2PGEA03t2Xk4aeAJROv17/FgvYVNS1G
D3wzKmhCt3qlx1D/IsdM2giujHGA3nhojKzF1XaLUPjt8UauZBIN51JO2wDKOhJH
FJJ6p+5pb4IRqOweEtYoDsoDzXUJr5nSd0AIxT43IFgXbNTH7t41j5hNdZ3dr1WE
/hPrMa8sEGu5Yv6jfuf4Xlw9h/R9WCnSiACxlHFvGKBf1edsOHoJnR7gkYTZpC3H
cdRW7q9zSU1qre96ODHmT9rXWq25hyKs0p7ig5cOKyG0f7zFrJRLgwvuW4oMgPvU
2piKjBrNIzEo/dOyjjkVMoqGr5Bj7LOr8q6vCEJO+lQ+RbQU76zLJ5Yg0vlUsO+A
qlyAi2mDcBJpQEvt6OjNt1zhlQ7Wet7okp25ki+0jozJu33jBfn2NP0Uiqk4HYsL
LqwPhvP8UM9rSkobr8ox
=rO7t
-----END PGP SIGNATURE-----

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


Re: LogAbandoned Stack Trace?

Posted by Phil Steitz <ph...@gmail.com>.
On 1/6/17 3:44 PM, Jerry Malcolm wrote:
> On 1/6/2017 4:30 PM, Christopher Schultz wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Jerry,
>>
>> On 1/6/17 10:35 AM, Jerry Malcolm wrote:
>>> I'm getting "too many connections" errors.
>> Where?
>>
>> Can you provide an exact error message and, better yet, a stack
>> trace?
>>
>>> I'm pretty sure I am configured with enough connections that I
>>> shouldn't run out.  So I'm assuming I'm leaving some connections
>>> open.
>> That's a good assumption.
>>
>>> I have LogAbandoned="true" in my jdbc resource statements.  The
>>> doc says TC will log a stack trace of abandoned connections.  But I
>>> don't see any stack traces.  Would they be in stderr, stdout,
>>> catalina log? Or is it that I'm actually not getting any
>>> abandoned?
>> Which db connection pool are you using? Standard (DBCP-based) or
>> tomcat-pool? A full (sanitized) <Resource> configuration would help.
>>
>> - -chris
>>
> Chris,
> Stack trace follows.  It looks like it may be mySQL that's
> rejecting the connection.  But even if that's the case, it's
> probably because I'm not closing some connections, which should
> still generate a logAbandoned stack trace, correct?  I believe I'm
> using dbcp.  Not doing anything fancy... Just defining data source
> resources in the context file:
>
>    <Resource testOnBorrow="true" validationQuery="SELECT 1"
> name="jdbc/cis" auth="Container" type="javax.sql.DataSource"
> maxTotal="100" maxIdle="30" maxWaitMillis="10000"
> removeAbandoned="true" removeAbandonedTimeout="60"
> logAbandoned="true" username="xxxxxxxx" password="xxxxxxx"
> driverClassName="com.mysql.jdbc.Driver"
> url="jdbc:mysql://localhost:3306/xxxxxxxxxx" />
In dbcp 2, the "removeAbandoned" config option was replaced by
removedAbondonedOnBorrow and removeAbandonedOnMaintenance.  You need
to set one of these to true the get abandoned connection cleanup to
work.  See [1].

|Phil

[1] http://commons.apache.org/proper/commons-dbcp/configuration.html
|||
>
>
>
> java.sql.SQLException: Cannot create PoolableConnectionFactory
> (Data source rejected establishment of connection,  message from
> server: "Too many connections")
>         at
> org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2195)
>         at
> org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:1945)
>         at
> org.apache.tomcat.dbcp.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1412)
>         at
> jwm.servletdb.ServletDBData.getInstance(ServletDBData.java:139)
>         at
> jwm.servletdb.ServletDBData.getInstance(ServletDBData.java:93)
>         at
> jwm.servletdb.ServletDBData.getInstance(ServletDBData.java:62)
>         at
> org.apache.jsp.jsp.login.login_005fv2_jsp._jspService(login_005fv2_jsp.java:450)
>         at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>         at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
>         at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
>         at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
>
>         at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
>         at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
>         at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
>         at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>
>         at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
>         at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:721)
>         at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:466)
>         at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)
>         at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)
>         at
> org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:411)
>         at
> org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:256)
>         at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
>         at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
>         at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
>         at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
>         at
> org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:291)
>         at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
>         at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:537)
>         at
> org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:831)
>         at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:658)
>         at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1556)
>         at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1513)
>         at
> java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>         at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>         at java.lang.Thread.run(Unknown Source)
> Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> Data source rejected establishment of connection,  message from
> server: "Too many connections"
>         at
> sun.reflect.GeneratedConstructorAccessor97.newInstance(Unknown
> Source)
>         at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
> Source)
>         at java.lang.reflect.Constructor.newInstance(Unknown Source)
>         at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>         at com.mysql.jdbc.Util.getInstance(Util.java:386)
>         at
> com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1013)
>         at
> com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
>         at
> com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
>         at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1128)
>         at
> com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
>         at
> com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
>         at
> com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
>         at
> com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:792)
>         at
> com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
>         at
> sun.reflect.GeneratedConstructorAccessor20.newInstance(Unknown
> Source)
>         at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
> Source)
>         at java.lang.reflect.Constructor.newInstance(Unknown Source)
>         at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>         at
> com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:381)
>         at
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305)
>         at
> org.apache.tomcat.dbcp.dbcp2.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
>         at
> org.apache.tomcat.dbcp.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:204)
>         at
> org.apache.tomcat.dbcp.dbcp2.BasicDataSource.validateConnectionFactory(BasicDataSource.java:2205)
>         at
> org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2191)
>         ... 38 more
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>



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


Re: LogAbandoned Stack Trace?

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Jerry,

On 1/6/17 5:44 PM, Jerry Malcolm wrote:
> On 1/6/2017 4:30 PM, Christopher Schultz wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> Jerry,
>> 
>> On 1/6/17 10:35 AM, Jerry Malcolm wrote:
>>> I'm getting "too many connections" errors.
>> Where?
>> 
>> Can you provide an exact error message and, better yet, a stack
>> trace?
>> 
>>> I'm pretty sure I am configured with enough connections that I 
>>> shouldn't run out.  So I'm assuming I'm leaving some
>>> connections open.
>> That's a good assumption.
>> 
>>> I have LogAbandoned="true" in my jdbc resource statements.
>>> The doc says TC will log a stack trace of abandoned
>>> connections.  But I don't see any stack traces.  Would they be
>>> in stderr, stdout, catalina log? Or is it that I'm actually not
>>> getting any abandoned?
>> Which db connection pool are you using? Standard (DBCP-based) or 
>> tomcat-pool? A full (sanitized) <Resource> configuration would
>> help.
>> 
>> - -chris
>> 
> Chris, Stack trace follows.  It looks like it may be mySQL that's
> rejecting the connection.  But even if that's the case, it's
> probably because I'm not closing some connections, which should
> still generate a logAbandoned stack trace, correct?  I believe I'm
> using dbcp.  Not doing anything fancy... Just defining data source
> resources in the context file:
> 
> <Resource testOnBorrow="true" validationQuery="SELECT 1" 
> name="jdbc/cis" auth="Container" type="javax.sql.DataSource" 
> maxTotal="100" maxIdle="30" maxWaitMillis="10000"
> removeAbandoned="true" removeAbandonedTimeout="60"
> logAbandoned="true" username="xxxxxxxx" password="xxxxxxx"
> driverClassName="com.mysql.jdbc.Driver" 
> url="jdbc:mysql://localhost:3306/xxxxxxxxxx" />

Can you reproduce this in a testing environment? If not, I'd recommend
the following:

1. Use maxActive="1" in dev/testing
2. removeAbandoned="false" in dev/testing

These two settings will grind your application to a halt in
dev/testing when you drop a connection because there's only one to go
around. It will also help you find deadlock timebombs you may have
when a thread tries to check-out two connections when only one is
appropriate.

You also might want to use a static-analysis tool like FindBugs to
scan your code: it might find a bunch of places where you can
immediately see missing Connection.close() calls.

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYcCLYAAoJEBzwKT+lPKRYOP8QAIssYUCTjyV/ukTVtYFJHVyv
upyqmFkoydAlHJzBluJw0U8NpT12+/mKN6JJJIJPtZZfvNc0kGq0Vd7Vl7mTOQx1
UZqH9ENrpzy+bPGjs2+21b1pstBas4TSyq3zM2nlx1QRgMwit31ywwJyYk3veYDf
On20vAWGh3eT1xgnr+IXBCkn0KX6R4JgbRkX2Rh0Dpuah/7QmsNJI/tgBDyqDoOF
UW2tN8oW6YfG0CLyodZWwg9jdM9cmLQgNmAc1TNqwoT+BqVDvHEVenLBTRL0OxWs
XYSSmoFiivHdT1X6Wy7wR0Ido1/GrKxDD6WvdbRi8ZKqWOYUrjRehKuNE6NzeXH9
OVQBi6bmtTN853HEO6YBh54GQg3JblpyRxJ64fsmdnm/TvvylEUdfPVKnIjxlv5o
AYpcfLsg0332xI/MmX+kRbfbQEpBv5fMR0M59p/FT0HYFMc6XtU+6AU6MNmYLwIP
zFFPTWKYfswrfXG/PzM6ZU6DBX50UnR9pUmLUoC5n+h31AZMJ7cGxZSVOZ8pLlAt
9KL7h79uNLFUhgBvnHQwLswSm9lgAl6IJzPGOXRssmmWbNiB9+vSzkLjVOZg8Zze
Rvj5LhsN4DylhBMXY9b+7tMqBHih9xZV/9ReDIpQ569bJX0t/mpXQemO01qVM9n7
vpqgCeLCy6QAjxNZsFgU
=DIwn
-----END PGP SIGNATURE-----

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


Re: LogAbandoned Stack Trace?

Posted by Jerry Malcolm <te...@malcolms.com>.
On 1/6/2017 4:30 PM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Jerry,
>
> On 1/6/17 10:35 AM, Jerry Malcolm wrote:
>> I'm getting "too many connections" errors.
> Where?
>
> Can you provide an exact error message and, better yet, a stack trace?
>
>> I'm pretty sure I am configured with enough connections that I
>> shouldn't run out.  So I'm assuming I'm leaving some connections
>> open.
> That's a good assumption.
>
>> I have LogAbandoned="true" in my jdbc resource statements.  The
>> doc says TC will log a stack trace of abandoned connections.  But I
>> don't see any stack traces.  Would they be in stderr, stdout,
>> catalina log? Or is it that I'm actually not getting any
>> abandoned?
> Which db connection pool are you using? Standard (DBCP-based) or
> tomcat-pool? A full (sanitized) <Resource> configuration would help.
>
> - -chris
>
Chris,
Stack trace follows.  It looks like it may be mySQL that's rejecting the 
connection.  But even if that's the case, it's probably because I'm not 
closing some connections, which should still generate a logAbandoned 
stack trace, correct?  I believe I'm using dbcp.  Not doing anything 
fancy... Just defining data source resources in the context file:

    <Resource testOnBorrow="true" validationQuery="SELECT 1" 
name="jdbc/cis" auth="Container" type="javax.sql.DataSource" 
maxTotal="100" maxIdle="30" maxWaitMillis="10000" removeAbandoned="true" 
removeAbandonedTimeout="60" logAbandoned="true" username="xxxxxxxx" 
password="xxxxxxx" driverClassName="com.mysql.jdbc.Driver" 
url="jdbc:mysql://localhost:3306/xxxxxxxxxx" />


java.sql.SQLException: Cannot create PoolableConnectionFactory (Data 
source rejected establishment of connection,  message from server: "Too 
many connections")
         at 
org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2195)
         at 
org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:1945)
         at 
org.apache.tomcat.dbcp.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1412)
         at jwm.servletdb.ServletDBData.getInstance(ServletDBData.java:139)
         at jwm.servletdb.ServletDBData.getInstance(ServletDBData.java:93)
         at jwm.servletdb.ServletDBData.getInstance(ServletDBData.java:62)
         at 
org.apache.jsp.jsp.login.login_005fv2_jsp._jspService(login_005fv2_jsp.java:450)
         at 
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
         at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
         at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
         at 
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
         at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
         at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
         at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
         at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:721)
         at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:466)
         at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)
         at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)
         at 
org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:411)
         at 
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:256)
         at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
         at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
         at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
         at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
         at 
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:291)
         at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
         at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:537)
         at 
org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:831)
         at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:658)
         at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1556)
         at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1513)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown 
Source)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
Source)
         at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
         at java.lang.Thread.run(Unknown Source)
Caused by: 
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: 
Data source rejected establishment of connection,  message from server: 
"Too many connections"
         at 
sun.reflect.GeneratedConstructorAccessor97.newInstance(Unknown Source)
         at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
         at java.lang.reflect.Constructor.newInstance(Unknown Source)
         at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
         at com.mysql.jdbc.Util.getInstance(Util.java:386)
         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1013)
         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
         at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1128)
         at 
com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2336)
         at 
com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2369)
         at 
com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2153)
         at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:792)
         at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
         at 
sun.reflect.GeneratedConstructorAccessor20.newInstance(Unknown Source)
         at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
         at java.lang.reflect.Constructor.newInstance(Unknown Source)
         at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
         at 
com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:381)
         at 
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:305)
         at 
org.apache.tomcat.dbcp.dbcp2.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
         at 
org.apache.tomcat.dbcp.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:204)
         at 
org.apache.tomcat.dbcp.dbcp2.BasicDataSource.validateConnectionFactory(BasicDataSource.java:2205)
         at 
org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2191)
         ... 38 more


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


Re: LogAbandoned Stack Trace?

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Jerry,

On 1/6/17 10:35 AM, Jerry Malcolm wrote:
> I'm getting "too many connections" errors.

Where?

Can you provide an exact error message and, better yet, a stack trace?

> I'm pretty sure I am configured with enough connections that I 
> shouldn't run out.  So I'm assuming I'm leaving some connections 
> open.

That's a good assumption.

> I have LogAbandoned="true" in my jdbc resource statements.  The
> doc says TC will log a stack trace of abandoned connections.  But I
> don't see any stack traces.  Would they be in stderr, stdout,
> catalina log? Or is it that I'm actually not getting any
> abandoned?

Which db connection pool are you using? Standard (DBCP-based) or
tomcat-pool? A full (sanitized) <Resource> configuration would help.

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYcBp5AAoJEBzwKT+lPKRYXuMP/0lKpStpX0OdG3HjNRR3iuLF
QBN5tl7v/+kAdlBzDRsGo5TosX5jOdyjrn3kSdLA1EuDE/5AkrHmgBxeo/nriUwM
QOPudlC40IA2x8+OvkNgHM5ELqohW0keNe44bGTrrvqyw7So16huGmYQnJI0ZKSe
PvfWxFtTRF3/maB0OtIy+xk+jxqG7bxx8YghlO2Of1MNvoYRZyjZ/4kdEh4h76VQ
2okjznZaNH9ZN6VJNbCzNlK4mpBbf0wz4FPV7qiIXobz0AkL8KHaHy4Z4QS8sAYF
rp9Z8V/oCMqbg2ULnDK03xcuYdFW9/DfYcMhojv/Dw+5fQOqhlZPm/LrgL47g5Mq
yW1ohryIV63GRO4VpTy51mgu1gyTAjQc971xJgg+fHQjkbqTMrqmxnQRRplvZhBg
57bmBlC2QQGh2Kp0VuMS/HDyTPGJ4gpQcUPB2LUl0y2mdPezxfE9oNhs8Rx0N7iE
41q6nwe85Qw63CIb+7FI9fRXnNYks98WuU488Aj5J919vnin3FhrQ09UPoJqXuTm
u6XJoOo5xt5pu0Er8ydUZumcES7yercGvTLdqrspjlQhprItWOT55aTftN3/GyVd
AKf3Bw/E5EQgvDs+X5novo7DnhJv1xxHgQviRdzPhAHwyBhM6POF4MS7ZawSERq/
QiZGvqYhicHGLTMjLq4s
=jMzt
-----END PGP SIGNATURE-----

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