Hi Romain. We lookef for DB locks, but it's only SELECT and INSERT statements, which should not cause locking on postgresql. And we also looked for locks using postgresql debuging, analytics. So we suspected the network and the JDBC driver, we did some TCP stack tuning, but also no major change.
Everything does run on VMWARE, so maybe this could be also something to look at. We could add some more Tomcat DB pool timeouts, but this is a dirty "fix". Can this be a phenomen of not enough connections in pool. But I would suspect a performance drop not lock. Can somebody explain this: is 1 transaction == 1 connection. So connected beans share the same connection and transcation? BR Matej 2015-06-10 19:24 GMT+02:00 Romain Manni-Bucau <[email protected]>: > well before playing with config the idea is to know what happened, is the > network quality the cause for instance? > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2015-06-10 10:22 GMT-07:00 Howard W. Smith, Jr. <[email protected]>: > > > On Wed, Jun 10, 2015 at 1:18 PM, Romain Manni-Bucau < > [email protected] > > > > > wrote: > > > > > Hi Matej > > > > > > looks like a database issue for me (stateless pool is waiting for the > > > stateless trying to get the db connection to be released), hasnt the DB > > > connection be lost or something like that? > > > > > > > > what is the best way for Matej to improve that? tomcat jdbc pool > settings? > > >
