Page 3 of 3

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Wed Nov 13, 2013 12:22 pm
by manics
If you're switching JDKs it might be worth trying the latest version (Java 7, either Oracle or OpenJDK).

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Wed Nov 13, 2013 2:02 pm
by dpwrussell
manics wrote:If you're switching JDKs it might be worth trying the latest version (Java 7, either Oracle or OpenJDK).


Done. Now using openjdk-7.

Try again please Helio.

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Fri Nov 15, 2013 5:52 pm
by hroque
Well it failed again but this time with an "Failed" import message that then led to a crash when I refreshed.
Douglas this was done around 16h so you would have already restarted the server due to the LDAP no?

Here is the log file.

https://www.dropbox.com/s/5lpe76zc11u7p ... nsight.log

Cheers,
Helio

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Mon Nov 18, 2013 11:46 am
by manics
Thanks Helio.
We'll need to see the server logs from Douglas too.

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Mon Nov 18, 2013 3:12 pm
by dpwrussell
manics wrote:Thanks Helio.
We'll need to see the server logs from Douglas too.


https://www.openmicroscopy.org/qa2/qa/feedback/7717/

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Mon Nov 18, 2013 7:37 pm
by jmoore
Thanks for the logs, Helio. This time there was a successful insertion of the metadata into the DB but it took some 230 minutes during which insight lost its connection.We'll look into a fix for that, but in the mean time if possible you might try kicking off a CLI import of the same file set as workaround.

Again, thanks for all your patience in helping us to track this down!
Cheers,
~Josh

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Mon Nov 18, 2013 8:14 pm
by dpwrussell
230 minutes!? Is there that much metadata being inserted into the database or is it some other aspect of the import which delays the completion past when Insight has timed out. If it's 230 minutes of inserts then either the inserts are crazy slow or we're going to be creating a pretty gigantic database!

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Tue Nov 19, 2013 12:08 pm
by hroque
but in the mean time if possible you might try kicking off a CLI import of the same file set as workaround.


Sorry but what is a CLI import.

Also about the metadata I don't think there is such amount of metadata but there is metadata in every single image file (~70000 files) so it takes forever to go trough all of them and read each single file. I think...

Cheers,
Helio

Re: MessageSize and server OOM (possibly) related problems

PostPosted: Thu Nov 21, 2013 6:53 am
by jmoore
hroque wrote:Sorry but what is a CLI import.


By CLI import I meant using `$OMERO_DIST/bin/omero import` from the server, itself.

Also about the metadata I don't think there is such amount of metadata but there is metadata in every single image file (~70000 files) so it takes forever to go trough all of them and read each single file. I think...


Quite likely. I'm trying to produce a data set of a similar size here to see if I can reproduce.

Regards,
~Josh