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?
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:08 GMT-07:00 Matej <[email protected]>: > Hello everyone. > > Anybody experience problems with Statelles timeout, idle in transaction > symptoms with Tomee under load. > > In production with modest load on servers we regulary experience problemes > with a deadlock which deosn't seem to originate from the DB. > > It seems to be dependet on the Stateless maxactive parameter. When > increasing this parameter usually the locking happens. At the database > level, we just see IDLE in TRANSACTION connections. > > We tried many things: > -JDK update > -tomee update > -increasing TCP buffers, other parameters. > > But nothing really solved it. By chaning the Statelles count, we seem to > influence something, but I don't really now if this is the cause of the > problem. The only thing that seems to help is limit the Statless paramter > and removing SQL statements, which are mostly SELECT and INSERT, so locking > should not happen. > > I have also a stacktrace if someone is willing to check. > > > BR > > Matej > > >
