B4J Question [Solved][Server] Warning when using mysql-connector-java-5.1.49-bin

[aeric]

When I develop B4J server locally, I set

#AdditionalJar: mysql-connector-java-5.1.49-bin

and I get the following warning (the bottom 3 lines)

Waiting for debugger to connect...
Program started.
2021-01-06 12:03:05.646:INFO::main: Logging initialized @1721ms to org.eclipse.jetty.util.log.StdErrLog
2021-01-06 12:03:06.053:INFO: oejs.Server:main: jetty-9.4.z-SNAPSHOT; built: 2018-05-03T15:56:21.710Z; git: daa59876e6f384329b122929e70a80934569428c; jvm 1.8.0_221-b11
2021-01-06 12:03:06.299:INFO: oejs.session:main: DefaultSessionIdManager workerName=node0
2021-01-06 12:03:06.299:INFO: oejs.session:main: No SessionScavenger set, using defaults
2021-01-06 12:03:06.301:INFO: oejs.session:main: node0 Scavenging every 660000ms
2021-01-06 12:03:06.302:INFO: oejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@8bd1b6a{/,file:///C:/Development/B4J/jAPI/Objects/www/,AVAILABLE}
2021-01-06 12:03:06.313:INFO: oejs.AbstractNCSARequestLog:main: Opened C:\Development\B4J\jAPI\Objects\logs\b4j-2021_01_06.request.log
2021-01-06 12:03:06.761:INFO: oejs.AbstractConnector:main: Started ServerConnector@1b52435f{HTTP/1.1,[http/1.1]}{0.0.0.0:17178}
2021-01-06 12:03:06.761:INFO: oejs.Server:main: Started @2841ms
Emulated network latency: 100ms
API server (version = 1.02) is running on port 17178
Open the following URL from your web browser

http://127.0.0.1:17178

Jan 06, 2021 12:03:19 PM com.mchange.v2.log.MLog
INFO: MLog clients using java 1.4+ standard logging.
Jan 06, 2021 12:03:20 PM com.mchange.v2.c3p0.C3P0Registry
INFO: Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -0800; debug? true; trace: 10]
Jan 06, 2021 12:03:20 PM com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource
INFO: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 20000, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, contextClassLoaderSource -> caller, dataSourceName -> 1bqub5uae1nc7yl91uutggk|3fd7a715, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> com.mysql.jdbc.Driver, extensions -> {}, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, forceSynchronousCheckins -> false, forceUseNamedDriverClass -> false, identityToken -> 1bqub5uae1nc7yl91uutggk|3fd7a715, idleConnectionTestPeriod -> 600, initialPoolSize -> 3, jdbcUrl -> jdbc:mysql://localhost/computer_api?characterEncoding=utf8, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 1800, ma...
Wed Jan 06 12:03:21 SGT 2021 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.
Wed Jan 06 12:03:21 SGT 2021 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.
Wed Jan 06 12:03:21 SGT 2021 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.

Using the following has no warning.

#AdditionalJar: mysql-connector-java-5.1.37-bin

How to prevent showing this warning?

 

[Erel]

I guess that you are not using SSL, right? Add useSSL=false to the JdbcURL. Or ignore this warning.

 

[aeric]

I guess that you are not using SSL, right? Add useSSL=false to the JdbcURL. Or ignore this warning.

Like this?

JdbcUrl=jdbc:mysql://localhost/computer_api?characterEncoding=utf8&useSSL=false

 

[Erel]

Yes.

 

[aeric]

Yes.

Thanks. Solved.