forums › forums › SQLyog › Using SQLyog › Can Not Connect To Some Server With Enterprise 5.2
- This topic is empty.
-
AuthorPosts
-
-
November 23, 2006 at 8:45 pm #10044kasiMember
I just upgraded to Enterprise 5.2:
I can not connect to 2 Servers using HTTP-Tunnel.
When I do Test Connection it is show 'Connection successful ' with the right MySQL Verson,
but when I try to Connect it shows me 'Error No. 3 SQLyog Enterprise tunne …'
showing TunnelVersion:5.2
I have seen that you use Connection:keep-alive in the request. Is it possible, that it is not working when the Server closes the connection? I don't have access to the Apache configuration at the moment, so I can not check the settings.
Thanks
KASI
-
November 24, 2006 at 5:36 am #22974peterlaursenParticipant
There is no (intentional) change in any such functionality introduced with 5.2.
Please answer:
1) Your are perfectly sure that this problem occured the very same moment as you upgrade?
2) What was the version that you used before?
-
November 24, 2006 at 5:19 pm #22975kasiMemberpeterlaursen wrote on Nov 24 2006, 06:36 AM:Please answer:
1) Your are perfectly sure that this problem occured the very same moment as you upgrade?
2) What was the version that you used before?
Yes I am shure. I had the same problem with that server when upgrading to version 5.17, so I switched back to version 5.13
Just reinstalled version 5.13 and it works.
version 5.13 works fine
version 5.17 no Test Connection and no Connection
version 5.2 Test Connection ok Connection fails
it is not the connection:keep-alive thing, this has been changed
any ideas ??
thanks
KASI
-
November 24, 2006 at 11:20 pm #22976kasiMember
I guess I found the problem.
Version 5.2 uses multiple connections to the webserver simulatinously and that is not allowed there.
I again checked version 5.13 and it uses only 1 connection. So something must have been changed between this version.
Question now is why does SQLyog do that and how can I change that??
thankes
kasi
-
November 27, 2006 at 8:08 pm #22977kasiMember
Now I found the problem.
For reasons I don't know the webserver sends a newlinw char before each content: So you can reproduce my error, when you insert a “echo chr(10);” at the beginning of the Tunnel-script.
It looks like that the connection that asks for the tunnel-version, doing a
“POST /SQLyogTunnel.php?app=sqlyog&version=5.2 HTTP/1.0” and receiving a
“
-