New versions of JP did not appear for a long time. Once again I have difficulty with the work JetProfiler.
You wrote (http://www.jetprofiler.com/forum/discussion/22/connection-via-proxy/)
* Bjorn admin * CommentTimeSep 21st 2009
"Hi and thanks for the input!
There's currently a long delay in trying to check for software upgrades which takes up to 5 minutes to complete. This is due to a high default connect-timeout value. Is this the problem you are experiencing?
In the coming release, it's been lowered to 5 seconds. So even if there is no option to disable check of upgrades, at least you will not have to wait more than five seconds.
Proxy support is on the roadmap, but no date has been decided. "
1) The proxy did not appear until now. 2) 5 seconds for the timeout has been lacking in the current working environment.
Now more about the problem: I use JetProfiler for monitoring. HeidiSQL - to develop. On 19 November I was not able to connect via JetProfiler to the base. Error:
"There was an error trying to connect to the target database. Connected, but failed to log in. Read timed out "
HeidiSQL connects for about 15 seconds. Then he starts to work at normal speed. The timeout may be related to increased load on the site. Or the fact that the database is in the data center, but I'm working from the office.
Explicitly, the problem JetProfiler in the timeout for the login. Through a GUI setting is not available. What can I do to change this setting?
I hope that this problem you will help me to decide as soon as possible. JetProfiler stopped working just when we need to upgrade the database schema and data monitoring would be very valuable.
thanks for the input! The 5 minutes hang-up was supposedly fixed in version 1.0.5, released on 2009-10-22. What problems are you seeing?
JP login timeout is 10 seconds. Unfortunately, this is not configurable at all. But it sounds strange that you need 15 seconds to connect. MySQL is usually very fast when it comes to accepting connections - unless you have reverse dns lookup enabled (I'm assuming you have not). More likely, the delay is caused by the fact that the database is in the datacenter. May I suggest that you open an ssh tunnel from your computer to the datacenter:3306 and try to connect through it instead? Any delays caused by the network equipment/firewalls might be solved that way, since the physical connection has already been approved.
Also, can you try to connect from the command line instead of using Jet Profiler? And also do that straight from the machine in the data center? Try to determine where the delay is. Once you are connected to the database, I'm assuming you don't notice any significant delays (e.g. > 200ms).
> JP login timeout is 10 seconds. Unfortunately, this is not configurable at all. That sounds bad ...
All resolved reboot the server at the datacenter. For 5 months caches and / or a memory leak took almost all 64 GB of RAM and started swapping, which led to this effect a long connection from the outside.