| Bug #37845 | NDBJ Connectors | ||
|---|---|---|---|
| Submitted: | 3 Jul 2008 18:01 | Modified: | 21 Sep 2009 9:37 |
| Reporter: | Richard Hickson | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | Connectors: NDB/Bindings | Severity: | S3 (Non-critical) |
| Version: | ndb-bindings-0.6.2 | OS: | Linux |
| Assigned to: | Monty Taylor | CPU Architecture: | Any |
[17 Apr 2009 17:39]
Richard Hickson
Monty (or NDBJ developer), is this still a problem for NDB-J connectors? Thanks Rich

Description: The following error is reported when 1 node of a 4-node cluster has been taken out of service (JDBC programs work without an issue): Exception in thread "main" Cluster was not ready at com.mysql.cluster.ndbj.ndbjJNI.NdbClusterConnectionImpl_waitUntilReady (NativeMethod) at com.mysql.cluster.ndbj.NdbClusterConnectionImpl.waitUntilReady (NdbClusterConnectionImpl.java:82) at com.alcatel_lucent.payment.CallGen.CallGen.main(CallGen.java:165) How to repeat: 1) Create 4-node system 2) Take one node out of service 3) Start NDB Connectors program. Previous error reported. 4) Start JDBC program, no problems. 5) Bring node back online 6) Start NDB connectors program, no issues. Suggested fix: Unknown