OutOfMemory exception when exporting mexico flora
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.
- 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