Upgrade Mysql-connector-java
Fanny Lococo
So I replaced the mysql-connector-java file with an older version (8.0.15), but when I go to CF admin settings page and look at CF Server Java Class Path, it still lists the newer version (8.0.25). And I did confirm the location of the file. I have restarted CommandBox and even my laptop, just in case.
After updating Confluence to version 7.4.17 to resolve the vulnerability CVE-2022-26134, we get the error message "Database connection failed." We've downloaded mysql-connector-java-5.1.48-bin.jar and placed it in /WEB-INF/lib/ and restarted Confluence, but the issue persists. We've made sure MySQL is running on the server and that we can log into the database with the credentials specified in confluence.cfg.xml.
1. What is the problem? Be very detailed.
I was running ODK Aggregate in AWS (EC2 + RDS.MySQL). Amazon pushed me to upgrade the MySQL version from 5.6.44 (EOL) to 5.7.33. After upgrading the JDBC connection started to fail:
3. What you have you tried to fix the problem?
Researching much on forums I found that this could be a problem of the connector version (although I'm not sure). So I tried to update to mysql-connector-java-8.0.25.jar.
Database: We've found an error in MySQL supported version!
The database type in your dbconfig.xml is set up to MySQL 5.7 and your MySQL version is different. Consider using MySQL 5.7 database type instead
See our documentation for more information on changing database type.
Although this seemed to be supported and was working fine with the 5.7 MySQL I decided to upgrade it to the 'latest' connector. This wasn't very straightforward as the connectors no longer seem to be individual downloads, so I had to download the whole latest MYSQL build (450MB) 8.0.28.MSI and add the Connector/J.
So adding Connector/J 8.0.28 installed into C:\Program Files (x86)\MySQL\Connector J 8.0. I copied the .jar file into the JIRA Lib location, and tried the config.bat again - still no joy. At this time I had both the 5.1.49 and 8.0 Java connectors in the directory, so I decided to move the 5.1.49.jar files out of the directory.
Now I was sure I had basic connectivity, I focused on the C:\Program Files\Atlassian\Application Data\JIRA\dbconfig.xml file. I suspected the changes described in -mysql-connection-url-for-jira-server-874744240.html may be needed, as I had tried this before the connector upgrade.
I suspect the main cause is the change from Java 8 running on the previous release to Java 11 running in the new LTS release is somehow incompatible with the mysql-connector-java-5.1.49.jar but am no expert in this area !
What I can tell you is connector/J 8.0.28 and changes to the dbconfig.xml file both were needed to get it working again, and hope this helps someone else get back and running after an LTS upgrade on Windows with MySQL 5.7 quicker than I did !
Sorry for not getting back with feedbacks during this week, but my environment was very unstable and I had to rebuild it on AWS. I have done the driver installation again: tar zxf /usr/mysql-connector-java-5.1.38.tar.gz. Then I realize that i still have the old version mysql-connector-java.jar under /usr/share/java. I then I want to copy the new file from /usr/mysql-connector-java-5.1.38 into the java folder but I realize that this is the file I have there: -rw-r--r--. 1 root root 983914 Dez 2 03:02 mysql-connector-java-5.1.38-bin.jar
I then copy it to /usr/share/java. I change it permissions with chmod 644 and try the sqoop command and get the same errors. Then I change the file name from mysql-connector-java-5.1.38-bin.jar into mysql-connector-java-5.1.38.jar and remove the mysql-connector-java.jar and keep having the same error.
Yes, for Mysql-5.5 and higher your need the latest version of mysql-connector and it cannot be installed using yum, download it from here. After installing it retry sqoop. Also on HDP Sandbox add "--driver com.mysql.jdbc.Driver" to your sqoop command.
Thank you guys. I downloaded and install the connector (tar zxf mysql-connector-java-5.1.38.tar.gz). Then add the --driver and parameters at the sqoop import command. Here is the errors I am getting now:
I updated the connector to mysql-connector-java-8.0.21.jar and it worked again. Now Java has updated to 8u261 and I have the same error again, but there is no new version of the JDBC driver.
The highest supported version of MySQL that the Percussion supports for this install/upgrade is MySQL 5.7. There are still several open issues that block upgrade / install with MySQL 8.0. These will be addressed in future updates.
You can use a system package manager to keep the jar up to date, just be sure that the 5.1.x version is installed. You would then use a symbolic link from mysql-connector.jar in the above locations to the copy of the jar maintained by your systems package manager.
During the upgrade, the system will modify the backend database schema with new changes and indexes. The latest version of the MySQL Connector supports new attributes including support for SSL/TLS encryption of the connection to the MySQL Server.
I am installing Ignition 8.1.xx on a Red Hat Enterprise Linux 8.5 server. When I attempt to make a database connection to my MySQL database I get an error that connector files are missing. I believe the missing file is mysql-connector-java-8.0.29-1.e18.noarch.rpm. When I proceed to install this file I get the following error:
MySQL Connector/J 8.1 supersedes the 8.0 series and is recommended for use on production systems. It is highly recommended for use with MySQL Server 5.7 and up. Please upgrade to MySQL Connector/J 8.1.
However, I got it to work and for documentation reasons (at least I didn't find any suitable instructions for loading drivers) I outline what exactly I did (also to assure that I did the right thing):
To your question: I think the hint was to use the 5.1.49 drivers and somewhere deep in the instruction it said that you only can use version 5.1. Below are the steps I did ... please tell me if I did something wrong or unnecessary.
For what you say, seems that you installed the "PDI MySql Plugin". To be honest, I've never had the need to use it but I assume that the only thing you'd need is to delete the prior "mysql-connector-java-5.1.23.jar" and replace it with the new "mysql-connector-java-5.1.49.jar" (don't copy the "-bin" jar as it can give you some problems).
Guacamole supports MySQL authentication through an extension available from the project website. This extension allows users and connections to be managed from within the web application. Unlike the default, XML-driven authentication module, all changes to users and connections take effect immediately; users need not logout and back in in order to see new connections.
The official MySQL authentication also supports load balancing through the use of "balancing groups". When a balancing group is created, it can be used like any other connection, but will use the least used of its underlying connections, spreading load evenly across any connections contained within.
The contents of lib/ must be copied into the classpath of Guacamole, which is the directory specified by the lib-directory property in guacamole.properties. If this property is not specified, simply add it. On Linux servers, /var/lib/guacamole/classpath is a good choice, but it can be whatever you like.
Each of the .jar files above is either the MySQL authentication module itself (guacamole-auth-mysql-0.8.0.jar) or a dependency. They must all be placed in Guacamole's lib-directory for the MySQL authentication to work.
If you do not see mysql-connector-java-5.1.23-bin.jar (or a similar file with a different version) present in the same directory as the other .jar files, then you have not copied MySQL Connector-J properly.
Be sure to download MySQL Connector-J from the MySQL website. Extract the downloaded archive, and copy the .jar file into the same directory as shown above. If this is not done, MySQL authentication will not work. Guacamole will be unable to connect to your MySQL database.
The MySQL authentication module will need a database to store all authentication data and a user to use only for data access and manipulation. You could use an existing database and existing user, but for the sake of simplicity and security, these instructions assume you will be creating a new database and new user that will be used only by Guacamole and only for this authentication module.
At this point, you need MySQL installed and the root MySQL user configured. If this is not the case, install MySQL now. Most distributions will provide a convenient MySQL package which will set up everything for you, including the root user. After MySQL is installed, create the new database and user:
The database and user can be named whatever you like, but these instructions will refer to both as "guacamole". Naturally, you should choose a real password for your user rather than the string "some_password" shown above.
The SQL scripts that create the database schema and default administrator user are included in the archive you downloaded within the schema/ directory. They are named such that they can be run in order with one command:
d3342ee215