Project

General

Profile

Actions

bug #10193

open

OutOfMemory exception when exporting mexico flora

Added by Andreas Müller 2 months ago. Updated 28 days ago.

Status:
New
Priority:
New
Assignee:
Category:
cdmadapter
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

When running CDM-l export the OOME occurred after about 85% (see logfile at about line 39.467).

A bit earlier (line 39.370) a deadlock appears in C3P0PooledConnectionPoolManager which might be caused by the memory issue (or is the OOME caused by the deadlock?).

Starting with about 75% the export becomes much slower. Before it is about 2 min per 10% then it becomes 15min per 10%.

After the OOME there come some JDBC exceptions like "Caused by: java.sql.SQLException: Not a navigable ResultSet." which are probably consecutive errors of the OOME.

Solutions:

  • we need to further optimize memory handling during exports e.g. by trying to profile it
  • a first workaround for the efloramex could be to give some more memory to the CDM server instance

Files

mexico-cdm-server-2022-11-30.7z (340 KB) mexico-cdm-server-2022-11-30.7z Andreas Müller, 12/01/2022 12:01 AM
Actions #1

Updated by Andreas Müller 2 months ago

  • Tags changed from export, memory to export, memory, cdmlight

KL, I assigend the ticket to you as you may implement the workaround solution.

If this works we may discuss how to procede.

Actions #2

Updated by Andreas Müller 28 days ago

  • Target version changed from Release 5.35 to Release 5.36
Actions

Also available in: Atom PDF