| Bug #28376 | garbled error code when doing NdbEventOperation::execute() | ||
|---|---|---|---|
| Submitted: | 11 May 2007 13:43 | Modified: | 15 May 2007 6:57 |
| Reporter: | Tomas Ulin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Tomas Ulin | CPU Architecture: | Any |
[11 May 2007 16:06]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/26497 ChangeSet@1.2143, 2007-05-11 16:45:52+02:00, tomas@whalegate.ndb.mysql.com +1 -0 Bug #28376 garbled error code when doing NdbEventOperation::execute() - make sure correct error code is set in SUB_START_REF
Description: NdbEventOperation::execute() may get garbled error message when failing. How to repeat: e.g. try execute while cluster is starting up you may get bad error message instead of the 1421 you're supposed to get can be forced by inserting delay code in ndbd Suggested fix: make sure to set the correct error code... void Dbdict::completeSubStartReq(Signal* signal, .... SubStartRef* ref = (SubStartRef*)signal->getDataPtrSend(); ref->errorCode = subbPtr.p->m_errorCode; sendSignal(subbPtr.p->m_senderRef, GSN_SUB_START_REF, signal, SubStartRef::SignalLength, JBB);