Bug #46095 Incorrect nil value on read_query_result (Agent bug)
Submitted: 9 Jul 2009 17:12 Modified: 20 Aug 2009 17:47
Reporter: Diego Medina Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Agent Severity:S2 (Serious)
Version: OS:Any
Assigned to: Jan Kneschke CPU Architecture:Any

[9 Jul 2009 17:12] Diego Medina
There are times when the proxy returns nil values, even though the mysql server sent an actual value on the resultset.

This is a dup of bug#35729 

How to repeat:
1- Start the proxy that comes with the MySQL Monitor Agent like this

./bin/mysql-proxy --proxy-lua-script=trunk/tests/suite/base/t/bug_35729-test.lua \

--proxy-backend-addresses= \

(Using the test case that is on the proxy gpl code)
2- On another terminal, just connect through port 4040 and send one query 


3- On the terminal where you started the proxy, you will see this message:

(critical) (read_query_result) [string "/Users/wizard/etools/mysql-gpl-proxy/local-..."]:30: assertion failed!
[22 Jul 2009 19:52] Enterprise Tools JIRA Robot
Jan Kneschke writes: 
a patch for it is in the mysql-proxy tree already. We just have to merge it over and test it.
[3 Aug 2009 16:03] Enterprise Tools JIRA Robot
Jan Kneschke writes: 
r1463..1468 contains the same (adapted) code as the gpl-proxy now.
[11 Aug 2009 14:20] Enterprise Tools JIRA Robot
Keith Russell writes: 
Patch installed in version =>
[12 Aug 2009 19:01] Enterprise Tools JIRA Robot
Diego Medina writes: 
Verified fixed on
[20 Aug 2009 17:47] MC Brown
A note has been added to the 2.1.0 changelog: 

The MySQL Enterprise Monitor Agent could return a null value for a valid result set, resulting in incorrect results when using Query Analyzer.