[eclipselink-users] OutOfMemoryError with polyglot persistence

[John Hogan <jhogan@xxxxxxxxxxxxx>]

I have a new set of JPA classes for an existing Postgres and MongoDb system.  There is a problem during application startup where it repeatedly dies with an OutOfMemoryError.  I can see both the postgres and mongodb connections created, and there’s a great deal of activity prior to the error.

 

The mongodb I’m connecting to has an extremely large set of data in some of the collections, with at least one having more than 180 million documents.

 

I was wondering if eclipselink might be attempting some type of scan of this data, possibly to validate the schema/class structure at startup.  Has anyone encountered an issue like this, and know of a workaround to prevent it?  Thanks in advance.

 

John Hogan