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 #10245 (new)

Opened 8 years ago

Last modified 5 years ago

BUG: Resource issues with OMERO.tables

Reported by: spli Owned by: spli
Priority: major Milestone: Metadata
Component: Services Version: OMERO-5.2.0
Keywords: n.a. Cc: analysis@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by spli)

I've been seeing some strange behaviour with OMERO.tables when making a large number of calls to add data from OMERO.scripts. This includes scripts exiting due to a failure to communicate with the Tables service, the Tables service using 100% CPU even after all clients have disconnected, apparent out-of-memory errors with theTables service (manifested as an OS X "Problem Report for Python" dialog).

Further investigation suggets this is due to opening/closing a table too frequently. For instance, reusing a connection/handle to a table instead of opening and closing the table for every operation (read, addData) seems to work fine. Still a bug though.

Attachments (1)

python-tables-crash2.txt (73.0 KB) - added by spli 8 years ago.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by spli

comment:1 Changed 8 years ago by spli

  • Description modified (diff)

comment:2 Changed 8 years ago by spli

Turns out this (or something similar) is a problem even when the table connections are reused. Occasionally the Tables service is killed and restarts automatically, the only sign is a "Python quit unexpectedly" OS X dialog, with no obvious error log. Tables-0.log only has a ***** ... Waiting 10000 ms on startup indicating the service was restarted with no error prior to this. master.err only has a failed connection from the scripts trying to connect:

01/28/13 16:09:17.917 OMERO.Glacier2: warning: dispatch exception: TcpTransceiver.cpp:158: Ice::ConnectionLostException:
connection lost: recv() returned zero
identity: 7D992E29-C70F-4C25-A3CB-284C8A9824C2
facet: 
operation: getWhereList
01/28/13 16:09:17.919 OMERO.Glacier2: warning: dispatch exception: TcpTransceiver.cpp:158: Ice::ConnectionLostException:
connection lost: recv() returned zero
identity: 986F88C9-E3CD-467B-B2F9-52E04B9324C2
facet: 
operation: getWhereList

comment:3 Changed 5 years ago by jburel

Referencing ticket #9944 has changed sprint.

comment:4 Changed 5 years ago by jburel

Referencing ticket #9944 has changed sprint.

comment:5 Changed 5 years ago by jburel

  • Milestone changed from Unscheduled to Metadata
  • Version set to OMERO-5.2.0
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.72687 sec.)

We're Hiring!