Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #3180 (closed)

Opened 14 years ago

Closed 14 years ago

Bug: Max'ing concurrent connections leads to "idle in transaction" death

Reported by: jamoore Owned by: jamoore
Priority: critical Milestone: OMERO-Beta4.2.1
Component: Performance Version: n.a.
Keywords: n.a. Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: 2010-10-28 (18)

Description

While testing omero.db.poolsize for 4.2.1 (#3179) a test of 100 threads all calling IConfig.getConfigValue() against a server with omero.db.poolsize == 50 lead to approx. 50 PG connections in the dreaded "idle in transaction state".

Removing our special handling of these exceptions ("SelfCorrectingDataSource" and Spring's "LazyConnectionDataSourceProxy") significantly improved throughput.

See also #3173 (session store concurrency)

Change History (2)

comment:1 Changed 14 years ago by jmoore

  • Owner set to jmoore
  • Status changed from new to assigned

comment:2 Changed 14 years ago by jmoore

  • Remaining Time set to 0
  • Resolution set to fixed
  • Status changed from assigned to closed

(In [8394]) Removing use of Spring's LazyConnectionDataSourceProxy (Fix #3180)

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.65050 sec.)

© 2000-2014 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!