assembly
assembly
Show Posts - tiker
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Ardor Client: Ardor 2.2.6

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - tiker

Pages: [1]
1
Nxt General Discussion / 1.5.8e out of memory
« on: May 19, 2015, 03:04:50 pm »
Since I updated to 1.5.8e, I haven't been able to keep the program running for more than a couple of days.

The .bat file I use to start NXT uses the following line to start NXT:
Code: [Select]
start "NXT NRS" java -Xmx1024M -cp nxt.jar;lib\*;conf nxt.Nxt

After a day or two, NXT dies.  Here's the end of a couple log files:
Code: [Select]
2015-05-17 01:43:58 FINE: Blacklisting 188.48.72.91 because of: nxt.dy: Peer sends invalid transactions: [nxt.dy: Invalid transaction signature for transaction {"senderPublicKey":"fad868f91878093dd9c2422bdb4f601a9e6c3b2b6d0f12559b4fbfd04ef85c6f","signature":"adf09a3f0984a40eeb2adf751147639c0a2ae780b55d1fb0a426b3f0851887050bd10a014d34c8287035846ea0d67baa76757e30ed84df0dc3e7f2bd8e74c50f","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"7217849232031679657","attachment":{"version.Message":1,"messageIsText":true,"message":"{\"contract\":{\"description\":\"SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO","version.ArbitraryMessage":0},"subtype":0,"amountNQT":0,"recipient":"0","ecBlockHeight":428929,"deadline":1440,"timestamp":46547039}]
nxt.dy: Peer sends invalid transactions: [nxt.dy: Invalid transaction signature for transaction {"senderPublicKey":"fad868f91878093dd9c2422bdb4f601a9e6c3b2b6d0f12559b4fbfd04ef85c6f","signature":"adf09a3f0984a40eeb2adf751147639c0a2ae780b55d1fb0a426b3f0851887050bd10a014d34c8287035846ea0d67baa76757e30ed84df0dc3e7f2bd8e74c50f","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"7217849232031679657","attachment":{"version.Message":1,"messageIsText":true,"message":"{\"contract\":{\"description\":\"SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description.  SEO contract testing after republishing brief description. SEO","version.ArbitraryMessage":0},"subtype":0,"amountNQT":0,"recipient":"0","ecBlockHeight":428929,"deadline":1440,"timestamp":46547039}]
at nxt.ez.a(Unknown Source)
at nxt.ez.a(Unknown Source)
at nxt.peer.u.a(Unknown Source)
at nxt.peer.PeerServlet.a(Unknown Source)
at nxt.peer.PeerServlet.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:83)
at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:364)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:470)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:322)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:292)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:517)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Unknown Source)
2015-05-17 01:53:52 FINE: Unblacklisting 5.9.8.9
2015-05-17 01:54:52 FINE: Unblacklisting 188.48.72.91
2015-05-17 02:08:08 FINE: Will process a fork of 2 blocks
2015-05-17 02:08:08 FINE: Rollback from block 3534093948153901715 at height 428945 to 2778486728366414826 at 428944
2015-05-17 02:08:14 FINE: Switched to peer's fork
2015-05-17 02:08:15 FINE: Error sending request to peer 176.94.115.161: Read timed out
2015-05-17 02:08:27 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError


Code: [Select]
2015-05-19 06:04:33 FINE: Unblacklisting 82.226.204.140
2015-05-19 06:05:33 FINE: Unblacklisting 195.28.85.114
2015-05-19 06:05:33 FINE: Unblacklisting 124.135.104.190
2015-05-19 06:18:46 FINE: Inbound WebSocket connection with 97.87.75.68 completed
2015-05-19 06:29:15 FINE: Hallmark host 54.77.53.42 doesn't match 131.72.136.251
2015-05-19 06:40:09 FINE: Error sending request to peer 217.17.88.5: Read timed out
2015-05-19 06:43:26 FINE: Inbound WebSocket connection with 97.87.75.68 closed
2015-05-19 06:45:45 FINE: Error sending request to peer 77.88.208.12: connect timed out
2015-05-19 06:48:50 FINE: Inbound WebSocket connection with 90.51.43.27 closed
2015-05-19 06:49:02 FINE: Inbound WebSocket connection with 23.88.59.163 closed
2015-05-19 06:49:27 FINE: Database connection pool current size: 26
2015-05-19 06:49:27 FINE: Database connection pool current size: 27
2015-05-19 06:49:27 FINE: Database connection pool current size: 28
2015-05-19 06:49:27 FINE: Database connection pool current size: 29
2015-05-19 06:49:27 FINE: Database connection pool current size: 30
2015-05-19 06:50:56 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError: unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.addWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source)
at java.util.concurrent.AbstractExecutorService.submit(Unknown Source)
at nxt.cc$1.a(Unknown Source)
at nxt.cc$1.a(Unknown Source)
at nxt.cc$1.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(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)

Is this a problem with my setup?  I haven't seen any other reports for this so far.  Previous versions such as 1.5.6e did not have this problem.  Same .bat file used in the past.



2
Nxt Helpdesk / Forging questions
« on: January 31, 2015, 12:00:12 am »
Is there an indicator or something to tell me that there's a problem with forging if something goes wrong?

I've been reading the various articles about forging, how it's based on the "Effective Balance".  However, when I look at the "last blocks generated" page I'm seeing accounts with a balance which is much lower than my balance on the page multiple times.

So, if an account with a small fraction of NXT compared to my account can generate multiple blocks in a 20 minute period, why has my client not generated a block yet?

My client is logged in, the green icon representing an LED is changing shades of green, I see the line "account 123 whatver started forging deadline...." message on the console.  The "Effective Balance" for my account is 30,000+ NXT.

Is there something I'm missing?  If my client was supposed to generate the next block but doesn't, would it be logged anywhere?

Pages: [1]
elective-stereophonic
elective-stereophonic
assembly
assembly