We’ve encountered a very unusual exception which seemed to be related to a specific entity. The exception started with the deployment of a specific release and was gone after the following release was deployed. None of the changes in both releases seemed to correlate to the exception and/or the entity. All other functionalities of the application were working as expected, including lots of Hibernate-related logic. We were not able to reproduce this, but looking at AbstractRowReader it seems that the NullPointerException can only occur if it has already been initialized the wrong way with a null value in entityReferenceInitializers. Do you have an idea what has happened here? Stack trace:
|