[Oct 07 14:42:53] java.lang.NullPointerException: Cannot read the array length because "<parameter1>" is null
See original GitHub issueI’m not sure if this is an issue that needs to be addressed, but I’m seeing <title> after the 1.5.0 update. This is the latest sparrow.log entry…
021-10-07 14:42:57,289 ERROR [JavaFX Application Thread] c.s.s.w.WalletForm [null:-1] Error retrieving wallet history
com.sparrowwallet.sparrow.net.ServerException: Failed to subscribe to paths: [m/0/0-m/0/19]
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer.subscribeWalletNodes(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer.getHistory(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer.getHistory(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer$TransactionHistoryService$1.call(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.ElectrumServer$TransactionHistoryService$1.call(Unknown Source)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.sparrowwallet.sparrow.net.ServerException: Retries exhausted
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.RetryLogic.getResult(Unknown Source)
at com.sparrowwallet.sparrow/com.sparrowwallet.sparrow.net.BatchedElectrumServerRpc.subscribeScriptHashes(Unknown Source)
... 13 common frames omitted
Caused by: java.lang.IllegalStateException: Unspecified id: 'm/1/0' in response
at simple.json.rpc.client@1.0/com.github.arteam.simplejsonrpc.client.builder.BatchRequestBuilder.processSingleResponse(Unknown Source)
at simple.json.rpc.client@1.0/com.github.arteam.simplejsonrpc.client.builder.BatchRequestBuilder.processBatchResponse(Unknown Source)
at simple.json.rpc.client@1.0/com.github.arteam.simplejsonrpc.client.builder.BatchRequestBuilder.execute(Unknown Source)
... 15 common frames omittedIssue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
Cannot read the array length because "<local3>" is null
I am working on a JDA Discord Bot and everytime I run it, I get this exception. java.lang.NullPointerException: Cannot read the array length...
Read more >Helpful NullPointerExceptions - G. Hunter Anderson
toUpperCase(); /* Exception in thread "main" java.lang. ... NullPointerException: Cannot read the array length because "myArray" is null */ ...
Read more >Reasons and Solutions of Null Pointer Exception in Java
Exception in thread "main" java.lang.NullPointerException: Cannot read the array length because "<local2>" is null at example3.main(example3.java:7).
Read more >Cannot read the array length because "buf" is null - CodeProject
Let me just explain what the error means: You have tried to use a variable, property, or a method return value but it...
Read more >java.lang.NullPointerException: Cannot read the array length ...
java.lang.NullPointerException: Cannot read the array length because "storage" is null at io.papermc.paper.world.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve posted an issue to the MyNode guys, as it looks (to my eyes) as if the Electrum server is now routing over TOR, rather than using the local network.
I’ve reset the bitcoind config
<maxconnections>to a much lower number than the default value of 40 to reduce the load that MyNode was subjected to.Since doing that, I’ve not had any repeat of this issue and so I will close this now, with a thank you for your time, and my best regards.