This forum has been archived. Please start a new discussion on GitHub.

[3.3.1] OutOfMemory in client when slice definition modified

The addition of an object to our EventContext type definition:
diff --git a/components/blitz/resources/omero/ b/components/blitz/resources/omero/
index bd84c53..9ccd744 100644
--- a/components/blitz/resources/omero/
+++ b/components/blitz/resources/omero/
@@ -40,6 +40,7 @@ module omero {
       LongList memberOfGroups;
       LongList leaderOfGroups;
       omero::model::Permissions umask;
+      omero::model::Permissions groupPermissions;

lead to the following failure in a client which had not yet updated its jar:
Data Retrieval Failure: java.lang.OutOfMemoryError: Java heap space
    at IceInternal.BasicStream.readString(
    at IceInternal.BasicStream.readTypeId(
    at Ice.ObjectImpl.__read(
    at omero.sys.EventContext.__read(
    at IceInternal.BasicStream.readObject(
    at IceInternal.BasicStream.readPendingObjects(
    at omero.api._IAdminDelM.getEventContext(



  • bernard
    bernard Jupiter, FL
    Hi Josh,

    If you set a large Ice.MessageSizeMax for your application, this is not unexpected.


    Best regards,
  • We do increase MessageSizeMax on all our clients & servers, but only to 64MB. Would this be enough to cause an OOM in such a situtation? I ask because this is the among the first method in our handshake as well as the keepalive ping method. Having it fail due to a stale jar is certainly unfortunate.

  • benoit
    benoit Rennes, France
    Hi Josh,

    After having a closer look, I think it's a bug in Ice for Java. Thanks for the report, we will fix this for 3.4.

  • Thanks, guys.

    And, of course, I meant "the addition led to ... " :)