This, I thought would be easy, but it turns out it is not. Below is my my.ini file (Since windoze do not have a my.conf file):

#This File was made using the WinMySQLAdmin 1.4 Tool
#11/9/2002 12:12:15 PM

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
basedir=C:/mysql
#bind-address=**.***.***.**
datadir=C:/mysql/data
#language=C:/mysql/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=C:/mysql/bin/mysqld-nt.exe
user=******
password=******


You will notice that it is pretty much straight out of the box configuration.

The problem is... once you run ONE select query against it, mysql will refuse to respond to that query, instead, it will fill up it's connection pool with fake connections, then return a response "connection pool full". Which is purely bs.

Anybody have a fix for this? All clean installs result in the same fake error.

mysql is the best open source project out there with the fastest data access speed. On top of that, it is free.

Your problem is not mysql, it's ur win-ddos server.

Funny, maybe next time you check your intelligance at the door, you will learn how to post?

Enough with the sarcasm, next time, tell the truth.

You do know that 4.0.15 has been released?

Yep, it doesnt fix the pooling bug. I may end up downgrading to 3.x, never had a problem with it, but figured the catching among other things would be quite helpful in 4.x.

I think I'll do that as 4.x is too unstable for any kind of production use.

Pfff, and you expect to be helped?

lol, not by hijackers and peeps who lie. Ie blame the windows box? lol, funny

Looks like data providers can create such bugs as well. ByteFX just sucks.


been edited, because I have horrible spelling:)

Maybe mySQL was not meant to be run on a WIN box after all

What are you using for:

bind-address=**.***.***.**

localhost
127.0.0.1
IP?

Are you running the select statement remotely or locally?
Do you have a DNS server/client running in that box?

Albo

lol

Problem has been narrowed down to the lame data provider ByteFx

Also, you will notice that the bind address is commented out, thus not used.

All queries are local.

On a side note, last night my wife and I bought a brand new 2003 car. heh. So I won't be doing much programming for awhile.