Qortal Core - Main Code Repository Decentralized Data Network - Blockchain - TRUE Cross-Chain Trading - Application and Website Hosting - Much More - Qortal is the future internet infrastructure for the global digital world.

Go to file

catbref fa0b7615a6 Fixing peer disconnections due to slow processing & Transaction expiry Transaction expiry wasn't happening. Use NTP.getTime to check whether transactions have expired. Also reject expired transactions when trying to add them to unconfirmed pool. Sometimes producing a task took way too long, causing massive spikes in the number of threads and peer disconnections. This is down to a repository pool exhaustion, so RepositoryManager.getRepository() would block (for up to 5 minutes). The key method at fault was Network.getConnectablePeer(). Various fixes: NetworkProcessor's executor now reaps old threads after only 10 seconds instead of the usual 60 seconds. Change logging in Network to help diagnose disconnection and repository issues. RepositoryManager now has a tryRepository() call that is non-blocking and returns null if repository pool is exhausted. Repository pool size increased from default (10) to 100. Pruning peers is now opportunistic, using tryRepository(), and returns early if repository pool is exhausted. getConnectablePeer() is now opportunistic, using tryRepository(), and returns null (no peer candidate for connection) if repository pool is exhausted. Merging peers is not opportunistic, using tryRepository(). Peer ping interval increased from 8s to 20s. HSQLDBRepositoryFactory now logs when getConnection() takes over 1000ms. Added more trace-level logging to ExecuteProduceConsume to highlight slow produceTask() calls.		2019-08-13 09:54:35 +01:00
lib/org/ciyam/at	Bump HSQLDB from svn r5970 to release v2.5.0	2019-08-02 13:05:18 +01:00
src	Fixing peer disconnections due to slow processing & Transaction expiry	2019-08-13 09:54:35 +01:00
.gitignore	Added settings.json to gitignore	2019-08-02 14:07:12 +01:00
log4j2.properties	new log4j2.properties	2019-07-18 18:31:58 +01:00
pom.xml	Improved detection of inaccurate system clock & nagging.	2019-08-13 09:14:07 +01:00
README.md	Unit test fixes + initial CIYAM AT integration	2018-10-04 14:38:59 +01:00

README.md

Qora2

To use:

Use maven to fetch dependencies.
Build project.
Build v1feeder.jar as a fatjar using src/v1feeder.java as the main class
Fire up an old-gen Qora node.
Use v1feeder.jar to migrate old Qora blocks to DB:

java -jar v1feeder.jar qora-v1-node-ip

You should now be able to run all the JUnit tests.

You can also examine the migrated database using HSQLDB's "sqltool".

It's a good idea to install "rlwrap" (ReadLine wrapper) too as sqltool doesn't support command history/editing!

Typical command line for sqltool would be:

rlwrap java -cp ${HSQLDB_JAR}:${SQLTOOL_JAR} org.hsqldb.cmdline.SqlTool --rcFile=${SQLTOOL_RC} qora

${HSQLDB_JAR} contains pathname to where Maven downloaded hsqldb, typically ${HOME}/.m2/repository/org/hsqldb/hsqldb/2.4.0/hsqldb-2.4.0.jar, but for now lib/org/hsqldb/hsqldb/r5836/hsqldb-r5836.jar

${SQLTOOL_JAR} contains pathname to where Maven downloaded sqltool, typically ${HOME}/.m2/repository/org/hsqldb/sqltool/2.4.1/sqltool-2.4.1.jar

${SQLTOOL_RC} contains pathname to a text file describing Qora2 database, e.g. ${HOME}/.sqltool.rc, with contents like:

urlid qora
url jdbc:hsqldb:file:db/qora
username SA
password

urlid qora-test
url jdbc:hsqldb:file:db/test
username SA
password

You could change the line url jdbc:hsqldb:file:db/test to use a full pathname for easier use.

Another idea is to assign a shell alias in your .bashrc like:

export HSQLDB_JAR=${HOME}/.m2/repository/org/hsqldb/hsqldb/2.4.0/hsqldb-2.4.0.jar
export SQLTOOL_JAR=${HOME}/.m2/repository/org/hsqldb/sqltool/2.4.1/sqltool-2.4.1.jar
alias sqltool='rlwrap java -cp ${HSQLDB_JAR}:${SQLTOOL_JAR} org.hsqldb.cmdline.SqlTool --rcFile=${SQLTOOL_RC}'

So you can simply type: sqltool qora-test

Don't forget to use SHUTDOWN; before exiting sqltool so that database files are closed cleanly.