this strange error appears quite regular after switching from toplink to
eclipselink. Unfortunatly it's not possible to reproduce in a unit test,
but around every third time I start our application I get this here:
I stepped through the eclipselink sourcecode and I really discovered, that
a xml file is written to hard disk only to clone an object when
TABLE_PER_CLASS inheritance is used.
This is the method:
org.eclipse.persistence.internal.jpa.metadata.xml.XMLEntityMappings.reloadXMLEntityMappingsObject(XMLEntityMappings)
I'm working with a huge legacy system, and maybe it's a bug on my side,
but why you don't use a memorystream or something comparable fast.