Quote from: Megalodon on April 07, 2017, 07:23:16 pm



SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.

Got this error while downloading blockchain after upgrading to this version.



Code: [Select] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: org.h2.jdbc.JdbcSQLException: Error opening database: "Concurrent update" [8000-194]

at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)

at org.h2.message.DbException.get(DbException.java:168)

at org.h2.store.FileLock.getExceptionFatal(FileLock.java:455)

at org.h2.store.FileLock.lockFile(FileLock.java:363)

at org.h2.store.FileLock.lock(FileLock.java:135)

at org.h2.engine.Database.open(Database.java:662)

at org.h2.engine.Database.openDatabase(Database.java:276)

at org.h2.engine.Database.<init>(Database.java:270)

at org.h2.engine.Engine.openSession(Engine.java:64)

at org.h2.engine.Engine.openSession(Engine.java:176)

at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)

at org.h2.engine.Engine.createSession(Engine.java:137)

at org.h2.engine.Engine.createSession(Engine.java:27)

at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)

at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)

at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)

at org.h2.Driver.connect(Driver.java:69)

at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:188)

at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:351)

at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:383)

at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:226)

at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:198)

at nxt.db.BasicDb.getPooledConnection(BasicDb.java:184)

at nxt.db.BasicDb.getConnection(BasicDb.java:178)

at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)

at nxt.db.EntityDbTable.get(EntityDbTable.java:103)

... 16 more

2017-04-07 12:03:52 FINE: Database transaction required 42.973 seconds at height 455636

nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1702)

nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:636)

nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:624)

nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:330)

nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:232)

2017-04-07 12:03:52 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.

java.lang.OutOfMemoryError: GC overhead limit exceeded

java.lang.OutOfMemoryError: GC overhead limit exceeded

2017-04-07 12:03:52 INFO: Shutting down...



You are probably running out of memory "java.lang.OutOfMemoryError: GC overhead limit exceeded" and this is causing a database related error.

Would be nice if you can post the workstation specications.

Please try to increase your memory settings by adding the following command line flag to run.sh: -mx800m



If this doesn't help you may need to download the blockchain on a stronger machine then copy it to this workstation.



Have been running nrs on this VPS ( Ubuntu 14.04 64-BIT, 2G memory) for years without similar problem.

Tried running with -mx800m flag, same problem.

Resolved with fresh blockchain from another machine.