tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: jdbc connection pool size 2
Date Fri, 28 Sep 2018 09:14:13 GMT
Hello,

are you able to use jmx to dump the datasource mbeans to see the actual
config? (ensure to remove your credentials before sharing this ;)).

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le ven. 28 sept. 2018 à 10:55, clemensx <clemens.fehr@sap.com> a écrit :

> Hi,
>
> we use TomEE 7.0.4 productively in a Cloud Foundry environment. JDBC
> connections are only used via JPA (eclipselink). Usually after one day or
> so
> uptime we see these errors:
>
> org.apache.tomcat.jdbc.pool.PoolExhaustedException: [http-nio-8080-exec-10]
> Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none
> available[size:2; busy:2; idle:0; lastwait:30000].",
>
> We did not specify pool size anywhere and I believe standard pool size is
> more like 100 than 2. What could cause this extremely small pool size? Is
> this somehow negotiated with the JDBC driver and/or DBMS? We use postgresql
> 9.4.1212 jdbc driver for a postgresql server on version 9.6.
>
> Any ideas greatly appreciated. Many thanks!
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message