Description of problem: There is no validation of the DB connectivity properties that the user enters into the installer. If there is an error or typo in the DB URL, username, etc. then the user will not be informed until the end of the installation. Can we add a 'connection test' feature such as is provided by the JON installer? Version-Release number of selected component (if applicable): ER4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
With out this type of built in test tool, users can mis-type a DB URL and then have to re-run the entire installation when it fails: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any pack ets from the server. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java: 45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:409) at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1122) at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:344) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2181) ... 26 more Caused by: java.net.UnknownHostException: localost: Name or service not known at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:894) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1286) at java.net.InetAddress.getAllByName0(InetAddress.java:1239) at java.net.InetAddress.getAllByName(InetAddress.java:1155) at java.net.InetAddress.getAllByName(InetAddress.java:1091) at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:246) at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:293) ... 27 more
This type of validation has been added to the post-beta installer: When the user clicks next, their connection will be tested (not optional.) They will be warned about the status of this connection (failure, missing driver, etc) and allowed to continue (perhaps they can correct the problem immediately outside the installer). Let me know if this isn't sufficient.
verified in ER7