MySQL Bugs: #44729: Service Manager uses an http proxy for everything (including jdbc)

Bug #44729	Service Manager uses an http proxy for everything (including jdbc)
Submitted:	7 May 2009 20:37	Modified:	21 Jul 2009 13:54
Reporter:	Diego Medina	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S2 (Serious)
Version:	2.1.0.1036	OS:	Any
Assigned to:	MC Brown	CPU Architecture:	Any

Description:
If you setup the service manager to use an http proxy, all traffic will try to go through the proxy, including the connection to the mysqld server running the repository

How to repeat:
1- Install and start the service manager and agent
2- Setup the Service Manager to use an http proxy (you don't even need a real one, just enter an ip and port number)
3- Restart the service manager
4- monitor the log and you will see errors like

https://intranet.mysql.com/secure/paste/displaypaste.php?codeid=7786

"...
Caused by: java.net.SocketException: Unknown proxy type : HTTP
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:366)
        at java.net.Socket.<init>(Socket.java:209)
        at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:253)
        at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:284)

.."

This should be resolved for the moment by:

revno: 7037
revision-id: jsled@asynchronous.org-20090511181428-9cvmhpt3uc3rcu03
parent: jsled@asynchronous.org-20090511163708-uccya3zl7496mwm5
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Mon 2009-05-11 14:14:28 -0400
message:
  Be specific about which types of URIs we want to proxy for; this is an interim solution, though; we really need to move to Jersey 1.0.3 to set proxies per-connection to get out of this mess.

Though as the comment says, it'd be nice to solve it better.

Patch installed in versions => 2.1.0.1043.

Verified fixed on 2.1.0.1047

An entry was added to the 2.1.0 changelog:

If the Service Manager was set up to use an HTTP proxy, all traffic attempted to go through the proxy, including the connection to the mysqld server running the repository.