Re: MySQL 4.1.22 Sqoop Connector
Posted by: Alexander Soklakov
Date: August 03, 2018 07:59AM

Just tried and I can connect to MySQL 4.1.22 with c/J 5.1.46 and have about 80% connection tests passed.
So the problem, as usual with CommunicationsException, could be a wrong server config or it's port unavailability (firwall etc) or wrong c/J connection string. Could you share these details?
The full stacktrace for CommunicationsException could also help to understand where it came from.

Options: ReplyQuote


Subject
Written By
Posted
Re: MySQL 4.1.22 Sqoop Connector
August 03, 2018 07:59AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.