Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
1.5.6
-
None
-
Google Cloud App Engine
Description
It appears that using the serverSslCert=-----BEGIN CERTIFICATE type of syntax (i.e. specifying it inline which we need to do) causes a write to the keyStore.
Google App Engine runs on a read-only file system, so no writes are allowed. I suspect this is why the connection fails. Is there some way to work around this? Possibly not write it to the trust store?
The exception backtrace looks like this:
 |
java.sql.SQLNonTransientConnectionException: Failed to store certificate from serverSslCert into a keyStore
|
at org.mariadb.jdbc.internal.util.ExceptionMapper.get(ExceptionMapper.java:132) |
at org.mariadb.jdbc.internal.util.ExceptionMapper.getException(ExceptionMapper.java:101) |
at org.mariadb.jdbc.internal.util.ExceptionMapper.throwException(ExceptionMapper.java:91) |
at org.mariadb.jdbc.Driver.connect(Driver.java:109) |
at java.sql.DriverManager.getConnection(DriverManager.java:571) |
at java.sql.DriverManager.getConnection(DriverManager.java:215) |
at com.parasql.schema.TransactionSet.openConnection(TransactionSet.java:272) |