NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

Nope. Behind NAT. Default prefs.

This is something related to Jetty settings. If u don't open web interface then u shouldn't see these warnings.

[bizz]

Nope. Behind NAT. Default prefs.

This is something related to Jetty settings. If u don't open web interface then u shouldn't see these warnings.

OK. I see no problems with client,  14 peers & talking to marked nodes mostly as usual.

[NxtChoice]

Where is the description on the marking of the node? I want to index it for reference.

Thanks.

[laowai80]

CfB,

is blocks.nxt file not immediately updated when new blocks have downloaded? I noticed, the browser shows new blocks already with the new timestamp, but the blocks.nxt file is still a few minutes away, the new blocks sync'ed into the file only a few minutes later. Is this standard operation or again openvz vps node strange behavior?

[brooklynbtc]

Hey Come From Beyond

 I just installed the 0.3.19e on OS X, running great. REAL fast catch up on the blocks. Like 5 seconds.

 It is showing me three orphaned blocks, I'll PM you a screenshot

 The GUI is a little laggy, transactions, peers, blocks buttons take almost that long to work, in fact the whole top bar is lagging. Can't select my address, clicking send has a delay etc

 I'll let it run a while and see what comes out

Thank you. Send me the screenshot plz, I don't understand how u managed to get 3 orphans so quickly.

PS: Interface is lagging coz client sends huge amounts of data to it during blockchain downloading.

PPS: Did u mean 5 minutes?

 Nah I meant 5 secs.. my total was zero when it started, and ripped through updating the blocks and my transactions.

 I did a clean install of 0.3.18 a few minutes earlier and that took about 5 minutes for the block chain.

 

[opticalcarrier]

Hypothetical scenario:

My client is forging, it says I have like 3 minutes before I can generate the next block.  My client crashes, or I hit CTRL-C, or my network dies, but I manage to get it back up in a few secs.

Do I lose my place in line?

[abctc]

v.0.3.19e. Trying to send transaction. After 40 min there is no confirmations at all ..
4 orphaned blocks. Server is on CentOS. 
And there is no new blocks during the last 11 min.

[opticalcarrier]

Im getting this fairly frequently on 0.3.18 (i CRTL-c out and rerun the jar, and it still happens every few mins):

10b8772{SSL-http/1.1}{0.0.0.0:7875}
2013-12-13 11:06:51.271:WARN:oejs.HttpChannel:Scheduler-31607536: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
        at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
3)
        at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$201(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2013-12-13 11:06:51.684:WARN:oejs.ServletHandler:qtp25380518-68: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired
: 5000/5000 ms
        at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:1
01)
        at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
        at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
        at java.io.OutputStream.write(Unknown Source)
        at Nxt.doPost(Unknown Source)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696
)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java
:526)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:143)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav
a:568)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl
er.java:221)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl
er.java:1110)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:
453)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle
r.java:183)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandle
r.java:1044)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:141)
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(Cont
extHandlerCollection.java:199)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerColl
ection.java:109)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper
.java:97)
        at org.eclipse.jetty.server.Server.handle(Server.java:459)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.jav
a:229)
        at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java
:505)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPoo
l.java:607)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool
.java:536)
        at java.lang.Thread.run(Unknown Source)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
        at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
3)
        at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$201(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

[JohnyCrypt]

Version 0.3.19e - https://dl.dropboxusercontent.com/u/67242472/nxt-experimental.zip

This is an experimental version, use it only if u want to help us as a tester.

Added "peerScheme" and "peerPort" in web.xml. This is for migration to HTTPS and different ports.
Added "maxNumberOfConnectedPublicPeers" in web.xml. Ur node will keep connecting to public peers until this number is reached. Previous version does it until total number of public and private peers < 100.
Removed code related to Colored Coins (to prepare source code for review). Now u don't have to copy so many .class files.

Made an attempt to fix blockchain downloading issue related to stuck "Catching up..." message. I removed it from .html files completely, so u won't see it anymore... It's a joke, I also changed a few lines of server code. Now blocks r downloaded faster (2 mins vs 30 mins in previous version) and u don't need to lock/unlock account to unfreeze Recent blocks widget (I hope). I wasn't able to check how the changes handle blockchain reorgs when orphaned blocks appear, that's why this version is experimental. If u can, please, install it and report if u see at least one orphaned block or the blockchain stops growing.

Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network?

[Pablito89]

Forging:

1) I run terminal as normal
2) i go to localhost:7875 and i unlock my "wallet"
3) i close my "wallet" without locking it
4) i let the terminal open
5) what now? how can i know if i got 1 block?
and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?

[abctc]

Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network?

- actually you can use 512 MB VPS even with 0.3.18.

[idev]

Errors on my box

Code:

2013-12-13 11:19:21.345:WARN:oejs.HttpChannel:Scheduler-203777958: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
	at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
	at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
2013-12-13 11:19:26.354:WARN:oejs.ServletHandler:qtp2016627616-33: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
	at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
	at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
	at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Nxt.doPost(Unknown Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:526)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:453)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
	at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
	at org.eclipse.jetty.server.Server.handle(Server.java:459)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
	at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
	at java.lang.Thread.run(Thread.java:724)
Caused by: 
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
	at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
	at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
2013-12-13 12:08:22.804:WARN:oejs.HttpChannel:Scheduler-203777958: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
	at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
	at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
2013-12-13 12:08:22.808:WARN:oejs.ServletHandler:qtp2016627616-34: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
	at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
	at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
	at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Nxt.doPost(Unknown Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:526)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:453)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
	at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
	at org.eclipse.jetty.server.Server.handle(Server.java:459)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
	at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
	at java.lang.Thread.run(Thread.java:724)
Caused by: 
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
	at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
	at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)

[JohnyCrypt]

Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network?

- actually you can use 512 MB VPS even with 0.3.18.

Okay, just checking. I saw the thread about VPS and mem usage at the nextcoin forums and wanted to make sure.Thanks!

[abctc]

5) what now? how can i know if i got 1 block?

- check your account with blockexplorer ("Fee Earned").

and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?

- you will just slightly increase the rate of the orphaned blocks.

[Pablito89]

5) what now? how can i know if i got 1 block?

- check your account with blockexplorer ("Fee Earned").

and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?

- you will just slightly increase the rate of the orphaned blocks.

Thanks
So the terminal won't tell me if i found a block, right?

[abctc]

v.0.3.19e. Trying to send transaction. After 40 min there is no confirmations at all ..

- actually there was confirmations, but they do not appeared in the browser.. albeit that unconfirmed transaction successfully disapeared from the transaction widget after 1 hour (expiration time I have set). After expiration I sent that transaction again, this time from 0.3.19e server on Win7, and later both transaction appeared in the blockchain.

[abctc]

So the terminal won't tell me if i found a block, right?

- you can only see that moment online: your time ticker drops to 3 sec.. 2 sec.. 1 sec.. and you'll see that the block appeared in the widget.

[Pablito89]

So the terminal won't tell me if i found a block, right?

- you can only see that moment online: your time ticker drops to 3 sec.. 2 sec.. 1 sec.. and you'll see that the block appeared in the widget.

Thanks again :p
4 last questions and i'll give you a free biscuit :
1) when will be released an official client (i mean i final version, for all)?
2) how much is the block found reward?
3) do you think this coin will be really used from a large amount of people?
4) why i see my "found block time" changing 1000 times from 4 days to 9 months?

[Come-from-Beyond]

CfB,

is blocks.nxt file not immediately updated when new blocks have downloaded? I noticed, the browser shows new blocks already with the new timestamp, but the blocks.nxt file is still a few minutes away, the new blocks sync'ed into the file only a few minutes later. Is this standard operation or again openvz vps node strange behavior?

It's standard since 0.3.19e. After all blocks r caught soft will dump all stuff to the disk.

[Come-from-Beyond]

v.0.3.19e. Trying to send transaction. After 40 min there is no confirmations at all ..
4 orphaned blocks. Server is on CentOS. 
And there is no new blocks during the last 11 min.

Did u find that transaction? 11 min is normal, forging is a probabilistic process.