Migrating a Big Derby embebed database to HSQLDB throw java.lang.OutOfMemoryError: Java heap space










4














I'm trying to migrate a big db from derby to HSQLDB in a Spring Boot service, like 1.5M regs in few tables of 10 columns. I'm checking with VisualVM; byte and char consume a lot of memory. But the biggest delta in time are in the derby classes.



Sometimes the error is thrown here, but other times thrown in other controllers. I don't want to touch all files to add my catchOutofMemory to restart.



Following is a version of my code, the block comment shows the resume of the process:



run()//thread inside static function.
while(keepMigrating)
keepMigrating=Migrate();


private static boolean Migrate(JdbcTemplate derby,JdbcTemplate hsql)
int regs = 100000;
PreparedStatement statement = null;
ResultSet rs = null;
PreparedStatement statementHSQL = null;
try
for (String table : tables) //tables contains all tables to migrate
//check how many registers left asd asign to cant, if cant is 0 the empty is true.
PreparedStatement statementUpd;
while (!empty)
if (trys <= 0) throw new Exception("redo");
//check how many registers left asd asign to cant, if cant is 0 the empty is true and out of bucle and ready to check next table
/*
*Next process resume as:
*fetch data from derby that hasnt been migrated limited by cant
*create a batch to insert in hsql
*create a update for derby
*create a delete in case someting goes wrong
*excecute insert and update, if someting in batch fail delete the entry in migrate table
*reduce regs to get out of migrate method at some ponint.
*/
statement = derby.getDataSource().getConnection().prepareStatement(
MessageFormat.format(select_all_migrate_false_and_fetch_cant,table));
statementUpd = new PreparedStatement[cant];
ArrayList<String> deleteIds = new ArrayList<>();
StringBuilder columnNames = new StringBuilder();
StringBuilder updateSQL = new StringBuilder();
StringBuilder bindVariables = new StringBuilder();
try
ResultSetMetaData meta = rs.getMetaData();
for (int i = 1; i <= meta.getColumnCount(); i++)
if (!meta.getColumnName(i).equals("MIGRATED"))
if (i > 1)
columnNames.append(", ");
bindVariables.append(", ");

columnNames.append(meta.getColumnName(i));
bindVariables.append('?');


String sql = "INSERT INTO " + table.substring(4) + " ("
+ columnNames
+ ") VALUES ("
+ bindVariables
+ ")";
statementHSQL = hsql.getDataSource().getConnection().prepareStatement(sql);
HashMap<String, Object> data = new HashMap<>();
int row = 0;
int lastId = 0;
String columnName;
while (rs.next())
for (int i = 1; i <= meta.getColumnCount(); i++)
columnName = meta.getColumnName(i);
Object o = rs.getObject(i);
statementHSQL.setObject(i, o);
if (columnName.equals(mainColumn))
deleteIds.add(String.valueOf(o));
if (!(meta.getColumnType(i) == 2004)) data.put(columnName, o);
if (columnName.equals(mainColumn)) id = rs.getObject(i);

int c = 1;
String update = MessageFormat.format("INSERT INTO 0M (1M, MIGRATED) VALUES(?, TRUE)",
table.substring(4), mainColumn).replace(""M", "M"");//migrated state is saved in other table
lastId = Integer.valueOf(String.valueOf(id));
statementUpd[row] = derby.getDataSource().getConnection().prepareStatement(update);
statementUpd[row].setObject(1, rs.getObject(mainColumn));
updateSQL = new StringBuilder();
statementHSQL.addBatch();
row += 1;

/*
* Build delete query in case of inserted values in HSQLDB but not updated in DERBY
*/
StringBuilder builder = new StringBuilder();
builder.append("(");
int count = 1;
for (String s : deleteIds)
if (count > 1) builder.append(", ");
builder.append("?");
count++;

builder.append(")");
String str = builder.toString();
String queryDelete = "DELETE FROM " + table.substring(4) + " WHERE " + mainColumn + " IN " + str;
PreparedStatement statementHSQLDel = hsql.getDataSource().getConnection().prepareStatement
(queryDelete);
int c = 1;
for (String s : deleteIds)
statementHSQLDel.setObject(c, s);
c++;

boolean deletes = statementHSQLDel.execute();
statementHSQLDel.close();
try
DatabaseUtils.close(statementHSQLDel);
catch (Exception e)
catchOutOfMemory(e);

int result = statementHSQL.executeBatch();
StringBuilder resultS = new StringBuilder();
int stCounter = 0;
int stCounterInsert = 0;
int stCounterUpdate = 0;
String notarydebug;
for (int i : result)
int upd = 0;
try
if (i == 1) upd = statementUpd[stCounter].executeUpdate();
catch (Exception e)
catchOutOfMemory(e);

stCounterInsert += i;
stCounterUpdate += upd;
resultS.append(",").append(String.valueOf(i)).append("-").append(String.valueOf(upd));
stCounter += 1;

statementHSQL.clearBatch();
try
DatabaseUtils.close(statementHSQL);
catch (Exception e)
catchOutOfMemory(e);

catch (SQLException se)
catchOutOfMemory(se);//otherstuff
catch (Exception e)
catchOutOfMemory(e);

try
DatabaseUtils.close(rs);
DatabaseUtils.close(statement);
catch (Exception e)
catchOutOfMemory(e);

regs=regs-cant;


catch (Exception e)
if (e.getMessage().equals("redo")) return true;//end the loop of regs maximun and get out of method.

return false;//end migration succesfully

private static int catchOutOfMemory(Throwable e)
if (e == null) return 0;
if (e instanceof OutOfMemoryError)
Application.restartBat();
return 1;
else
return catchOutOfMemory(e.getCause());




edit:
So I change as sugested inthe comment to accept a commit, something like this:



Connection hsqlCon;
PrepareStatement hsqlStm;
hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
hsqlStm = hsqlCon.prepareStatement(sql);
hsqlStm.addBatch();
hsqlStm.execute();
hsqlStm.close();
hsqlCon.close();


but i got the same heap memory consumpsion:
enter image description here










share|improve this question























  • What URL are you using for HSQLDB? Are you using the in-memory URL instead of file-based?
    – Mark Rotteveel
    Nov 9 at 14:55










  • bot DERBY and HSQLDB are files
    – Giovanni Leon
    Nov 9 at 17:59










  • The only other problem I see is that you aren't correctly closing connections and statements when you've used them (although your code is hard to follow given its structure), which cause more objects in memory than necessary.
    – Mark Rotteveel
    Nov 9 at 18:03










  • Thanks @Mark, I'll double check one by one again if an statement keep open, I was using null in some points and found one.
    – Giovanni Leon
    Nov 9 at 19:20











  • You need to do this kind of transfer in multiple transactions and commit each transaction. HSQLDB keeps the uncommitted rows in memory, which can run out if the database is large.
    – fredt
    Nov 9 at 22:26















4














I'm trying to migrate a big db from derby to HSQLDB in a Spring Boot service, like 1.5M regs in few tables of 10 columns. I'm checking with VisualVM; byte and char consume a lot of memory. But the biggest delta in time are in the derby classes.



Sometimes the error is thrown here, but other times thrown in other controllers. I don't want to touch all files to add my catchOutofMemory to restart.



Following is a version of my code, the block comment shows the resume of the process:



run()//thread inside static function.
while(keepMigrating)
keepMigrating=Migrate();


private static boolean Migrate(JdbcTemplate derby,JdbcTemplate hsql)
int regs = 100000;
PreparedStatement statement = null;
ResultSet rs = null;
PreparedStatement statementHSQL = null;
try
for (String table : tables) //tables contains all tables to migrate
//check how many registers left asd asign to cant, if cant is 0 the empty is true.
PreparedStatement statementUpd;
while (!empty)
if (trys <= 0) throw new Exception("redo");
//check how many registers left asd asign to cant, if cant is 0 the empty is true and out of bucle and ready to check next table
/*
*Next process resume as:
*fetch data from derby that hasnt been migrated limited by cant
*create a batch to insert in hsql
*create a update for derby
*create a delete in case someting goes wrong
*excecute insert and update, if someting in batch fail delete the entry in migrate table
*reduce regs to get out of migrate method at some ponint.
*/
statement = derby.getDataSource().getConnection().prepareStatement(
MessageFormat.format(select_all_migrate_false_and_fetch_cant,table));
statementUpd = new PreparedStatement[cant];
ArrayList<String> deleteIds = new ArrayList<>();
StringBuilder columnNames = new StringBuilder();
StringBuilder updateSQL = new StringBuilder();
StringBuilder bindVariables = new StringBuilder();
try
ResultSetMetaData meta = rs.getMetaData();
for (int i = 1; i <= meta.getColumnCount(); i++)
if (!meta.getColumnName(i).equals("MIGRATED"))
if (i > 1)
columnNames.append(", ");
bindVariables.append(", ");

columnNames.append(meta.getColumnName(i));
bindVariables.append('?');


String sql = "INSERT INTO " + table.substring(4) + " ("
+ columnNames
+ ") VALUES ("
+ bindVariables
+ ")";
statementHSQL = hsql.getDataSource().getConnection().prepareStatement(sql);
HashMap<String, Object> data = new HashMap<>();
int row = 0;
int lastId = 0;
String columnName;
while (rs.next())
for (int i = 1; i <= meta.getColumnCount(); i++)
columnName = meta.getColumnName(i);
Object o = rs.getObject(i);
statementHSQL.setObject(i, o);
if (columnName.equals(mainColumn))
deleteIds.add(String.valueOf(o));
if (!(meta.getColumnType(i) == 2004)) data.put(columnName, o);
if (columnName.equals(mainColumn)) id = rs.getObject(i);

int c = 1;
String update = MessageFormat.format("INSERT INTO 0M (1M, MIGRATED) VALUES(?, TRUE)",
table.substring(4), mainColumn).replace(""M", "M"");//migrated state is saved in other table
lastId = Integer.valueOf(String.valueOf(id));
statementUpd[row] = derby.getDataSource().getConnection().prepareStatement(update);
statementUpd[row].setObject(1, rs.getObject(mainColumn));
updateSQL = new StringBuilder();
statementHSQL.addBatch();
row += 1;

/*
* Build delete query in case of inserted values in HSQLDB but not updated in DERBY
*/
StringBuilder builder = new StringBuilder();
builder.append("(");
int count = 1;
for (String s : deleteIds)
if (count > 1) builder.append(", ");
builder.append("?");
count++;

builder.append(")");
String str = builder.toString();
String queryDelete = "DELETE FROM " + table.substring(4) + " WHERE " + mainColumn + " IN " + str;
PreparedStatement statementHSQLDel = hsql.getDataSource().getConnection().prepareStatement
(queryDelete);
int c = 1;
for (String s : deleteIds)
statementHSQLDel.setObject(c, s);
c++;

boolean deletes = statementHSQLDel.execute();
statementHSQLDel.close();
try
DatabaseUtils.close(statementHSQLDel);
catch (Exception e)
catchOutOfMemory(e);

int result = statementHSQL.executeBatch();
StringBuilder resultS = new StringBuilder();
int stCounter = 0;
int stCounterInsert = 0;
int stCounterUpdate = 0;
String notarydebug;
for (int i : result)
int upd = 0;
try
if (i == 1) upd = statementUpd[stCounter].executeUpdate();
catch (Exception e)
catchOutOfMemory(e);

stCounterInsert += i;
stCounterUpdate += upd;
resultS.append(",").append(String.valueOf(i)).append("-").append(String.valueOf(upd));
stCounter += 1;

statementHSQL.clearBatch();
try
DatabaseUtils.close(statementHSQL);
catch (Exception e)
catchOutOfMemory(e);

catch (SQLException se)
catchOutOfMemory(se);//otherstuff
catch (Exception e)
catchOutOfMemory(e);

try
DatabaseUtils.close(rs);
DatabaseUtils.close(statement);
catch (Exception e)
catchOutOfMemory(e);

regs=regs-cant;


catch (Exception e)
if (e.getMessage().equals("redo")) return true;//end the loop of regs maximun and get out of method.

return false;//end migration succesfully

private static int catchOutOfMemory(Throwable e)
if (e == null) return 0;
if (e instanceof OutOfMemoryError)
Application.restartBat();
return 1;
else
return catchOutOfMemory(e.getCause());




edit:
So I change as sugested inthe comment to accept a commit, something like this:



Connection hsqlCon;
PrepareStatement hsqlStm;
hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
hsqlStm = hsqlCon.prepareStatement(sql);
hsqlStm.addBatch();
hsqlStm.execute();
hsqlStm.close();
hsqlCon.close();


but i got the same heap memory consumpsion:
enter image description here










share|improve this question























  • What URL are you using for HSQLDB? Are you using the in-memory URL instead of file-based?
    – Mark Rotteveel
    Nov 9 at 14:55










  • bot DERBY and HSQLDB are files
    – Giovanni Leon
    Nov 9 at 17:59










  • The only other problem I see is that you aren't correctly closing connections and statements when you've used them (although your code is hard to follow given its structure), which cause more objects in memory than necessary.
    – Mark Rotteveel
    Nov 9 at 18:03










  • Thanks @Mark, I'll double check one by one again if an statement keep open, I was using null in some points and found one.
    – Giovanni Leon
    Nov 9 at 19:20











  • You need to do this kind of transfer in multiple transactions and commit each transaction. HSQLDB keeps the uncommitted rows in memory, which can run out if the database is large.
    – fredt
    Nov 9 at 22:26













4












4








4







I'm trying to migrate a big db from derby to HSQLDB in a Spring Boot service, like 1.5M regs in few tables of 10 columns. I'm checking with VisualVM; byte and char consume a lot of memory. But the biggest delta in time are in the derby classes.



Sometimes the error is thrown here, but other times thrown in other controllers. I don't want to touch all files to add my catchOutofMemory to restart.



Following is a version of my code, the block comment shows the resume of the process:



run()//thread inside static function.
while(keepMigrating)
keepMigrating=Migrate();


private static boolean Migrate(JdbcTemplate derby,JdbcTemplate hsql)
int regs = 100000;
PreparedStatement statement = null;
ResultSet rs = null;
PreparedStatement statementHSQL = null;
try
for (String table : tables) //tables contains all tables to migrate
//check how many registers left asd asign to cant, if cant is 0 the empty is true.
PreparedStatement statementUpd;
while (!empty)
if (trys <= 0) throw new Exception("redo");
//check how many registers left asd asign to cant, if cant is 0 the empty is true and out of bucle and ready to check next table
/*
*Next process resume as:
*fetch data from derby that hasnt been migrated limited by cant
*create a batch to insert in hsql
*create a update for derby
*create a delete in case someting goes wrong
*excecute insert and update, if someting in batch fail delete the entry in migrate table
*reduce regs to get out of migrate method at some ponint.
*/
statement = derby.getDataSource().getConnection().prepareStatement(
MessageFormat.format(select_all_migrate_false_and_fetch_cant,table));
statementUpd = new PreparedStatement[cant];
ArrayList<String> deleteIds = new ArrayList<>();
StringBuilder columnNames = new StringBuilder();
StringBuilder updateSQL = new StringBuilder();
StringBuilder bindVariables = new StringBuilder();
try
ResultSetMetaData meta = rs.getMetaData();
for (int i = 1; i <= meta.getColumnCount(); i++)
if (!meta.getColumnName(i).equals("MIGRATED"))
if (i > 1)
columnNames.append(", ");
bindVariables.append(", ");

columnNames.append(meta.getColumnName(i));
bindVariables.append('?');


String sql = "INSERT INTO " + table.substring(4) + " ("
+ columnNames
+ ") VALUES ("
+ bindVariables
+ ")";
statementHSQL = hsql.getDataSource().getConnection().prepareStatement(sql);
HashMap<String, Object> data = new HashMap<>();
int row = 0;
int lastId = 0;
String columnName;
while (rs.next())
for (int i = 1; i <= meta.getColumnCount(); i++)
columnName = meta.getColumnName(i);
Object o = rs.getObject(i);
statementHSQL.setObject(i, o);
if (columnName.equals(mainColumn))
deleteIds.add(String.valueOf(o));
if (!(meta.getColumnType(i) == 2004)) data.put(columnName, o);
if (columnName.equals(mainColumn)) id = rs.getObject(i);

int c = 1;
String update = MessageFormat.format("INSERT INTO 0M (1M, MIGRATED) VALUES(?, TRUE)",
table.substring(4), mainColumn).replace(""M", "M"");//migrated state is saved in other table
lastId = Integer.valueOf(String.valueOf(id));
statementUpd[row] = derby.getDataSource().getConnection().prepareStatement(update);
statementUpd[row].setObject(1, rs.getObject(mainColumn));
updateSQL = new StringBuilder();
statementHSQL.addBatch();
row += 1;

/*
* Build delete query in case of inserted values in HSQLDB but not updated in DERBY
*/
StringBuilder builder = new StringBuilder();
builder.append("(");
int count = 1;
for (String s : deleteIds)
if (count > 1) builder.append(", ");
builder.append("?");
count++;

builder.append(")");
String str = builder.toString();
String queryDelete = "DELETE FROM " + table.substring(4) + " WHERE " + mainColumn + " IN " + str;
PreparedStatement statementHSQLDel = hsql.getDataSource().getConnection().prepareStatement
(queryDelete);
int c = 1;
for (String s : deleteIds)
statementHSQLDel.setObject(c, s);
c++;

boolean deletes = statementHSQLDel.execute();
statementHSQLDel.close();
try
DatabaseUtils.close(statementHSQLDel);
catch (Exception e)
catchOutOfMemory(e);

int result = statementHSQL.executeBatch();
StringBuilder resultS = new StringBuilder();
int stCounter = 0;
int stCounterInsert = 0;
int stCounterUpdate = 0;
String notarydebug;
for (int i : result)
int upd = 0;
try
if (i == 1) upd = statementUpd[stCounter].executeUpdate();
catch (Exception e)
catchOutOfMemory(e);

stCounterInsert += i;
stCounterUpdate += upd;
resultS.append(",").append(String.valueOf(i)).append("-").append(String.valueOf(upd));
stCounter += 1;

statementHSQL.clearBatch();
try
DatabaseUtils.close(statementHSQL);
catch (Exception e)
catchOutOfMemory(e);

catch (SQLException se)
catchOutOfMemory(se);//otherstuff
catch (Exception e)
catchOutOfMemory(e);

try
DatabaseUtils.close(rs);
DatabaseUtils.close(statement);
catch (Exception e)
catchOutOfMemory(e);

regs=regs-cant;


catch (Exception e)
if (e.getMessage().equals("redo")) return true;//end the loop of regs maximun and get out of method.

return false;//end migration succesfully

private static int catchOutOfMemory(Throwable e)
if (e == null) return 0;
if (e instanceof OutOfMemoryError)
Application.restartBat();
return 1;
else
return catchOutOfMemory(e.getCause());




edit:
So I change as sugested inthe comment to accept a commit, something like this:



Connection hsqlCon;
PrepareStatement hsqlStm;
hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
hsqlStm = hsqlCon.prepareStatement(sql);
hsqlStm.addBatch();
hsqlStm.execute();
hsqlStm.close();
hsqlCon.close();


but i got the same heap memory consumpsion:
enter image description here










share|improve this question















I'm trying to migrate a big db from derby to HSQLDB in a Spring Boot service, like 1.5M regs in few tables of 10 columns. I'm checking with VisualVM; byte and char consume a lot of memory. But the biggest delta in time are in the derby classes.



Sometimes the error is thrown here, but other times thrown in other controllers. I don't want to touch all files to add my catchOutofMemory to restart.



Following is a version of my code, the block comment shows the resume of the process:



run()//thread inside static function.
while(keepMigrating)
keepMigrating=Migrate();


private static boolean Migrate(JdbcTemplate derby,JdbcTemplate hsql)
int regs = 100000;
PreparedStatement statement = null;
ResultSet rs = null;
PreparedStatement statementHSQL = null;
try
for (String table : tables) //tables contains all tables to migrate
//check how many registers left asd asign to cant, if cant is 0 the empty is true.
PreparedStatement statementUpd;
while (!empty)
if (trys <= 0) throw new Exception("redo");
//check how many registers left asd asign to cant, if cant is 0 the empty is true and out of bucle and ready to check next table
/*
*Next process resume as:
*fetch data from derby that hasnt been migrated limited by cant
*create a batch to insert in hsql
*create a update for derby
*create a delete in case someting goes wrong
*excecute insert and update, if someting in batch fail delete the entry in migrate table
*reduce regs to get out of migrate method at some ponint.
*/
statement = derby.getDataSource().getConnection().prepareStatement(
MessageFormat.format(select_all_migrate_false_and_fetch_cant,table));
statementUpd = new PreparedStatement[cant];
ArrayList<String> deleteIds = new ArrayList<>();
StringBuilder columnNames = new StringBuilder();
StringBuilder updateSQL = new StringBuilder();
StringBuilder bindVariables = new StringBuilder();
try
ResultSetMetaData meta = rs.getMetaData();
for (int i = 1; i <= meta.getColumnCount(); i++)
if (!meta.getColumnName(i).equals("MIGRATED"))
if (i > 1)
columnNames.append(", ");
bindVariables.append(", ");

columnNames.append(meta.getColumnName(i));
bindVariables.append('?');


String sql = "INSERT INTO " + table.substring(4) + " ("
+ columnNames
+ ") VALUES ("
+ bindVariables
+ ")";
statementHSQL = hsql.getDataSource().getConnection().prepareStatement(sql);
HashMap<String, Object> data = new HashMap<>();
int row = 0;
int lastId = 0;
String columnName;
while (rs.next())
for (int i = 1; i <= meta.getColumnCount(); i++)
columnName = meta.getColumnName(i);
Object o = rs.getObject(i);
statementHSQL.setObject(i, o);
if (columnName.equals(mainColumn))
deleteIds.add(String.valueOf(o));
if (!(meta.getColumnType(i) == 2004)) data.put(columnName, o);
if (columnName.equals(mainColumn)) id = rs.getObject(i);

int c = 1;
String update = MessageFormat.format("INSERT INTO 0M (1M, MIGRATED) VALUES(?, TRUE)",
table.substring(4), mainColumn).replace(""M", "M"");//migrated state is saved in other table
lastId = Integer.valueOf(String.valueOf(id));
statementUpd[row] = derby.getDataSource().getConnection().prepareStatement(update);
statementUpd[row].setObject(1, rs.getObject(mainColumn));
updateSQL = new StringBuilder();
statementHSQL.addBatch();
row += 1;

/*
* Build delete query in case of inserted values in HSQLDB but not updated in DERBY
*/
StringBuilder builder = new StringBuilder();
builder.append("(");
int count = 1;
for (String s : deleteIds)
if (count > 1) builder.append(", ");
builder.append("?");
count++;

builder.append(")");
String str = builder.toString();
String queryDelete = "DELETE FROM " + table.substring(4) + " WHERE " + mainColumn + " IN " + str;
PreparedStatement statementHSQLDel = hsql.getDataSource().getConnection().prepareStatement
(queryDelete);
int c = 1;
for (String s : deleteIds)
statementHSQLDel.setObject(c, s);
c++;

boolean deletes = statementHSQLDel.execute();
statementHSQLDel.close();
try
DatabaseUtils.close(statementHSQLDel);
catch (Exception e)
catchOutOfMemory(e);

int result = statementHSQL.executeBatch();
StringBuilder resultS = new StringBuilder();
int stCounter = 0;
int stCounterInsert = 0;
int stCounterUpdate = 0;
String notarydebug;
for (int i : result)
int upd = 0;
try
if (i == 1) upd = statementUpd[stCounter].executeUpdate();
catch (Exception e)
catchOutOfMemory(e);

stCounterInsert += i;
stCounterUpdate += upd;
resultS.append(",").append(String.valueOf(i)).append("-").append(String.valueOf(upd));
stCounter += 1;

statementHSQL.clearBatch();
try
DatabaseUtils.close(statementHSQL);
catch (Exception e)
catchOutOfMemory(e);

catch (SQLException se)
catchOutOfMemory(se);//otherstuff
catch (Exception e)
catchOutOfMemory(e);

try
DatabaseUtils.close(rs);
DatabaseUtils.close(statement);
catch (Exception e)
catchOutOfMemory(e);

regs=regs-cant;


catch (Exception e)
if (e.getMessage().equals("redo")) return true;//end the loop of regs maximun and get out of method.

return false;//end migration succesfully

private static int catchOutOfMemory(Throwable e)
if (e == null) return 0;
if (e instanceof OutOfMemoryError)
Application.restartBat();
return 1;
else
return catchOutOfMemory(e.getCause());




edit:
So I change as sugested inthe comment to accept a commit, something like this:



Connection hsqlCon;
PrepareStatement hsqlStm;
hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
hsqlStm = hsqlCon.prepareStatement(sql);
hsqlStm.addBatch();
hsqlStm.execute();
hsqlStm.close();
hsqlCon.close();


but i got the same heap memory consumpsion:
enter image description here







java spring-boot database-migration derby hsqldb






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 26 at 15:53

























asked Nov 8 at 1:38









Giovanni Leon

212




212











  • What URL are you using for HSQLDB? Are you using the in-memory URL instead of file-based?
    – Mark Rotteveel
    Nov 9 at 14:55










  • bot DERBY and HSQLDB are files
    – Giovanni Leon
    Nov 9 at 17:59










  • The only other problem I see is that you aren't correctly closing connections and statements when you've used them (although your code is hard to follow given its structure), which cause more objects in memory than necessary.
    – Mark Rotteveel
    Nov 9 at 18:03










  • Thanks @Mark, I'll double check one by one again if an statement keep open, I was using null in some points and found one.
    – Giovanni Leon
    Nov 9 at 19:20











  • You need to do this kind of transfer in multiple transactions and commit each transaction. HSQLDB keeps the uncommitted rows in memory, which can run out if the database is large.
    – fredt
    Nov 9 at 22:26
















  • What URL are you using for HSQLDB? Are you using the in-memory URL instead of file-based?
    – Mark Rotteveel
    Nov 9 at 14:55










  • bot DERBY and HSQLDB are files
    – Giovanni Leon
    Nov 9 at 17:59










  • The only other problem I see is that you aren't correctly closing connections and statements when you've used them (although your code is hard to follow given its structure), which cause more objects in memory than necessary.
    – Mark Rotteveel
    Nov 9 at 18:03










  • Thanks @Mark, I'll double check one by one again if an statement keep open, I was using null in some points and found one.
    – Giovanni Leon
    Nov 9 at 19:20











  • You need to do this kind of transfer in multiple transactions and commit each transaction. HSQLDB keeps the uncommitted rows in memory, which can run out if the database is large.
    – fredt
    Nov 9 at 22:26















What URL are you using for HSQLDB? Are you using the in-memory URL instead of file-based?
– Mark Rotteveel
Nov 9 at 14:55




What URL are you using for HSQLDB? Are you using the in-memory URL instead of file-based?
– Mark Rotteveel
Nov 9 at 14:55












bot DERBY and HSQLDB are files
– Giovanni Leon
Nov 9 at 17:59




bot DERBY and HSQLDB are files
– Giovanni Leon
Nov 9 at 17:59












The only other problem I see is that you aren't correctly closing connections and statements when you've used them (although your code is hard to follow given its structure), which cause more objects in memory than necessary.
– Mark Rotteveel
Nov 9 at 18:03




The only other problem I see is that you aren't correctly closing connections and statements when you've used them (although your code is hard to follow given its structure), which cause more objects in memory than necessary.
– Mark Rotteveel
Nov 9 at 18:03












Thanks @Mark, I'll double check one by one again if an statement keep open, I was using null in some points and found one.
– Giovanni Leon
Nov 9 at 19:20





Thanks @Mark, I'll double check one by one again if an statement keep open, I was using null in some points and found one.
– Giovanni Leon
Nov 9 at 19:20













You need to do this kind of transfer in multiple transactions and commit each transaction. HSQLDB keeps the uncommitted rows in memory, which can run out if the database is large.
– fredt
Nov 9 at 22:26




You need to do this kind of transfer in multiple transactions and commit each transaction. HSQLDB keeps the uncommitted rows in memory, which can run out if the database is large.
– fredt
Nov 9 at 22:26












1 Answer
1






active

oldest

votes


















0














The type of table in HSQLDB is not clear from the supplied code. You must use this statement once for each table, to make sure the table data is stored in the finename.data file:



SET TABLE tableName TYPE CACHED


The reported sequence of batch INSERT is not correct. Use this sequence:



Connection hsqlCon;
PrepareStatement hsqlStm;
hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
hsqlStm = hsqlCon.prepareStatement(sql);

// repeat this block until all is finished
// repeat for 1000 rows
hsqlStm.addBatch();

hsqlStm.executeBatch(); // after every 1000 rows


hsqlStm.close();
hsqlCon.close();





share|improve this answer






















    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53200371%2fmigrating-a-big-derby-embebed-database-to-hsqldb-throw-java-lang-outofmemoryerro%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The type of table in HSQLDB is not clear from the supplied code. You must use this statement once for each table, to make sure the table data is stored in the finename.data file:



    SET TABLE tableName TYPE CACHED


    The reported sequence of batch INSERT is not correct. Use this sequence:



    Connection hsqlCon;
    PrepareStatement hsqlStm;
    hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
    hsqlStm = hsqlCon.prepareStatement(sql);

    // repeat this block until all is finished
    // repeat for 1000 rows
    hsqlStm.addBatch();

    hsqlStm.executeBatch(); // after every 1000 rows


    hsqlStm.close();
    hsqlCon.close();





    share|improve this answer



























      0














      The type of table in HSQLDB is not clear from the supplied code. You must use this statement once for each table, to make sure the table data is stored in the finename.data file:



      SET TABLE tableName TYPE CACHED


      The reported sequence of batch INSERT is not correct. Use this sequence:



      Connection hsqlCon;
      PrepareStatement hsqlStm;
      hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
      hsqlStm = hsqlCon.prepareStatement(sql);

      // repeat this block until all is finished
      // repeat for 1000 rows
      hsqlStm.addBatch();

      hsqlStm.executeBatch(); // after every 1000 rows


      hsqlStm.close();
      hsqlCon.close();





      share|improve this answer

























        0












        0








        0






        The type of table in HSQLDB is not clear from the supplied code. You must use this statement once for each table, to make sure the table data is stored in the finename.data file:



        SET TABLE tableName TYPE CACHED


        The reported sequence of batch INSERT is not correct. Use this sequence:



        Connection hsqlCon;
        PrepareStatement hsqlStm;
        hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
        hsqlStm = hsqlCon.prepareStatement(sql);

        // repeat this block until all is finished
        // repeat for 1000 rows
        hsqlStm.addBatch();

        hsqlStm.executeBatch(); // after every 1000 rows


        hsqlStm.close();
        hsqlCon.close();





        share|improve this answer














        The type of table in HSQLDB is not clear from the supplied code. You must use this statement once for each table, to make sure the table data is stored in the finename.data file:



        SET TABLE tableName TYPE CACHED


        The reported sequence of batch INSERT is not correct. Use this sequence:



        Connection hsqlCon;
        PrepareStatement hsqlStm;
        hsqlCon = JdbcHSQLDB.getDataSource().getConnection();
        hsqlStm = hsqlCon.prepareStatement(sql);

        // repeat this block until all is finished
        // repeat for 1000 rows
        hsqlStm.addBatch();

        hsqlStm.executeBatch(); // after every 1000 rows


        hsqlStm.close();
        hsqlCon.close();






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 8 at 15:48

























        answered Dec 8 at 12:47









        fredt

        19.4k32952




        19.4k32952



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53200371%2fmigrating-a-big-derby-embebed-database-to-hsqldb-throw-java-lang-outofmemoryerro%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

            Crossroads (UK TV series)

            ữḛḳṊẴ ẋ,Ẩṙ,ỹḛẪẠứụỿṞṦ,Ṉẍừ,ứ Ị,Ḵ,ṏ ṇỪḎḰṰọửḊ ṾḨḮữẑỶṑỗḮṣṉẃ Ữẩụ,ṓ,ḹẕḪḫỞṿḭ ỒṱṨẁṋṜ ḅẈ ṉ ứṀḱṑỒḵ,ḏ,ḊḖỹẊ Ẻḷổ,ṥ ẔḲẪụḣể Ṱ ḭỏựẶ Ồ Ṩ,ẂḿṡḾồ ỗṗṡịṞẤḵṽẃ ṸḒẄẘ,ủẞẵṦṟầṓế