CRITICAL - ActionManager: java.lang.OutOfMemoryError: GC overhead limit exceeded

0
Hi Team, We are facing issue with the java.lang.OutOfMemoryError: GC overhead limit exceeded. PFB logs for more details. 2016-01-14 00:28:52.949 WARNING - ConnectionBus: Database connections: 50 active, 0 idle. 2016-01-14 00:28:52.949 ERROR - ConnectionBus: Opening JDBC connection to dbcloud041-scan.db.gen.local:1521 failed with SQLState: null Error code: 0 Message: Cannot get a connection, pool error Timeout waiting for idle object Retrying...(3/4) 2016-01-14 00:28:52.949 CRITICAL - ActionManager: Error in scheduled event 'SEProcessTopology4GStart' 2016-01-14 00:28:52.949 CRITICAL - ActionManager: java.lang.OutOfMemoryError: GC overhead limit exceeded 2016-01-14 00:28:52.949 WARNING - Caching: Fetching object from cache for id '[MendixIdentifier:: id=41658296553227972 objectType=AuditTrail.Log entityID=148]' in session '0d3d08de-230e-43d1-a5de-9a38bc9d5ada' timed out. 2016-01-14 00:28:52.949 WARNING - Caching: Fetching object from cache for id '[MendixIdentifier:: id=41658296553779578 objectType=AuditTrail.Log entityID=148]' in session '0d3d08de-230e-43d1-a5de-9a38bc9d5ada' timed out. 2016-01-14 00:28:52.949 WARNING - Caching: Getting MxIds from cache for session 'c178acf6-e9cd-430b-b7f9-923119a42bf2' timed out. 2016-01-14 00:28:52.949 WARNING - Caching: Fetching object from cache for id '[MendixIdentifier:: id=41658296553895110 objectType=AuditTrail.Log entityID=148]' in session '0d3d08de-230e-43d1-a5de-9a38bc9d5ada' timed out. 2016-01-14 00:28:52.949 WARNING - Caching: Fetching object from cache for id '[MendixIdentifier:: id=41658296553428360 objectType=AuditTrail.Log entityID=148]' in session '0d3d08de-230e-43d1-a5de-9a38bc9d5ada' timed out. 2016-01-14 00:28:52.949 ERROR - Webservices: Exception occurred while processing webservice request 2016-01-14 00:28:52.949 ERROR - Webservices: com.mendix.core.CoreRuntimeException: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.User[Name='TieUser']"}', all database changes executed by this action were rolled back at hC.b(SourceFile:218) Caused by: com.mendix.core.CoreRuntimeException: Exception occurred in action '{"amount":-1,"sort":{},"offset":-1,"type":"RetrieveXPathAction","depth":0,"xpath":"//System.User[Name='TieUser']"}', all database changes executed by this action were rolled back at com.mendix.core.actionmanagement.CoreAction.c(SourceFile:515) Caused by: l: An exception has occurred for the following request(s): fu (depth = 0): //System.User[Name='TieUser'] at x.a(SourceFile:49) Caused by: l: Exception occurred while retrieving data. (SQL State: null, Error Code: 0) Detail Message: java.util.NoSuchElementException: Timeout waiting for idle object at H.a(SourceFile:1398) Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
asked
3 answers
3

It seems like this scheduled event is using to many objects at once. You should optimize this scheduled event microflow. One of the things you can do is make use of batches. This example still applies. Play with the batch size and don't forget to clear the list after every iteration/loop since this forces the Business Server memory to be cleaned.

I hope this helps.

answered
1

The maxed database connections could be a result of to little memory for the db node. Check your monitor to see if this is the case.

Regards,

Ronald

answered
0

For the errors being thrown I see that you maxed out on the database connections, default you have 50 connections. You could check what processes are running in addition to the scheduled event.

answered