Issues with call to procedures.

[odederner1]

The version of OS and ProxySQL: RedHat, Proxysql 2.0.4-116

we have calls to stored procedures.
procedures are returning a parameter to Node JS application via: select my_var
in procedure body
it seems that in this way data doesn't flow constantly via proxysql.

Does ProxySQL supports returning parameter value via procedure body?
Does it take any setup to reach this?

here is how it looks when running from console:

1. it always ends with Lost connection.
2. some times it will never get result set back.

MySQL [aws]> call decrypt.test_2('hello');
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 28
Current database: aws

+--------+
| i_name |
+--------+
| hello |
+--------+
1 row in set (0.01 sec)

ERROR 2013 (HY000): Lost connection to MySQL server during query
MySQL [aws]> call decrypt.test_2('hello');
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 29
Current database: aws

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 30
Current database: aws

ERROR 2006 (HY000): MySQL server has gone away
MySQL [aws]> call decrypt.test_2('hello');
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 31
Current database: aws

+--------+
| i_name |
+--------+
| hello |
+--------+
1 row in set (0.01 sec)
ERROR 2013 (HY000): Lost connection to MySQL server during query
MySQL [aws]> call decrypt.test_2('hello');
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 32
Current database: aws

[odederner1]

Hi Hardy, thanks very much to notify me. Do you know if this issue is new to version > 2 ? In other words is the same bug found with 1.x versions? Thanks much,Oded.

…

On Wed, May 15, 2019 at 10:33 AM Hardy ***@***.***> wrote: I have the same issue. and same to issue #1903 <#1903>. ProxySQL version v2.0.4-2-g7274fe2_DEBUG — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2057?email_source=notifications&email_token=AI7LL7VZPPLUAYNFYC5KAJTPVO4FPA5CNFSM4HM2WZZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNY4LI#issuecomment-492539437>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI7LL7V4IWW5VSKN2U2XNNLPVO4FPANCNFSM4HM2WZZA> .

[renecannao]

Closing this one, and following on #2059 that has a clear reproducible test case