Bug #23571 missing jamEntry() after EXECUTE_DIRECT in lqh
Submitted: 24 Oct 2006 5:45 Modified: 7 Feb 2007 17:09
Reporter: Stewart Smith Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.13bk OS:
Assigned to: Stewart Smith CPU Architecture:Any

[24 Oct 2006 5:45] Stewart Smith 
Description:
in the below EXECUTE_DIRECT, jam() is called - making trace harder to read when we get back to lqh and execute more jam()

How to repeat:
have a trace with stuff in restore

Suggested fix:
===== dblqh/DblqhMain.cpp 1.125 vs edited =====
--- 1.125/storage/ndb/src/kernel/blocks/dblqh/DblqhMain.cpp     2006-10-24 15:42:45 +10:00
+++ edited/dblqh/DblqhMain.cpp  2006-10-24 15:39:10 +10:00
@@ -7181,7 +7181,7 @@
   TRACE_OP(regTcPtr, "ACC_ABORTCONF");
   signal->theData[0] = regTcPtr->tupConnectrec;
   EXECUTE_DIRECT(DBTUP, GSN_TUP_ABORTREQ, signal, 1);
-
+  jamEntry();
   continueAbortLab(signal);
   return;
 }//Dblqh::execACC_ABORTCONF()
[1 Feb 2007 6:20] 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/19159

ChangeSet@1.2416, 2007-02-01 17:19:19+11:00, stewart@willster.(none) +1 -0
  BUG#23571  	missing jamEntry() after EXECUTE_DIRECT in lqh
  
  add the jamEntry()
[1 Feb 2007 6:29] Stewart Smith 
pushed to 5.1-ndb