[ome-users] (no subject)

Josh Moore josh at glencoesoftware.com
Mon Aug 30 15:17:15 BST 2010

Thanks, Bram. The section of log did point to a possible bug in which far too many sessions might be created. I've opened a ticket at:


In the mean time, you might try increasing the memory of your Blitz process by changing:





On Aug 30, 2010, at 2:52 PM, <b.gerritsen at nki.nl> wrote:

> Hi Josh,
> No, I didn't change any defaults. Except for a couple pertaining to db name, password, and location of the omero data dir. However I did patch the PixelsProcessor.java to fix the platename and plate description (part of the code of my patch is included in ticket #2648).
> I have included everything of the log up until the first DatabaseBusy exception. Hopefully that is of help.
> Kind Regards,
> Bram
> ________________________________________
> From: Josh Moore [josh at glencoesoftware.com]
> Sent: Monday, August 30, 2010 2:46 PM
> To: Bram Gerritsen
> Cc: OME Users
> Subject: Re: [ome-users] (no subject)
> On Aug 30, 2010, at 2:39 PM, <b.gerritsen at nki.nl> wrote:
>> Hi Josh,
>> I'm really sorry, but I shut down the server just before reading your reply :(
> No worries, Bram. The next time it happens, though, the stack dump would be quite useful.
>> I am attempting to reproduce the exception, but haven't been able to yet. What I did do just before shutting down was temporarily bump up the debug level in dist/etc/log4j.xml and tried to log in again. See attachment with the last section of the log.
> Unfortunately, it's the logs from before the first DatabaseBusy exceptions start that are the most telling. In general, these exceptions can occur under very high-load, and a server restart is almost always needed. Have you increased the memory for your server beyond the default?
>> Kind Regards,
>> Bram
> Cheers,
> ~Josh.
> <first_part.log.gz>

More information about the ome-users mailing list