problem is still same withn 0.40 version 
I'm getting new blocks right away on 0.4.0. No problems at all:
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2285. (Read 2761632 times)
I'm getting new blocks right away on 0.4.0. No problems at all:
Is sending NXT still possible during DDOS?
Any certain measures I should take? What is recommended fee, and what is the best deadline to use when sending?
Thanks very much
Any certain measures I should take? What is recommended fee, and what is the best deadline to use when sending?
Thanks very much
problem is still same withn 0.40 version
So you need to ask him to upload 0.4.0 again if you don't trust my version . There's no way I can prove that the file I uploaded is "safe".
. There's no way I can prove that the file I uploaded is "safe". 
i believe that link points to 0.4.2 now. CfB reuses the same link for his downloads
22548 13622604611491767079 152330 %
why can I not get to that block? stuck on 22486. I have TCP7874 forwarded to my PC, 50+ active peers (and climbing). The timestap on that block is about 2 hrs old, and i dont see a "you can generate" timer at all
You don't know. It might be full of viruses and malware. Use on your own risk.
How do we know this is safe?
22548 13622604611491767079 152330 %
why can I not get to that block? stuck on 22486. I have TCP7874 forwarded to my PC, 50+ active peers (and climbing). The timestap on that block is about 2 hrs old
Where I can found 0.40 version
Link?
Link?
Version 0.4.2 of the client is causing problems on Linux.
Version 0.4.0 works fine.
On v.0.4.2 I'm getting this error time and again:
Same here - no manipulations with -Xms and -Xmx help.
Version 0.4.0 works fine.
On v.0.4.2 I'm getting this error time and again:
Keep getting this error after a few minutes of running NXT.
Loads of free memory ~13GB, and 4G of swap. Tried increasing the -Xms and -Xmx values. Using Oracle JDK 1.7 u45 on Linux.
Code:
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x000000077c280000, 4718592, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 4718592 bytes for committing reserved memory.
# An error report file with more information is saved as:
Loads of free memory ~13GB, and 4G of swap. Tried increasing the -Xms and -Xmx values. Using Oracle JDK 1.7 u45 on Linux.
Same here - no manipulations with -Xms and -Xmx help.
I don't understand, i stay on this block since 1 hour and i can't see the recent block
I always need to reinstall all to see the new block!
I have something wrong in my config?
22496 6483973064837388393 23/12/2013 00:00:42
9 0 + 9 1'359 B
1 15424397685768250757 6176 %
I always need to reinstall all to see the new block!
I have something wrong in my config?
22496 6483973064837388393 23/12/2013 00:00:42
9 0 + 9 1'359 B
1 15424397685768250757 6176 %
stuck here for 3 hours...
22389 8435108420902103484 22. dec. 2013 22.06.19 CET
4 0 + 4 590 B
1 17150625892671498274 15950 %
22389 8435108420902103484 22. dec. 2013 22.06.19 CET
4 0 + 4 590 B
1 17150625892671498274 15950 %
22548 13622604611491767079 152330 %
Errors on my node
Code:
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: 30000/30000 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-22 18:18:09.424:WARN:oejh.HttpParser:qtp2016627616-258: badMessage: 400 Illegal character for HttpChannelOverHttp@50adf3be{r=0,a=IDLE,uri=-}
2013-12-22 18:20:20.196:WARN:oejh.HttpParser:qtp2016627616-258: badMessage: 400 Illegal character for HttpChannelOverHttp@67e539da{r=0,a=IDLE,uri=-}
2013-12-22 18:25:31.647:WARN:oejh.HttpParser:qtp2016627616-252: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@3ecc7e07{r=1,a=IDLE,uri=-}
2013-12-22 18:50:55.640:WARN:oejh.HttpParser:qtp2016627616-204: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@b1436e2{r=1,a=IDLE,uri=-}
2013-12-22 18:51:49.223:WARN:oejh.HttpParser:qtp2016627616-259: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@5ea1690f{r=2,a=IDLE,uri=-}
2013-12-22 18:51:49.224:WARN:oejh.HttpParser:qtp2016627616-273: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@36f88852{r=1,a=IDLE,uri=-}
2013-12-22 18:51:55.396:WARN:oejh.HttpParser:qtp2016627616-272: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@4aaba0cf{r=1,a=IDLE,uri=-}
2013-12-22 18:52:03.017:WARN:oejh.HttpParser:qtp2016627616-273: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@3590ca3a{r=1,a=IDLE,uri=-}
2013-12-22 18:53:03.216:WARN:oejh.HttpParser:qtp2016627616-205: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@3fa92c24{r=1,a=IDLE,uri=-}
2013-12-22 18:54:43.605:WARN:oejh.HttpParser:qtp2016627616-273: badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@47fcc791{r=1,a=IDLE,uri=-}
How ? in which file ? The difficulty level is very low. am I in a wrong branch ?
In nxt/webapps/root/WEB-INF/web.xml. U seem to be on a short branch.
So should I keep it going. Or shut it down and wait for an update. Is there any benefit to the network if I keep on going ?
SAME PROBLEM AND ME
How do you fix this?
Generated an incorrect block. Waiting for the next one
How do you fix this?
Generated an incorrect block. Waiting for the next one
It's normal, I think. It just means you tried to solve a block, but failed.
CfB, please confirm.
SAME PROBLEM AND ME
How do you fix this?
Generated an incorrect block. Waiting for the next one
How do you fix this?
Generated an incorrect block. Waiting for the next one
Jump to: