PoolServerJ - Tech Support

[Flowz]

Can anyone tell me which bitcoin daemon version is the best for PoolServerJ?

I know 0.7 won't work, but will anything below it work? Because I'm trying to figure out the reasons of some bugs I've been getting.

And what about namecoind? What are the patches that it needs to make getmemorypool work with it, and where to find it?

Thank you!

Since nobody has answered I'll reply back to you.

As far as I know, from a performance point of view, the 4diff patched bitcoind is the best way to go.

http://poolserverj.org/documentation/performance-memory-tuning/

https://github.com/bitcoin/bitcoin/pull/426

The last patch I remember coming out was a beta patch 4diff with a 0.5.

Kind regards,
Flowz

[1715061579]

1715061579

[1715061579]

1715061579

[1715061579]

1715061579

[sippsnapp]

Anybody here who can tell me what am i doing wrong?

Code:

root@j064:/opt/poolserverj-0.4.0rc2/bin# java -classpath poolserverj.jar:../lib/*:../lib/lib_non-maven/*:../lib/plugins com.shadworld.poolserver.servicelauncher.PoolServerService start ../conf/poolserverj.conf
Args - [2]: start ../conf/poolserverj.conf
PoolServerJ Service Starting Tue Oct 30 14:46:55 UTC 2012
[14:46:56.054] Starting PoolServerJ v0.4.0-WM-b233-c-d5e730c5756c
[14:46:56.055] user.dir: /opt/poolserverj-0.4.0rc2/bin
[14:46:56.055] Home path set to: /opt/poolserverj-0.4.0rc2/bin/poolserverj.jar
[14:46:56.055] Home directory set from jar file location to: /opt/poolserverj-0.4.0rc2
[14:46:56.059] Sever is set to testnet: false
[14:46:56.066] Adding donation target: chainName: namecoin donationAmount: 0.3 calc method: [% of total] addressUrl: http://poolserverj.org/meta/donations/ address: NFja75nNRHZYKtN9YQ6wHPQdmhzBEAmTAt
[14:46:56.067] Adding donation target: chainName: bitcoin donationAmount: 0.3 calc method: [% of total] addressUrl: http://poolserverj.org/meta/donations/ address: 1LezqRatQz7MeNoCVziYwcdwtqeEbvrdAq
[14:46:56.071] Wrote PID: 22107 to pidFile: /opt/poolserverj-0.4.0rc2/tmp/poolserverj.pid
[14:46:56.101] Connecting to DB URL: jdbc:mysql://127.0.0.1:3306/poolserverj_native?allowMultiQueries=true&zeroDateTimeBehavior=round&dumpQueriesOnException=true&dumpMetadataOnColumnNotFound=true&useCompression=true&autoReconnect=true&rewriteBatchedStatements=true
[14:46:56.288] Mapped parameter 1 to field 1 (remote_host)
[14:46:56.288] Mapped parameter 2 to field 2 (username)
[14:46:56.289] Mapped parameter 3 to field 3 (our_result)
[14:46:56.289] Mapped parameter 4 to field 4 (upstream_result)
[14:46:56.289] Mapped parameter 5 to field 5 (reason)
[14:46:56.289] Mapped parameter 6 to field 7 (time)
[14:46:56.289] Mapped parameter 7 to field 8 (source)
[14:46:56.289] Mapped parameter 8 to field 9 (block_num)
[14:46:56.289] Mapped parameter 9 to field 11 (useragent)
[14:46:56.290] Building Shares-DB-flush-engine: DefaultPreparedStatementSharesDBFlushEngine.class with extraParams: []
[14:46:56.291] Building Worker-authentication-engine: WorkerAuthenticator.class with extraParams: null
[14:46:56.302] Configuring aux daemon for WorkSource: bitcoind-mm
[14:46:56.302] Chain name: namecoin
[14:46:56.302] Chain id: 1
[14:46:56.302] Chain url: http://127.0.0.1:7334/
[14:46:56.303] Chain username: noobtub3ndsafu
[14:46:56.303] Chain payoutAddress: N15ThaRx21TjWsDdex4TuUPywMSts4iXM3
[14:46:56.303] Chain password: 9*****************************1
530 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
547 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
585 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@0.0.0.0:8999 STARTING
586 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
586 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
589 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@127.0.0.1:8997 STARTING
[14:46:56.447] Starting local work source proxy: bitcoind-mm
[14:46:56.508] RETRY
[14:46:56.508] RETRY
[14:46:56.515] RETRY
[14:46:56.516] RETRY
[14:46:56.518] New Block detected [81555] from source: DaemonSource[bitcoind-mm].namecoin - 0 lagging sources.
[14:46:56.518] New Block detected [205718] from source: DaemonSource[bitcoind-mm].bitcoin - 0 lagging sources.
[14:46:56.518] Restoring workmap from file: /opt/poolserverj-0.4.0rc2/tmp/workmap-8999.bin
[14:46:56.806] Updating donation target address for chain: namecoin Address: NFja75nNRHZYKtN9YQ6wHPQdmhzBEAmTAt
[14:46:56.912] Updating donation target address for chain: bitcoin Address: 1Lk8f18EyPB3uAJvgTeHgzCVkKY9njQ5bA
[14:47:06.548] Exception in Cleaner Thread
java.lang.RuntimeException: Waited 5 seconds for client provider to be set but it hasn't.  This would indicate a problem with your client configuration.
        at com.shadworld.poolserver.workmaker.WorkMaker.update(WorkMaker.java:184)
        at com.shadworld.poolserver.source.merged.MergedMiningGroup.updateAuxes(MergedMiningGroup.java:249)
        at com.shadworld.poolserver.Cleaner.run(Cleaner.java:54)
java.io.IOException: Socket is disconnected
        at com.google.bitcoin.core.BitcoinSerializer.seekPastMagicBytes(BitcoinSerializer.java:347)
        at com.google.bitcoin.core.BitcoinSerializer.deserialize(BitcoinSerializer.java:216)
        at com.google.bitcoin.core.NetworkConnection.readMessage(NetworkConnection.java:170)
        at com.google.bitcoin.core.NetworkConnection.<init>(NetworkConnection.java:96)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.startListener(BitcoinDualConnection.java:93)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.start(BitcoinDualConnection.java:47)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.start(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:159)
        at com.shadworld.poolserver.source.WorkSource.start(WorkSource.java:154)
        at com.shadworld.poolserver.WorkProxy.start(WorkProxy.java:914)
        at com.shadworld.poolserver.PoolServer.start(PoolServer.java:262)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.start(PoolServerService.java:99)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.windowsService(PoolServerService.java:58)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.main(PoolServerService.java:28)
[14:47:57.033] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:133)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.startListener(BitcoinDualConnection.java:98)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.start(BitcoinDualConnection.java:47)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.start(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:159)
        at com.shadworld.poolserver.source.WorkSource.start(WorkSource.java:154)
        at com.shadworld.poolserver.WorkProxy.start(WorkProxy.java:914)
        at com.shadworld.poolserver.PoolServer.start(PoolServer.java:262)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.start(PoolServerService.java:99)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.windowsService(PoolServerService.java:58)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.main(PoolServerService.java:28)
[14:47:57.034] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:141)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.startListener(BitcoinDualConnection.java:98)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.start(BitcoinDualConnection.java:47)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.start(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:159)
        at com.shadworld.poolserver.source.WorkSource.start(WorkSource.java:154)
        at com.shadworld.poolserver.WorkProxy.start(WorkProxy.java:914)
        at com.shadworld.poolserver.PoolServer.start(PoolServer.java:262)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.start(PoolServerService.java:99)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.windowsService(PoolServerService.java:58)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.main(PoolServerService.java:28)
^C73102 [Thread-0] INFO org.eclipse.jetty.util.log - Graceful shutdown SelectChannelConnector@0.0.0.0:8999 STARTED
[14:48:08.960] Shutting down poolserver...
[14:48:08.960] Flushing cached shares...
[14:48:08.960] Flush shares cache complete...
[14:48:08.961] Waiting to complete upstream share submits...
[14:48:08.961] Finished upstream submits...
[14:48:08.961] Flushing final shares...
[14:48:08.962] 0 shares in 1,351,608,448 seconds. Current hashRate: 0 GH/s
[14:48:08.962] Submit Throttling on: false
[14:48:08.962] All share submits flushed...
[14:48:08.962] Waiting for threads to die...
[14:48:08.963] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:133)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.shutdown(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:146)
        at com.shadworld.poolserver.source.WorkSource.shutdown(WorkSource.java:190)
        at com.shadworld.poolserver.WorkProxy.shutdown(WorkProxy.java:923)
        at com.shadworld.poolserver.PoolServer.shutdown(PoolServer.java:620)
        at com.shadworld.poolserver.PoolServer$1.run(PoolServer.java:252)
[14:48:08.964] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:141)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.shutdown(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:146)
        at com.shadworld.poolserver.source.WorkSource.shutdown(WorkSource.java:190)
        at com.shadworld.poolserver.WorkProxy.shutdown(WorkProxy.java:923)
        at com.shadworld.poolserver.PoolServer.shutdown(PoolServer.java:620)
        at com.shadworld.poolserver.PoolServer$1.run(PoolServer.java:252)
[14:48:08.965] Dumping workmap to file: /opt/poolserverj-0.4.0rc2/tmp/workmap-8999.bin
73112 [Thread-0] INFO org.eclipse.jetty.util.log - Graceful shutdown o.e.j.s.ServletContextHandler{/,null}
[14:48:09.032] Shutting down Web Server...
[14:48:09.133] Closed 0 longpoll connections in 0ms
78165 [Thread-0] INFO org.eclipse.jetty.util.log - stopped o.e.j.s.ServletContextHandler{/,null}
78278 [shutdown] INFO org.eclipse.jetty.util.log - stopped o.e.j.s.ServletContextHandler{/,null}
[14:48:14.188] Shutdown complete...
root@j064:/opt/poolserverj-0.4.0rc2/bin#

If its caused by a wrong bitcoind build, which one is the correct one? [source please]

[Flowz]

Anybody here who can tell me what am i doing wrong?

Code:

root@j064:/opt/poolserverj-0.4.0rc2/bin# java -classpath poolserverj.jar:../lib/*:../lib/lib_non-maven/*:../lib/plugins com.shadworld.poolserver.servicelauncher.PoolServerService start ../conf/poolserverj.conf
Args - [2]: start ../conf/poolserverj.conf
PoolServerJ Service Starting Tue Oct 30 14:46:55 UTC 2012
[14:46:56.054] Starting PoolServerJ v0.4.0-WM-b233-c-d5e730c5756c
[14:46:56.055] user.dir: /opt/poolserverj-0.4.0rc2/bin
[14:46:56.055] Home path set to: /opt/poolserverj-0.4.0rc2/bin/poolserverj.jar
[14:46:56.055] Home directory set from jar file location to: /opt/poolserverj-0.4.0rc2
[14:46:56.059] Sever is set to testnet: false
[14:46:56.066] Adding donation target: chainName: namecoin donationAmount: 0.3 calc method: [% of total] addressUrl: http://poolserverj.org/meta/donations/ address: NFja75nNRHZYKtN9YQ6wHPQdmhzBEAmTAt
[14:46:56.067] Adding donation target: chainName: bitcoin donationAmount: 0.3 calc method: [% of total] addressUrl: http://poolserverj.org/meta/donations/ address: 1LezqRatQz7MeNoCVziYwcdwtqeEbvrdAq
[14:46:56.071] Wrote PID: 22107 to pidFile: /opt/poolserverj-0.4.0rc2/tmp/poolserverj.pid
[14:46:56.101] Connecting to DB URL: jdbc:mysql://127.0.0.1:3306/poolserverj_native?allowMultiQueries=true&zeroDateTimeBehavior=round&dumpQueriesOnException=true&dumpMetadataOnColumnNotFound=true&useCompression=true&autoReconnect=true&rewriteBatchedStatements=true
[14:46:56.288] Mapped parameter 1 to field 1 (remote_host)
[14:46:56.288] Mapped parameter 2 to field 2 (username)
[14:46:56.289] Mapped parameter 3 to field 3 (our_result)
[14:46:56.289] Mapped parameter 4 to field 4 (upstream_result)
[14:46:56.289] Mapped parameter 5 to field 5 (reason)
[14:46:56.289] Mapped parameter 6 to field 7 (time)
[14:46:56.289] Mapped parameter 7 to field 8 (source)
[14:46:56.289] Mapped parameter 8 to field 9 (block_num)
[14:46:56.289] Mapped parameter 9 to field 11 (useragent)
[14:46:56.290] Building Shares-DB-flush-engine: DefaultPreparedStatementSharesDBFlushEngine.class with extraParams: []
[14:46:56.291] Building Worker-authentication-engine: WorkerAuthenticator.class with extraParams: null
[14:46:56.302] Configuring aux daemon for WorkSource: bitcoind-mm
[14:46:56.302] Chain name: namecoin
[14:46:56.302] Chain id: 1
[14:46:56.302] Chain url: http://127.0.0.1:7334/
[14:46:56.303] Chain username: noobtub3ndsafu
[14:46:56.303] Chain payoutAddress: N15ThaRx21TjWsDdex4TuUPywMSts4iXM3
[14:46:56.303] Chain password: 9*****************************1
530 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
547 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
585 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@0.0.0.0:8999 STARTING
586 [main] INFO org.eclipse.jetty.util.log - jetty-7.4.0.v20110414
586 [main] INFO org.eclipse.jetty.util.log - started o.e.j.s.ServletContextHandler{/,null}
589 [main] INFO org.eclipse.jetty.util.log - Started SelectChannelConnector@127.0.0.1:8997 STARTING
[14:46:56.447] Starting local work source proxy: bitcoind-mm
[14:46:56.508] RETRY
[14:46:56.508] RETRY
[14:46:56.515] RETRY
[14:46:56.516] RETRY
[14:46:56.518] New Block detected [81555] from source: DaemonSource[bitcoind-mm].namecoin - 0 lagging sources.
[14:46:56.518] New Block detected [205718] from source: DaemonSource[bitcoind-mm].bitcoin - 0 lagging sources.
[14:46:56.518] Restoring workmap from file: /opt/poolserverj-0.4.0rc2/tmp/workmap-8999.bin
[14:46:56.806] Updating donation target address for chain: namecoin Address: NFja75nNRHZYKtN9YQ6wHPQdmhzBEAmTAt
[14:46:56.912] Updating donation target address for chain: bitcoin Address: 1Lk8f18EyPB3uAJvgTeHgzCVkKY9njQ5bA
[14:47:06.548] Exception in Cleaner Thread
java.lang.RuntimeException: Waited 5 seconds for client provider to be set but it hasn't.  This would indicate a problem with your client configuration.
        at com.shadworld.poolserver.workmaker.WorkMaker.update(WorkMaker.java:184)
        at com.shadworld.poolserver.source.merged.MergedMiningGroup.updateAuxes(MergedMiningGroup.java:249)
        at com.shadworld.poolserver.Cleaner.run(Cleaner.java:54)
java.io.IOException: Socket is disconnected
        at com.google.bitcoin.core.BitcoinSerializer.seekPastMagicBytes(BitcoinSerializer.java:347)
        at com.google.bitcoin.core.BitcoinSerializer.deserialize(BitcoinSerializer.java:216)
        at com.google.bitcoin.core.NetworkConnection.readMessage(NetworkConnection.java:170)
        at com.google.bitcoin.core.NetworkConnection.<init>(NetworkConnection.java:96)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.startListener(BitcoinDualConnection.java:93)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.start(BitcoinDualConnection.java:47)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.start(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:159)
        at com.shadworld.poolserver.source.WorkSource.start(WorkSource.java:154)
        at com.shadworld.poolserver.WorkProxy.start(WorkProxy.java:914)
        at com.shadworld.poolserver.PoolServer.start(PoolServer.java:262)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.start(PoolServerService.java:99)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.windowsService(PoolServerService.java:58)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.main(PoolServerService.java:28)
[14:47:57.033] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:133)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.startListener(BitcoinDualConnection.java:98)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.start(BitcoinDualConnection.java:47)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.start(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:159)
        at com.shadworld.poolserver.source.WorkSource.start(WorkSource.java:154)
        at com.shadworld.poolserver.WorkProxy.start(WorkProxy.java:914)
        at com.shadworld.poolserver.PoolServer.start(PoolServer.java:262)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.start(PoolServerService.java:99)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.windowsService(PoolServerService.java:58)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.main(PoolServerService.java:28)
[14:47:57.034] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:141)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.startListener(BitcoinDualConnection.java:98)
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.start(BitcoinDualConnection.java:47)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.start(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:159)
        at com.shadworld.poolserver.source.WorkSource.start(WorkSource.java:154)
        at com.shadworld.poolserver.WorkProxy.start(WorkProxy.java:914)
        at com.shadworld.poolserver.PoolServer.start(PoolServer.java:262)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.start(PoolServerService.java:99)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.windowsService(PoolServerService.java:58)
        at com.shadworld.poolserver.servicelauncher.PoolServerService.main(PoolServerService.java:28)
^C73102 [Thread-0] INFO org.eclipse.jetty.util.log - Graceful shutdown SelectChannelConnector@0.0.0.0:8999 STARTED
[14:48:08.960] Shutting down poolserver...
[14:48:08.960] Flushing cached shares...
[14:48:08.960] Flush shares cache complete...
[14:48:08.961] Waiting to complete upstream share submits...
[14:48:08.961] Finished upstream submits...
[14:48:08.961] Flushing final shares...
[14:48:08.962] 0 shares in 1,351,608,448 seconds. Current hashRate: 0 GH/s
[14:48:08.962] Submit Throttling on: false
[14:48:08.962] All share submits flushed...
[14:48:08.962] Waiting for threads to die...
[14:48:08.963] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:133)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.shutdown(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:146)
        at com.shadworld.poolserver.source.WorkSource.shutdown(WorkSource.java:190)
        at com.shadworld.poolserver.WorkProxy.shutdown(WorkProxy.java:923)
        at com.shadworld.poolserver.PoolServer.shutdown(PoolServer.java:620)
        at com.shadworld.poolserver.PoolServer$1.run(PoolServer.java:252)
[14:48:08.964] This error may indicate your bitcoin daemon was not contactable. Check it is running and you have entered the correct host:port for the bitcoin protocol interface NOT the json-rpc interface.
java.lang.NullPointerException
        at com.shadworld.bitcoin.p2p.BitcoinDualConnection.shutdown(BitcoinDualConnection.java:141)
        at com.shadworld.poolserver.source.merged.JsonRpcMergeMiningLocalWorkMakerDaemonHandler.shutdown(JsonRpcMergeMiningLocalWorkMakerDaemonHandler.java:146)
        at com.shadworld.poolserver.source.WorkSource.shutdown(WorkSource.java:190)
        at com.shadworld.poolserver.WorkProxy.shutdown(WorkProxy.java:923)
        at com.shadworld.poolserver.PoolServer.shutdown(PoolServer.java:620)
        at com.shadworld.poolserver.PoolServer$1.run(PoolServer.java:252)
[14:48:08.965] Dumping workmap to file: /opt/poolserverj-0.4.0rc2/tmp/workmap-8999.bin
73112 [Thread-0] INFO org.eclipse.jetty.util.log - Graceful shutdown o.e.j.s.ServletContextHandler{/,null}
[14:48:09.032] Shutting down Web Server...
[14:48:09.133] Closed 0 longpoll connections in 0ms
78165 [Thread-0] INFO org.eclipse.jetty.util.log - stopped o.e.j.s.ServletContextHandler{/,null}
78278 [shutdown] INFO org.eclipse.jetty.util.log - stopped o.e.j.s.ServletContextHandler{/,null}
[14:48:14.188] Shutdown complete...
root@j064:/opt/poolserverj-0.4.0rc2/bin#

If its caused by a wrong bitcoind build, which one is the correct one? [source please]

Are you only trying to mine namecoin's?

1. Make sure the information you set in the config file is correct, as to what you use to run your bitcoind!
-> A pretty common problem.

From what I'm reading, you're only trying to mine namecoins:

Code:

[14:46:56.302] Chain name: namecoin
[14:46:56.302] Chain id: 1
[14:46:56.302] Chain url: http://127.0.0.1:7334/
[14:46:56.303] Chain username: noobtub3ndsafu
[14:46:56.303] Chain payoutAddress: N15ThaRx21TjWsDdex4TuUPywMSts4iXM3
[14:46:56.303] Chain password: 9*****************************1

In most cases chain id 1 is the bitcoin chain, and chain id 2 is namecoin.
(You've edited the config to not mine bitcoins I suppose by just changing the bitcoin information to bitcoin information?)
As far as I know you must run both bitcoind and namecoind for merged mining to work.


The namecoind is working properly, I suggest you to check if you bitcoind is running properly with the correct settings/config!

[sippsnapp]

I now have disabled namecoin/merged mining, i only care for bitcoin now.

I still need a correct release for bitcoin to run poolservj.

[Flowz]

I now have disabled namecoin/merged mining, i only care for bitcoin now.

I still need a correct release for bitcoin to run poolservj.

It doesn't matter which release to be honest.

On the PSJ-site under the 'fine tuning' tab you'll find the patch by JoelKatz for a certain bitcoin release which allow more connections to the daemon.

[nyusternie]

Greetings,

I would like to reach out to anyone that is still using PoolServerJ as an "active/production" pool server. I have about a month off during the holidays and I see it being spent in the Bitcoin community.

The last post on the official website "PoolServerJ 0.4rc1 WorkMaker Edition" was made on Nov 8 11'. I did see an update to the codebase on https://bitbucket.org/shadders/bitcoin-poolserverj/ on Oct 20 12', so I don't know where things stand right now. Does anyone know if this project is still active?

I've cloned the repo onto my GitHub account (just not a fan of Mercurial) to research the codebase, but it seems extremely outdated now (with Stratum and GetBlockTemplate being the norms now), so I'm trying to decide how to proceed with my own endeavors towards a Java-based mining server.

Any suggestions would be appreciated.

Thanks,
Shomari

[RoboCoder]

Greetings,

I would like to reach out to anyone that is still using PoolServerJ as an "active/production" pool server. I have about a month off during the holidays and I see it being spent in the Bitcoin community.

The last post on the official website "PoolServerJ 0.4rc1 WorkMaker Edition" was made on Nov 8 11'. I did see an update to the codebase on https://bitbucket.org/shadders/bitcoin-poolserverj/ on Oct 20 12', so I don't know where things stand right now. Does anyone know if this project is still active?

I've cloned the repo onto my GitHub account (just not a fan of Mercurial) to research the codebase, but it seems extremely outdated now (with Stratum and GetBlockTemplate being the norms now), so I'm trying to decide how to proceed with my own endeavors towards a Java-based mining server.

Any suggestions would be appreciated.

Thanks,
Shomari

I just started using it myself.. I am using it for solomining though and have not put a front end on it at this point.  Just thought this would be more efficient than mining directly against the bitcoind.  I am using the .7 version.  As I understand it - i don't need the patched version if i am using this newer version - would love some other opinion on that though.  I see a huge fluctuation in the hashrate reported by PSJ every 20-30 seconds or so and I use bfgminer as my clients and it appears that they are getting a lower hashrate by shares accepted than i would normally against a regular pool.  Wondering if that is due to Longpolling vs. stratum.

I am using the .4rc7 workmaker version.

PSJ gives decent stats on getworks and inound work - but i wish it would give more stats on the shares being tested back to the daemon.  I would actually lilke to see more stats in general by miner made available directly from the management interface.  Would certainly be willing to help test any work you do - and would definitely be willing to contribute funds toward development of stratum support and maybe a management client with stats reporting and more detail/monitoring by worker.

[RoboCoder]

Also would like to note that by switching to the 32bit java and incrreasing the jvm memory size the hashrate reported by PSJ did improve..

[nyusternie]

@RoboCoder - I have only spent a short time testing PSJ. Mainly to make sure it worked correctly so that I could study the codebase. My immediate goal is to gain a complete understanding of the inner working of Bitcoin (protocols, community, problems, etc). As I'm much stronger in Java than C, PSJ seemed to be the best starting point. BitcoinJ (https://code.google.com/p/bitcoinj/) has also a great codebase to learn from.

As the original author is unreachable, I've opted to start from scratch (learning along the way) in building a fresh JAVA pool server.  I've also been studying Eloipool's codebase (https://gitorious.org/bitcoin/eloipool), which is Python3, and it seems to be pretty solid. I've got a very VERY basic implementation up and running in Java, but its not quite ready for public testing yet.

PSJ gives decent stats on getworks and inound work - but i wish it would give more stats on the shares being tested back to the daemon.  I would actually lilke to see more stats in general by miner made available directly from the management interface.  Would certainly be willing to help test any work you do - and would definitely be willing to contribute funds toward development of stratum support and maybe a management client with stats reporting and more detail/monitoring by worker.

I totally agree, and plan on integrating a Reporting Engine with API support, run by a lightweight web server (lighttpd or similar).

Can I ask you WHY you choose PSJ? Is it stricly because of Java or is there another reason? I'll be sure to let you know when I have something that is worth-while testing.

[RoboCoder]

@RoboCoder - I have only spent a short time testing PSJ. Mainly to make sure it worked correctly so that I could study the codebase. My immediate goal is to gain a complete understanding of the inner working of Bitcoin (protocols, community, problems, etc). As I'm much stronger in Java than C, PSJ seemed to be the best starting point. BitcoinJ (https://code.google.com/p/bitcoinj/) has also a great codebase to learn from.

As the original author is unreachable, I've opted to start from scratch (learning along the way) in building a fresh JAVA pool server.  I've also been studying Eloipool's codebase (https://gitorious.org/bitcoin/eloipool), which is Python3, and it seems to be pretty solid. I've got a very VERY basic implementation up and running in Java, but its not quite ready for public testing yet.

PSJ gives decent stats on getworks and inound work - but i wish it would give more stats on the shares being tested back to the daemon.  I would actually lilke to see more stats in general by miner made available directly from the management interface.  Would certainly be willing to help test any work you do - and would definitely be willing to contribute funds toward development of stratum support and maybe a management client with stats reporting and more detail/monitoring by worker.

I totally agree, and plan on integrating a Reporting Engine with API support, run by a lightweight web server (lighttpd or similar).

Can I ask you WHY you choose PSJ? Is it stricly because of Java or is there another reason? I'll be sure to let you know when I have something that is worth-while testing.

Howdy!

I choose PSJ primarily because i run windows servers and am not very experienced with the vagaries of Linux - and i can run PSJ (java) on windows pretty easily.  I am come from a different development background for code/web - i am a ms developer so vb and c are my prefered languages and for web scripting (are you ready for this) i am old school cold fusion - been developing in that since version 2 - actually met Jeremy Allaire years ago when he ran the company and i was on a development contract for y2k.gov (done in CF) and Allaire wanted to do a case study on it!   I am WAY out of the normal developer profile for the bitcoin world!

Also C <-> Java is pretty easy cross training.  Also do not have a lot of time to develop large apps so wanted something where the work was already done.  And mining directly against the bitcoind is somewhat unsatisfying as i use bfgminer and the only thing you see is a change in the best share difficultly solved.

I actually had it running with the bitcoin-qt .63 and my miners got shares via longpoll but the hash rate reported by BFG on submitted shares is about 5% lower than when i mine against slush's pool with stratum.

It seems to be working on feeding work to the miners but not really confident that a solution will get back to the daemon and get me the block.

I have not looked at either the bitcoin daemon code or the PSJ code (yet) but am beginning to think the best way to figure out what might be going on is to reverse engineer the code.  But it is soooo time consuming.  Also because my goal was an internal mining "controller" for my own rigs, i think that i should approach it by just developing a scaled down app for my uses.  Decisions, decisions..

RoboCoder

[13MSzfPPr4gXvusKJFAFR2EAN]

Can someone help me with poolserverj sources ?
In the sources which I have are some java files not included but needed.

I am looking for the class or source of com.shadworld.cache.ArrayDequeResourcePool.

Please send it to diamantminer@gmx.de

Please help.

Wily

[sielaeparchen]

I am just examining the poolserverj sources. The first thing which I did was create 2 public repositories of those shadworld.com libraries not included in maven:
Here are the source repositories:
https://github.com/archenroot/shadtools-util
https://github.com/archenroot/shadtools-sql

@Wily
The class ArrayDequeResourcePool.java you are looking for is inside shadtools-util project, you can package and should work, search the repo, it is there

[sielaeparchen]

We are evaluating PoolServerJ for our mining pool, 50btc.com, as replacement for pushpoold. There are few problems we have encountered during testing; can anyone help with them?

We are running Scientific Linux 6.1, java version java-1.6.0-openjdk-1.6.0.0-1.40.1.9.10, poolserverj 0.4.0rc7 (rc2 + rc7 patch), stock bitcoind 0.5.2.

First problem is that currently PoolServerJ doesn't support postgresql properly. For example, with settings

Code:

db.engine=postgresql
db.host=dbserver
db.name=pool
db.schema=public
db.port=5432
db.user=pooluser
db.password=pass

It incorrectly forms connectiong string, it prints
[20:54:18.678] Connecting to DB URL: jdbc:postgresql:pool//dbserver:5432/public?autoReconnect=true
and then always connects to localhost, not "dbserver"

If I understand correctly, specifying connection string in jdbc:postgresql:<database> form can be used only for localhost connections, according to documentation http://jdbc.postgresql.org/documentation/80/connect.html. So jdbc happily ignores dbserver and port, which makes poolserverj connect only to localhost.

We wouldn't mind to fix that issue, but there are no sources for this part of server (shadtools-sql), even in source repository there is only binary .jar. Therefore, we really can't do anything. Currently, for testing we have installed redirecting proxy for postgresql which forwards requests from localhost to real database server, but for production it would be nice to fix that issue properly. This problem is present both in 0.4.0 and git version.

Second problem is that we want users to authorize with any password, as long as they are registered on pool. There is auth engine called AnyPasswordWorkerAuthenticator which supposed to do the trick, but it doesn't do as advertised. Namely, it does allow to log in with any password, but not without password - when logging in with username only (we tried guiminer+poclbm and minerd) it still returns "401 Unauthorized". Of course, it's set up as it's supposed to

Code:

authenticatorEngine=com.shadworld.poolserver.servlet.auth.AnyPasswordWorkerAuthenticator
authenticatorEngine.extraParams=true, false

and I have looked at its simple code a few times but still can't figure out why it won't allow empty password. Could it be that there is a bug in other code which rejects empty password before it's processed by AnyPasswordWorkerAuthenticator?

sources
https://github.com/archenroot/shadtools-util
https://github.com/archenroot/shadtools-sql

[sielaeparchen]

@RoboCoder - I have only spent a short time testing PSJ. Mainly to make sure it worked correctly so that I could study the codebase. My immediate goal is to gain a complete understanding of the inner working of Bitcoin (protocols, community, problems, etc). As I'm much stronger in Java than C, PSJ seemed to be the best starting point. BitcoinJ (https://code.google.com/p/bitcoinj/) has also a great codebase to learn from.

As the original author is unreachable, I've opted to start from scratch (learning along the way) in building a fresh JAVA pool server.  I've also been studying Eloipool's codebase (https://gitorious.org/bitcoin/eloipool), which is Python3, and it seems to be pretty solid. I've got a very VERY basic implementation up and running in Java, but its not quite ready for public testing yet.

PSJ gives decent stats on getworks and inound work - but i wish it would give more stats on the shares being tested back to the daemon.  I would actually lilke to see more stats in general by miner made available directly from the management interface.  Would certainly be willing to help test any work you do - and would definitely be willing to contribute funds toward development of stratum support and maybe a management client with stats reporting and more detail/monitoring by worker.

I totally agree, and plan on integrating a Reporting Engine with API support, run by a lightweight web server (lighttpd or similar).

Can I ask you WHY you choose PSJ? Is it stricly because of Java or is there another reason? I'll be sure to let you know when I have something that is worth-while testing.

do you have some codebase repo? I am examining now java pool, so if you implemented something interesting, let's share.