MySQL Connector/Net problem reusing a pooled connection

MySQL Connector/Net problem reusing a pooled connection

am 15.09.2004 02:13:49 von Svetoslav Milenov

Hi,
I couldn't find any more related to the issue list, so please excuse me if
I'm posting in the wrong place. If this is so, please, tell me where to post
this bug.

Test equipment:
client - MySQL Connector/Net beta 1.0.0, Win2kPro, .Net v. 1.1.
servers:
srv3 - ver. 3.22.32 - this is shipped with AvantGo Server 5.2. for Linux.
srv4 - ver. 4.0.18 on SuSE 9.1

Description of the problem:
When reusing a connection from the pool, reusing fails when against server
version 3.22.32. It works OK with 4.0.18 server.

Expected behavior:
The connection should be reused.

Steps to reproduce / test program:

using System;
using MySql.Data.MySqlClient;

namespace testAG
{
class Class1
{
[STAThread]
static void Main(string[] args)
{
string cs = "Persist Security Info=False;database=Data1;";
cs += "server=" + args[0]
cs += ";user id=root;Password=xxx";

MySqlConnection con = new MySqlConnection(cs);
con.Open();
con.Close();

MySqlConnection con2 = new MySqlConnection(cs);
con.Open();
con.Close();
}
}
}

When executed against srv3, the second Open method throws MySQLException:
Unknown command, with exception.Number 1047.

It seems that the problem is in the Driver.ResetUser() method. It starts a
new packet with a DBCmd.CHANGE_USER as a first byte. After that, when this
packet is send to the server, the response is an error message.

I tried to find if there was (and what) a change in the commands between v.
3.22.5 and 4.0.18, but no success.

I'll be glad to receive either a patch, or at least the commands as they
were implemented in 3.22, so I can change the code myself.

Thanks for reading this

Cheers
Sunny


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: MySQL Connector/Net problem reusing a pooled connection

am 15.09.2004 03:23:23 von Sergei Golubchik

Hi!

On Sep 14, Svetoslav Milenov wrote:
> Hi,
> I couldn't find any more related to the issue list, so please excuse me if
> I'm posting in the wrong place. If this is so, please, tell me where to post
> this bug.

Great that you reported it on http://bugs.mysql.com - it's the
recommended way to report bugs.

Just in case other subscribers may be interested in the same issue:

use http://bugs.mysql.com/5583 to track the progress or the report.

Regards,
Sergei

--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org