Thank you for help! BRM
2015-06-10 20:21 GMT+02:00 Romain Manni-Bucau <[email protected]>: > 2015-06-10 11:17 GMT-07:00 Matej <[email protected]>: > > > Hi. > > > > Maybe what i forgot to tell is that when looking at the database we see > > many connections like that: > > > > IDLE IN TRANSACTION, mayn (ALL) transaction that are long running, > waiting > > for commit statemet which somehow doesn't happen. > > > > And the CPU load on DB and App server is almost 0, so the system does > seem > > to lock up. > > > > Romain, last question can 2 or more transaction share the same > connection, > > maybe this could cause some locks to deadlock?.... > > > > > shouldnt normally > > Now on what you observe it really looks like the connection is somehow lost > on client side. Maybe try to kill connection on DB side, it could throw an > error on application side and unlock the app maybe. If so the network has > an issue somewhere. > > > > > > BR > > > > Matej > > > > > > > > > > 2015-06-10 20:01 GMT+02:00 Romain Manni-Bucau <[email protected]>: > > > > > 2015-06-10 10:59 GMT-07:00 Matej <[email protected]>: > > > > > > > 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. > > > > > > > > > > > was more thinking about locks in the datasource pool than on db side > (ie > > > pool size too small) > > > > > > > > > > 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". > > > > > > > > > > set the timeout to maybe 0 to set the app failing is there is not > enough > > > connections in the pool > > > > > > > > > > > > > > Can this be a phenomen of not enough connections in pool. But I would > > > > suspect a performance drop not lock. > > > > > > > > > > well i dont see locks in the logs but "locked" which means waiting for > > > something to happen (getting the connection) > > > > > > > > > > > > > > Can somebody explain this: is 1 transaction == 1 connection. So > > > connected > > > > beans share the same connection and transcation? > > > > > > > > > > by datasource you have 1 connection per transaction yes > > > > > > > > > > > > > > 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? > > > > > > > > > > > > > > > > > > > > >
