[BUG] Groovy evaluation error: java.util.concurrent.ExecutionException

[ffazendeiro]

Hi, We are implementing more non GUI tests and using much more properties getFromGroovy and noticed for performance issues with Cerberus application (and eventually a crash). Seems to be a metaspace memory usage with the getFromGroovy and we get the following error: Groovy evaluation error: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Metaspace

We did some tests and we noticed that the getFromGroovy consumes lots of resources that are never released:

• First arrow: Massive tests using services (REST - Get, Put, ...) Small increase but stable.
• Second arrow: Massive tests that have a Groovy property. Instant increase on the metaspace and number os classes.
• Third arrow: Stopped tests having groovy and started again the services tests. Seems the metaspace/classes are not released.

With a massive use of groovy property during the day, metaspace with reach the maximum and will start returning the error. Instances will start to struggle and are not able to handle the load leading to the fail of the application:

Can you please double check Groovy implementation? Thanks in advance.

Version tested: Cerberus4.12-SNAPSHOT-1583 (but this could be present in earlier release as it was never massively tested)

[mbessa]

Just to add, the analysis reveal memory usage behavior with glassfish and tomcat is the same.

[ittaLaRedoute]

Hello @vertigo17 , any news on that ?

[vertigo17]

I upgraded to latest groovy. Can you please test ?

[vertigo17]

Do you still have the behavior following Groovy upgrade ?

[vertigo17]

Do you still have the behavior following Groovy upgrade ?