I want to enable SSL connections while connecting to MySQL. Ideally my application should through exception because I have still not configured certificates while starting the application. But it is getting successfully restarted and able to connect to DB. I am using MySQL version 8 and spring boot 2.6.
spring.datasource.url=jdbc:mysql://localhost:3306/sms?verifyServerCertificate=true&useSSL=true&requireSSL=true
#spring.datasource.username=root
#spring.datasource.password=root
2022-07-28 16:26:40.659 INFO 15036 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2022-07-28 16:26:40.926 WARN 15036 --- [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2022-07-28 16:26:41.656 INFO 15036 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 9076 (https) with context path ''
2022-07-28 16:26:41.759 INFO 15036 --- [ main] n.j.s.StudentManagementSystemApplication : Started StudentManagementSystemApplication in 5.878 seconds (JVM running for 6.351)
I am currently following along with this document:
https://spring.io/guides/gs/accessing-data-mysql/
and when I build using Gradle, the process does not finish executing.
20-10-11 18:12:09.099 INFO 4584 --- [task-1] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2020-10-11 18:12:09.245 INFO 4584 --- [main] DeferredRepositoryInitializationListener : Spring Data repositories initialized!
2020-10-11 18:12:09.253 INFO 4584 --- [main] c.e.a.AccessingDataMysqlApplication : Started AccessingDataMysqlApplication in 4.295 seconds (JVM running for 4.699)
<=========----> 75% EXECUTING [4m 32s]
I am new to Spring and starting a project from the ground up and do not know where to begin looking to solve this issue.
You are not just building the application - you are actually running it. And since it is a web application, listening to web requests on localhost:8080/demo, it runs until you exit it with ctrl+c.
I am currently learning more about implementing JDBC and using databases in a Spring Boot webapp, and I encountered the following Stack Trace written in the bottom of the post.
I have created a simple Employee model, and I am trying to execute some database code on the same class which my main() lies in. The model and the main class are the only two java files existing in this whole project. I am trying to implement the following run() code that overrides the one from the interface, CommandLineRunner, but I do not get the logs that should come after log.info("Part A:"):
log.info("Part A:")
employees.forEach(employee -> {log.info(employee.toString());
log.info("part a");});
--Things I noticed:
I noticed that the last line of the log before the stack trace starts comes from: "Thread-1" instead of "main". I think that means that a thread from somewhere other than the main encountered an error and closed connection before when it should close normally.
Also, I think that because HikariPool closed before "peer's close_notify", which I presume that it refers to the normal closure of HikariPool, I am not able to see the final bit of logging that I have kept trying to procure. The final bit of logging that I want to see is the logging of the employee that has become inserted into my database.
The final bit of logging that I want to see should be procured from this line of code:
employees.forEach(employee -> {log.info(employee.toString());
log.info("part a");});
--Things to note:
Because of this line in the log, I thought I would see the employee inserted into my database, but when I queried directly on MySQL Command Line Client, it returned an empty set:
2018-11-03 21:08:35.362 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : rows affected: 1
I don't understand why a row has been affected when nothing has been inserted into the database.
The stacktrace and logs: (The stacktrace pasted below actually repeats itself several more times but I cut it off for brevity.)
2018-11-03 21:08:32.997 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : Starting JdbcTest1Application on KitKat with PID 2408 (C:\Users\Nano\Downloads\jdbc-test1\jdbc-test1\target\classes started by Nano in C:\Users\Nano\Downloads\jdbc-test1\jdbc-test1)
2018-11-03 21:08:33.003 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : No active profile set, falling back to default profiles: default
2018-11-03 21:08:33.770 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : Started JdbcTest1Application in 1.024 seconds (JVM running for 1.778)
2018-11-03 21:08:33.770 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : Creating tables
2018-11-03 21:08:33.770 INFO 2408 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2018-11-03 21:08:34.082 INFO 2408 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2018-11-03 21:08:35.135 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : Inserting Baggins Hopkins
2018-11-03 21:08:35.362 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : rows affected: 1
2018-11-03 21:08:35.362 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : Querying for employee
2018-11-03 21:08:36.065 INFO 2408 --- [ main] c.j.jdbctest1.JdbcTest1Application : Part A:
2018-11-03 21:08:36.065 INFO 2408 --- [ Thread-1] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated...
Sat Nov 03 21:08:36 KST 2018 WARN: Caught while disconnecting...
EXCEPTION STACK TRACE:
** BEGIN NESTED EXCEPTION **
javax.net.ssl.SSLException
MESSAGE: closing inbound before receiving peer's close_notify
STACKTRACE:
javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129)
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:308)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:255)
at java.base/sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:645)
at java.base/sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:624)
at com.mysql.cj.protocol.a.NativeProtocol.quit(NativeProtocol.java:1312)
at com.mysql.cj.NativeSession.quit(NativeSession.java:182)
at com.mysql.cj.jdbc.ConnectionImpl.realClose(ConnectionImpl.java:1750)
at com.mysql.cj.jdbc.ConnectionImpl.close(ConnectionImpl.java:720)
at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:135)
at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:441)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
** END NESTED EXCEPTION **
The Java Code:
#SpringBootApplication
public class JdbcTest1Application implements CommandLineRunner {
private static final Logger log = LoggerFactory.getLogger(JdbcTest1Application.class);
#Autowired
JdbcTemplate jdbcTemplate;
public static void main(String[] args) {
SpringApplication.run(JdbcTest1Application.class, args);
}
#Override
public void run(String... args) throws Exception {
log.info("Creating tables");
jdbcTemplate.execute("DROP TABLE IF EXISTS employees");
jdbcTemplate.execute("CREATE TABLE employees (emp_id int, name varchar(100), role varchar(100), status varchar(100))");
log.info("Inserting Baggins Hopkins");
int rowsAffected = jdbcTemplate.update("INSERT INTO EMPLOYEE(EMP_ID, NAME, ROLE, STATUS)"
+ " VALUES(1,'Baggins Hopkins','thief','WORKING')");
log.info("rows affected: "+ Integer.toString(rowsAffected));
log.info("Querying for employee");
String sql = "SELECT emp_id,name,role,status FROM employees";
List<Employee> employees = jdbcTemplate.query(sql,(rs, rowNum)->
new Employee(rs.getInt("emp_id"), rs.getString("name"),
rs.getString("role"),Status.valueOf(rs.getString("status"))));
log.info("Part A:");
employees.forEach(employee -> {log.info(employee.toString());
log.info("part a");});
}
}
Also just in case this matters, I pasted this code from application.properties:
spring.datasource.url=jdbc:mysql://localhost:3306/employee_database
spring.datasource.username=employee
spring.datasource.password=employee
spring.datasource.driver-class-name=com.mysql.cj.jdbc.Driver
The SSL connection to the database is failing, try changing your datasource URL to:
spring.datasource.url=jdbc:mysql://localhost:3306/employee_database?useSSL=false
The warning looks like a MySQL driver bug with Java 11 and SSL enabled : https://bugs.mysql.com/bug.php?id=93590
Deactivating encryption because of a driver warning is a bad idea.
Your insertion problem looks more like a classic transaction issue though, I doubt it is related to the SSL warning.
This Worked for me
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<scope>runtime</scope>
<version>8.0.20</version>
</dependency>
I also faced the same issue.
if you look the the stacktrace, it's cleary mentioned what to do -
Sat Mar 16 09:00:01 IST 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'.
You need either to explicitly disable SSL by setting **useSSL=false**, or set **useSSL=true** and provide truststore for server certificate verification.
so after disabling the ssl by making changes in data source url solved the problem -
spring.datasource.url=jdbc:mysql://localhost:3306/security?useSSL=false
To solve this problem, it took me about three days.
(Edit: This is a workaround for testing and not actually a solution.)
At first, I started solving the problem from trying to configure my own SSL for mysql, and I spent quite a few hours on that. Too much time had passed until I realized configuring it had to do with Cmake and C++, which made me give up. It was very frustrating. However I did not give up and tried to disable SSL entirely through a method that hasn't been found. And I eventually did find the method. Here it is:
You have to use the legacy password for MySQL. The legacy password is the way MySQL authenticated things in version 5.7x.
Open up the MySQL installer again, and reconfigure the MySQL Server settings.
When you get there you will see this screen:
The screen that you should get to
You might get some errors when reaching the final stage of the reconfiguration:
I had problems at the final stage I had no idea how to fix so I uninstalled MySQL altogether. I use windows. I deleted the MySQL project root directory from Program Files to uninstall MySQL. I also deleted the databases saved in Program Data (a hidden folder in the C Drive) because I wanted to start afresh(WARNING: this will delete all your previously saved data!). Uninstalling MySQL from the control panel might not be enough to completely erase MySQL from your computer.
Delete all *.pem files in C:\ProgramData\MySQL\MySQL Server 8.0\Data. (or move it somewhere else, which is what I did)
You might not see ProgramData in the C Drive. That is because it is a hidden folder. In order to see hidden folders:
search for folder options in the control panel.
Go to view.
Under 'Advanced settings' and under 'Hidden files and folders' of that, click "Show hidden files, folders, and drives."
Go to C:\ProgramData\MySQL\MySQL Server 8.0 and open my.cnf (or my.ini). Add the following line after [mysqld]:
ssl=0
Then save. It should work now.
References:
https://community.atlassian.com/t5/Confluence-questions/MySQL-Public-Key-Retrieval-is-not-allowed/qaq-p/778956
https://scalegrid.io/blog/configuring-and-managing-ssl-on-your-mysql-server/
My similar problem in a tomcat trying to conect via ssl to Aurora mysql (AWS)
I solved the problem by updating the driver version from 'mysql-connector-java-5.1.40.jar' to 'mysql-connector-java-5.1.49.jar', and installing a root CA into ceacerts:
keytool -import -trustcacerts -file rds-ca-2019-root.pem -keystore /<your_java_home>/lib/security/cacerts
Hope be use to you
Try using the following URL. As they suggested use useSSL=false Also, Make sure to use <&> instead of just & when you have multiple properties defined in your URL.
jdbc:mysql://localhost:3306/TestDB?serverTimezone=PST&useSSL=false
I was also facing the same issue
But then i updated the mysql-connector-java version from 5.1.46 to 8.0.20 and by changing com.mysql.jdbc.Driver to com.mysql.cj.jdbc.Driver
it solved my issue
My similary prolem is in spark,
I solove the problem by down the java verion from
'openjdk version "1.8.0_275"' to 'openjdk version "1.8.0_265"',
hope be use to you
I had this issue and decided to use Carrier Pigeon Protocol's solution until I accidentally solved it by updating Tomcat from version 9.0.12 to 9.0.16.
I faced a similar issue when I upgraded the Java version in my server to 11 from 8.
The spring boot started supporting Java 11 from 2.1 and onwards. So make sure your project's dependencies are also updated accordingly. This is relevant for this answer as SpringBoot also influence MySQL connector, Hibernate core, and other dependencies.
The inability to connect to DB was resulting in some more NoClassDefFoundErrors. So make sure you solve this first before looking into other errors.
An example pom dependency for the SpringBoot starter
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.1.12.RELEASE</version>
<relativePath />
</parent>
Hope this helps someone.
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: name-unit] Unable to build Hibernate SessionFactory
I had exactly the same problem, I also modified a false my useSSL like this useSSL=false and it works fine.
I think for those who use intelliJ ultimate the error the problem does not arise. But for those who use the community version "yes" also for those who are on netbeans like my case. This concerns the management of persistence.xml files and the EntityManagerHolder file
Rather than disabling SSL/TLS I appended the following to the database connection string: &enabledTLSProtocols=TLSv1.2
Setup : HDFS --- Cluster (1-master ,2 Slaves) Druid --- Cluster (1-(zk,coordinator,overload),1-(historical,middile manager),1-(broker))
Version using for Druid : imply-2.3.9,HDFS : 2.7.3
common.runtime.properties for druid :For HDFS:
druid.storage.type=hdfs
druid.storage.storageDirectory=http://hadoopmachince:9000/druid/segments
When i posted task to http://druidip:port/druid/indexer/v1/supervisor for creating datasource . Task get failed with below exception.
Error Stack Trace :
1)Error injecting constructor, java.io.IOException: No FileSystem for scheme: http
at io.druid.storage.hdfs.HdfsDataSegmentPusher.(HdfsDataSegmentPusher.java:63)
while locating io.druid.storage.hdfs.HdfsDataSegmentPusher
at io.druid.storage.hdfs.HdfsStorageDruidModule.configure(HdfsStorageDruidModule.java:97) (via modules: com.google.inject.util.Modules$OverrideModule -> io.druid.storage.hdfs.HdfsStorageDruidModule)
while locating io.druid.segment.loading.DataSegmentPusher annotated with #com.google.inject.multibindings.Element(setName=,uniqueId=152, type=MAPBINDER, keyType=java.lang.String)
Need to change from http to hdfs
common.runtime.properties for druid :For HDFS:
druid.storage.type=hdfs druid.storage.storageDirectory=hdfs://hadoopmachince:9000/druid/segments
I am using qemu-kvm on a CentOS 6.6 node. For no apparent reason, this node rebooted during the night, and the virtual machines did not automatically start at boot time.
I am trying to start the machine and I get this error :
# start srv50
error: Failed to start domain srv50
error: internal error problem reading /sys/devices/system/node/node0: No such file or directory
I tried to check whether /sys/devices/system/node/node0 was accessible and it seems to be :
drwxr-xr-x 3 root root 0 Sep 12 08:22 /sys/devices/system/node/node0
Here is the libvirt log file :
2015-09-12 07:47:43.039+0000: 2933: info : libvirt version: 0.10.2, package: 54.el6 (CentOS BuildSystem <http://bugs.centos.org>, 2015-07-24-04:48:57, c6b9.bsys.dev.centos.org)
2015-09-12 07:47:43.039+0000: 2933: info : virNetlinkEventServiceStart:517 : starting netlink event service with protocol 0
2015-09-12 07:47:43.040+0000: 2933: info : virNetlinkEventServiceStart:517 : starting netlink event service with protocol 15
2015-09-12 07:47:43.044+0000: 2945: info : dnsmasqCapsSetFromBuffer:667 : dnsmasq version is 2.48, --bind-dynamic is NOT present, SO_BINDTODEVICE is NOT in use
2015-09-12 07:47:43.045+0000: 2945: info : networkReloadIptablesRules:1980 : Reloading iptables rules
2015-09-12 07:47:43.094+0000: 2945: info : networkRefreshDaemons:1342 : Refreshing network daemons
2015-09-12 07:47:43.095+0000: 2945: info : virStorageBackendVolOpenCheckMode:1093 : Skipping special dir '..'
2015-09-12 07:47:43.095+0000: 2945: info : virStorageBackendVolOpenCheckMode:1093 : Skipping special dir '.'
2015-09-12 07:47:43.095+0000: 2945: info : virStorageBackendVolOpenCheckMode:1093 : Skipping special dir '..'
2015-09-12 07:47:43.095+0000: 2945: info : virStorageBackendVolOpenCheckMode:1093 : Skipping special dir '.'
2015-09-12 07:47:43.223+0000: 2945: info : qemudLoadDriverConfig:443 : Configured cgroup controller 'cpu'
2015-09-12 07:47:43.223+0000: 2945: info : qemudLoadDriverConfig:443 : Configured cgroup controller 'cpuacct'
2015-09-12 07:47:43.223+0000: 2945: info : qemudLoadDriverConfig:443 : Configured cgroup controller 'cpuset'
2015-09-12 07:47:43.223+0000: 2945: info : qemudLoadDriverConfig:443 : Configured cgroup controller 'memory'
2015-09-12 07:47:43.223+0000: 2945: info : qemudLoadDriverConfig:443 : Configured cgroup controller 'devices'
2015-09-12 07:47:43.223+0000: 2945: info : qemudLoadDriverConfig:443 : Configured cgroup controller 'blkio'
2015-09-12 07:47:43.225+0000: 2945: error : virNodeParseNode:263 : problem reading /sys/devices/system/node/node0: No such file or directory
2015-09-12 07:47:43.225+0000: 2945: warning : qemuCapsInit:880 : Failed to get host CPU
2015-09-12 07:47:43.347+0000: 2945: info : virDomainLoadAllConfigs:15374 : Scanning for configs in /var/run/libvirt/qemu
2015-09-12 07:47:43.354+0000: 2945: info : virDomainLoadAllConfigs:15374 : Scanning for configs in /etc/libvirt/qemu
2015-09-12 07:47:43.354+0000: 2945: info : virDomainLoadAllConfigs:15396 : Loading config file 'srv50.xml'
2015-09-12 07:47:43.355+0000: 2945: info : virDomainLoadAllConfigs:15396 : Loading config file 'srv51.xml'
2015-09-12 07:47:43.355+0000: 2945: info : qemuDomainSnapshotLoad:494 : Scanning for snapshots for domain srv51 in /var/lib/libvirt/qemu/snapshot/srv51
2015-09-12 07:47:43.355+0000: 2945: info : qemuDomainSnapshotLoad:494 : Scanning for snapshots for domain srv50 in /var/lib/libvirt/qemu/snapshot/srv50
2015-09-12 07:47:43.378+0000: 2945: info : lxcSecurityInit:1380 : lxcSecurityInit (null)
2015-09-12 07:47:43.378+0000: 2945: info : virDomainLoadAllConfigs:15374 : Scanning for configs in /var/run/libvirt/lxc
2015-09-12 07:47:43.378+0000: 2945: info : virDomainLoadAllConfigs:15374 : Scanning for configs in /etc/libvirt/lxc
I tried to upgrade CentOS to the latest version, as this reset libvirtd configuration, but I still get the same errors.
How can I start those virtual machines and what's wrong with the node files ?
Your server may be compromised, according to some similiar cases recently.
You should check your /etc/rc.local to see if anything added like _-pud and _-minerd. If they are exist then you are one of the victims.
To get your VMs back, you need to remove those files:
/usr/bin/_-minerd
/usr/bin/_-pud
/usr/bin/_-config
/etc/ld.so.preload
/lib64/libncom.so.4.0.1
/tmp/initramfs.*/lib64/libncom.so.4.0.1
And don't forget to remove those two lines in /etc/rc.local:
nohup /usr/bin/_-pud 119.78.232.8 >/dev/null
nohup /usr/bin/_-minerd -c /usr/bin/_-config 2> /dev/null&
VMs should be up and running at your next reboot.
Please remember to check if your IPMI or iDRAC is accessible from the Internet, this issue is caused by vulnerabilities in the IPMI firmware. Update to a new version of firmware is recommended.
References:
http://www.webhostingtalk.com/showthread.php?p=9534226
http://www.webhostingtalk.com/showthread.php?t=1512831