New build of the mac client which includes the 0.3.20 release:
https://copy.com/YL2vVHK7vXza
And I'm happy to say that this seems to solve the memory issue that plagued earlier versions, at least on my system. (It appears to have been related to the 0.3.19 experimental build).
If other users can test this as well and report back. There should be no need to force quit the app the first time any more.
More info here: https://nextcoin.org/index.php/topic,708.msg5475.html
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2374. (Read 2761626 times)
Code:
2013-12-16 20:44:53.604:WARN:oejh.HttpParser:qtp180753500-18: badMessage: 400 Illegal character for HttpChannelOverHttp@6b073ba0{r=0,a=IDLE,uri=-}
2013-12-16 20:45:49.860:WARN:oejh.HttpParser:qtp180753500-19: badMessage: 400 Illegal character for HttpChannelOverHttp@13460a5b{r=0,a=IDLE,uri=-}
2013-12-16 20:52:50.693:WARN:oejh.HttpParser:qtp180753500-14: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@2d0aa021{r=5,a=IDLE,uri=-}
Any Jetty expert there?
You can talk to Jetty's coder @ irc.freenode.net #jetty his nickname is : joakime just a minute ago he helped me a lot he is a good guy.
This is from the last version.
Code:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:52.462:WARN:oejut.QueuedThreadPool:qtp2016627616-155:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:21.824:WARN:oejut.QueuedThreadPool:qtp2016627616-151:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:10:35.829:WARN:oejut.QueuedThreadPool:qtp2016627616-147:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:47.705:WARN:oejut.QueuedThreadPool:qtp2016627616-143:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:00.107:WARN:oejut.QueuedThreadPool:qtp2016627616-139:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:56.608:WARN:oejut.QueuedThreadPool:qtp2016627616-138:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:54.793:WARN:oejut.QueuedThreadPool:qtp2016627616-93:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:50.928:WARN:oejh.HttpParser:qtp2016627616-90: badMessage: 400 No Host for HttpChannelOverHttp@4be6e4c7{r=0,a=IDLE,uri=-}
2013-12-16 16:14:52.293:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:54.584:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
Exception in thread "qtp2016627616-90" java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:16:55.461:WARN:oeji.SelectorManager:qtp2016627616-12-selector-ServerConnectorManager@6f9bc97/0: Exception while notifying connection SslConnection@2863cb73{NEED_UNWRAP,eio=-1/-1,di=-1} -> HttpConnection@2fc1ffbc{IDLE}
java.lang.OutOfMemoryError: Java heap space
Try to set heap size:
Code:
java -Xms256m -Xmx1024m -jar start.jar
Cheers, I've now updated my public node to the latest version and set pushThreshold and pullThreshold parameters to 1.
Starting to see these on a few nodes:
Code:
2013-12-16 21:13:54.744:WARN:oejh.HttpParser:qtp180753500-18: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@757e9b8e{r=1,a=IDLE,uri=-}
Have u ran 0.3.19e on these nodes? I changed nothing that could lead to "too much data after closed for HttpChannelOverHttp".
Restarted all 10 - no errors, but only 3 are connecting.
Not particularly optimistic on Bitcoin future: Google official
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
Maybe Nxt is a Google's project
Hm, let's ask him.
Mem 2.40 GB
Is it memory consumed by java.exe process?
It returned to normal after restarting the client.
Pin
Not particularly optimistic on Bitcoin future: Google official
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
Maybe Nxt is a Google's project
Hm, let's ask him.
Not particularly optimistic on Bitcoin future: Google official
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
Maybe Nxt is a Google's project
Starting to see these on a few nodes:
Code:
2013-12-16 21:13:54.744:WARN:oejh.HttpParser:qtp180753500-18: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@757e9b8e{r=1,a=IDLE,uri=-}
Have u ran 0.3.19e on these nodes? I changed nothing that could lead to "too much data after closed for HttpChannelOverHttp".
Yes, but my deploy system creates a new nxt/ directory so it's using everything out of the new zip file. I can redeploy and restart everything to be sure.
Not particularly optimistic on Bitcoin future: Google official
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt
Maybe Nxt is a Google's project
Mem 2.40 GB
Is it memory consumed by java.exe process?
Not particularly optimistic on Bitcoin future: Google official
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt?
"I think something like this technology will take hold in the future but I am not particularly optimistic about bitcoin because it suffers from being the first in the area." Google Chief Economist Hal Varian
Maybe he's already heard of Nxt?
Starting to see these on a few nodes:
Code:
2013-12-16 21:13:54.744:WARN:oejh.HttpParser:qtp180753500-18: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@757e9b8e{r=1,a=IDLE,uri=-}
Have u ran 0.3.19e on these nodes? I changed nothing that could lead to "too much data after closed for HttpChannelOverHttp".
This is from the last version.
Code:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:52.462:WARN:oejut.QueuedThreadPool:qtp2016627616-155:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:21.824:WARN:oejut.QueuedThreadPool:qtp2016627616-151:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:10:35.829:WARN:oejut.QueuedThreadPool:qtp2016627616-147:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:47.705:WARN:oejut.QueuedThreadPool:qtp2016627616-143:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:00.107:WARN:oejut.QueuedThreadPool:qtp2016627616-139:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:56.608:WARN:oejut.QueuedThreadPool:qtp2016627616-138:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:54.793:WARN:oejut.QueuedThreadPool:qtp2016627616-93:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:50.928:WARN:oejh.HttpParser:qtp2016627616-90: badMessage: 400 No Host for HttpChannelOverHttp@4be6e4c7{r=0,a=IDLE,uri=-}
2013-12-16 16:14:52.293:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:54.584:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
Exception in thread "qtp2016627616-90" java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:16:55.461:WARN:oeji.SelectorManager:qtp2016627616-12-selector-ServerConnectorManager@6f9bc97/0: Exception while notifying connection SslConnection@2863cb73{NEED_UNWRAP,eio=-1/-1,di=-1} -> HttpConnection@2fc1ffbc{IDLE}
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:52.462:WARN:oejut.QueuedThreadPool:qtp2016627616-155:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:21.824:WARN:oejut.QueuedThreadPool:qtp2016627616-151:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:10:35.829:WARN:oejut.QueuedThreadPool:qtp2016627616-147:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:47.705:WARN:oejut.QueuedThreadPool:qtp2016627616-143:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:00.107:WARN:oejut.QueuedThreadPool:qtp2016627616-139:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:56.608:WARN:oejut.QueuedThreadPool:qtp2016627616-138:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:54.793:WARN:oejut.QueuedThreadPool:qtp2016627616-93:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:50.928:WARN:oejh.HttpParser:qtp2016627616-90: badMessage: 400 No Host for HttpChannelOverHttp@4be6e4c7{r=0,a=IDLE,uri=-}
2013-12-16 16:14:52.293:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:54.584:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
Exception in thread "qtp2016627616-90" java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:16:55.461:WARN:oeji.SelectorManager:qtp2016627616-12-selector-ServerConnectorManager@6f9bc97/0: Exception while notifying connection SslConnection@2863cb73{NEED_UNWRAP,eio=-1/-1,di=-1} -> HttpConnection@2fc1ffbc{IDLE}
java.lang.OutOfMemoryError: Java heap space
Try to set heap size:
Code:
java -Xms256m -Xmx1024m -jar start.jar
Code:
2013-12-16 20:44:53.604:WARN:oejh.HttpParser:qtp180753500-18: badMessage: 400 Illegal character for HttpChannelOverHttp@6b073ba0{r=0,a=IDLE,uri=-}
2013-12-16 20:45:49.860:WARN:oejh.HttpParser:qtp180753500-19: badMessage: 400 Illegal character for HttpChannelOverHttp@13460a5b{r=0,a=IDLE,uri=-}
2013-12-16 20:52:50.693:WARN:oejh.HttpParser:qtp180753500-14: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@2d0aa021{r=5,a=IDLE,uri=-}
2013-12-16 20:45:49.860:WARN:oejh.HttpParser:qtp180753500-19: badMessage: 400 Illegal character for HttpChannelOverHttp@13460a5b{r=0,a=IDLE,uri=-}
2013-12-16 20:52:50.693:WARN:oejh.HttpParser:qtp180753500-14: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@2d0aa021{r=5,a=IDLE,uri=-}
Any Jetty expert there?
laptop is sweating hard ….
[2013-12-16 22:15:54.942] Generated an incorrect block. Waiting for the next one
Cpu 25%-45%
Mem 2.40 GB
Pin
[2013-12-16 22:15:54.942] Generated an incorrect block. Waiting for the next one
Cpu 25%-45%
Mem 2.40 GB
Pin
LTC and all Scrypt clones will collapse IMHO. That's why I have already got out of ANC though I loved it...
http://www.coindesk.com/litecoin-radeon-shortage/
Let's see when ASIC's bubble will collapse too - maybe 3rd of Jan?
http://www.coindesk.com/litecoin-radeon-shortage/
Let's see when ASIC's bubble will collapse too - maybe 3rd of Jan?
Important note
"pushThreshold" and "pullThreshold" r set to 0 by default, but everyone who run a public node should mark their nodes with at least 1 NXT, coz in the future these parameters may be set to non-zero values.
"pushThreshold" and "pullThreshold" r set to 0 by default, but everyone who run a public node should mark their nodes with at least 1 NXT, coz in the future these parameters may be set to non-zero values.
Updated nxtbase's web.xml.default template to set to 1.
node*.nxtbase.com are updated as well.
Same here. *.nxtnode.net updated and thresholds set to 1
Starting to see these on a few nodes:
Code:
2013-12-16 21:13:54.744:WARN:oejh.HttpParser:qtp180753500-18: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@757e9b8e{r=1,a=IDLE,uri=-}
This is from the last version.
Code:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:52.462:WARN:oejut.QueuedThreadPool:qtp2016627616-155:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:21.824:WARN:oejut.QueuedThreadPool:qtp2016627616-151:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:10:35.829:WARN:oejut.QueuedThreadPool:qtp2016627616-147:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:47.705:WARN:oejut.QueuedThreadPool:qtp2016627616-143:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:00.107:WARN:oejut.QueuedThreadPool:qtp2016627616-139:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:56.608:WARN:oejut.QueuedThreadPool:qtp2016627616-138:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:54.793:WARN:oejut.QueuedThreadPool:qtp2016627616-93:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:50.928:WARN:oejh.HttpParser:qtp2016627616-90: badMessage: 400 No Host for HttpChannelOverHttp@4be6e4c7{r=0,a=IDLE,uri=-}
2013-12-16 16:14:52.293:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:54.584:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
Exception in thread "qtp2016627616-90" java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:16:55.461:WARN:oeji.SelectorManager:qtp2016627616-12-selector-ServerConnectorManager@6f9bc97/0: Exception while notifying connection SslConnection@2863cb73{NEED_UNWRAP,eio=-1/-1,di=-1} -> HttpConnection@2fc1ffbc{IDLE}
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:52.462:WARN:oejut.QueuedThreadPool:qtp2016627616-155:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:11:21.824:WARN:oejut.QueuedThreadPool:qtp2016627616-151:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:10:35.829:WARN:oejut.QueuedThreadPool:qtp2016627616-147:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:47.705:WARN:oejut.QueuedThreadPool:qtp2016627616-143:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:09:00.107:WARN:oejut.QueuedThreadPool:qtp2016627616-139:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:56.608:WARN:oejut.QueuedThreadPool:qtp2016627616-138:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:08:54.793:WARN:oejut.QueuedThreadPool:qtp2016627616-93:
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:50.928:WARN:oejh.HttpParser:qtp2016627616-90: badMessage: 400 No Host for HttpChannelOverHttp@4be6e4c7{r=0,a=IDLE,uri=-}
2013-12-16 16:14:52.293:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:14:54.584:WARN:oejs.ServletHandler:qtp2016627616-90: Error for /nxt
java.lang.OutOfMemoryError: Java heap space
Exception in thread "qtp2016627616-90" java.lang.OutOfMemoryError: Java heap space
2013-12-16 16:16:55.461:WARN:oeji.SelectorManager:qtp2016627616-12-selector-ServerConnectorManager@6f9bc97/0: Exception while notifying connection SslConnection@2863cb73{NEED_UNWRAP,eio=-1/-1,di=-1} -> HttpConnection@2fc1ffbc{IDLE}
java.lang.OutOfMemoryError: Java heap space
Jump to: