i have configured the symmetricDS server and clinet node and data transfer is replicating over http and after adding the ssl certificates and enabling the https in been getting the below error.
[store-001] - DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
at sun.security.ssl.SSLSocketInputRecord.handleUnknownRecord(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
at org.jumpmind.symmetric.transport.http.HttpConnection.getOutputStream(HttpConnection.java:69)
at org.jumpmind.symmetric.transport.http.HttpIncomingTransport.applyRequestProperties(HttpIncomingTransport.java:253)
at org.jumpmind.symmetric.transport.http.HttpIncomingTransport.openStream(HttpIncomingTransport.java:136)
at org.jumpmind.symmetric.transport.http.HttpIncomingTransport.openReader(HttpIncomingTransport.java:175)
at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromTransport(DataLoaderService.java:598)
at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:308)
at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:256)
at org.jumpmind.symmetric.service.impl.RegistrationService.attemptToRegisterWithServer(RegistrationService.java:501)
at org.jumpmind.symmetric.service.impl.RegistrationService.registerWithServer(RegistrationService.java:476)
at org.jumpmind.symmetric.service.impl.PullService.pullData(PullService.java:90)
at org.jumpmind.symmetric.job.PullJob.doJob(PullJob.java:48)
at org.jumpmind.symmetric.job.AbstractJob.invoke(AbstractJob.java:227)
at org.jumpmind.symmetric.job.AbstractJob.run(AbstractJob.java:298)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Last edit: Abhinay 2021-01-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is this a new configuration and first attempt to use HTTPS between
SymmetricDS instances? (guessing since your engine/node is
"store-001"). There are several points of failure that can occur when
trying to configure SymmetricDS to use HTTPS between nodes (or
Java-based software applications in general). The first thing I do is
set this JVM argument:
That would be in conf/sym_service.conf for SymmetricDS
This JVM argument will increase the logging verbosity of Java's
attempt to establish an encrypted connection. The logging output will
end up in the service wrapper's log file. I think by default in
SymmetricDS that is logs/wrapper.log (determined by what you configure
in sym_service.conf for the "wrapper.logfile" parameter.
Note: There is a lot of material to go through in the service wrapper
log but that is where you need to start.
I have not integrated the symmetricDS with any other java application.
In my scenario i want to replicate the data from server DB to client DB and i have configured Corp properties for the server DB and store properties for client DB, when i insert data (insert new records) into server DB data is replicating into client DB for the http setup for sync url in corp and registration url in store.
By referring the above document i have generated keys and update the my sync and registration url to https in the respective property files after generated keys it added the sym.cer file in the corp when i start the servers for corp and store i encountered the below error on starting my store DB. DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have not integrated the symmetricDS with any other java application.
In my scenario i want to replicate the data from server DB to client DB and i have configured Corp properties for the server DB and store properties for client DB, when i insert data (insert new records) into server DB data is replicating into client DB for the http setup for sync url in corp and registration url in store.
By referring the above document i have generated keys and update the my sync and registration url to https in the respective property files after generated keys it added the sym.cer file in the corp when i start the servers for corp and store i encountered the below error on starting my store DB. DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "unsupported or unrecognized SSL message" can happen if you specify a sync_url with a protocol of HTTPS but the port is for a HTTP server. Unless you changed port numbers, the default port of 31417 is for HTTPS.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it was working for the http setup and later when i have geneated the keys and enabled the https port i was getting the below error. DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Then, in the engine property file, you will need to make sure that the sync.url property is pointing to this port that is set up for HTTPS (make sure to change the string "someservername" to the actual host name):
And because the communication is not working at all, you will have to update the record in the client database by executing the following SQL statement at the client database (make sure to change the string "someservername" to the actual host name):
update sym_node set sync_url='https://someservername:31417/sync/corp-000' where node_id='000';
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i have configured the symmetricDS server and clinet node and data transfer is replicating over http and after adding the ssl certificates and enabling the https in been getting the below error.
[store-001] - DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
at sun.security.ssl.SSLSocketInputRecord.handleUnknownRecord(Unknown Source)
at sun.security.ssl.SSLSocketInputRecord.decode(Unknown Source)
at sun.security.ssl.SSLTransport.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
at org.jumpmind.symmetric.transport.http.HttpConnection.getOutputStream(HttpConnection.java:69)
at org.jumpmind.symmetric.transport.http.HttpIncomingTransport.applyRequestProperties(HttpIncomingTransport.java:253)
at org.jumpmind.symmetric.transport.http.HttpIncomingTransport.openStream(HttpIncomingTransport.java:136)
at org.jumpmind.symmetric.transport.http.HttpIncomingTransport.openReader(HttpIncomingTransport.java:175)
at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromTransport(DataLoaderService.java:598)
at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:308)
at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:256)
at org.jumpmind.symmetric.service.impl.RegistrationService.attemptToRegisterWithServer(RegistrationService.java:501)
at org.jumpmind.symmetric.service.impl.RegistrationService.registerWithServer(RegistrationService.java:476)
at org.jumpmind.symmetric.service.impl.PullService.pullData(PullService.java:90)
at org.jumpmind.symmetric.job.PullJob.doJob(PullJob.java:48)
at org.jumpmind.symmetric.job.AbstractJob.invoke(AbstractJob.java:227)
at org.jumpmind.symmetric.job.AbstractJob.run(AbstractJob.java:298)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Last edit: Abhinay 2021-01-13
Is this a new configuration and first attempt to use HTTPS between
SymmetricDS instances? (guessing since your engine/node is
"store-001"). There are several points of failure that can occur when
trying to configure SymmetricDS to use HTTPS between nodes (or
Java-based software applications in general). The first thing I do is
set this JVM argument:
wrapper.java.additional=-Djavax.net.debug=ssl,handshake
That would be in conf/sym_service.conf for SymmetricDS
This JVM argument will increase the logging verbosity of Java's
attempt to establish an encrypted connection. The logging output will
end up in the service wrapper's log file. I think by default in
SymmetricDS that is logs/wrapper.log (determined by what you configure
in sym_service.conf for the "wrapper.logfile" parameter.
Note: There is a lot of material to go through in the service wrapper
log but that is where you need to start.
On Wed, Jan 13, 2021 at 8:18 AM Abhinay abhinay@users.sourceforge.net wrote:
Thanks for your reply Bruce
I have not integrated the symmetricDS with any other java application.
In my scenario i want to replicate the data from server DB to client DB and i have configured Corp properties for the server DB and store properties for client DB, when i insert data (insert new records) into server DB data is replicating into client DB for the http setup for sync url in corp and registration url in store.
it has worked for me in the above scenario and i have referred the below document (section 5.8.4)
https://www.symmetricds.org/doc/3.4/html/advanced-topics.html#encrypted-passwords
By referring the above document i have generated keys and update the my sync and registration url to https in the respective property files after generated keys it added the sym.cer file in the corp when i start the servers for corp and store i encountered the below error on starting my store DB.
DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
Thanks for your reply Bruce
I have not integrated the symmetricDS with any other java application.
In my scenario i want to replicate the data from server DB to client DB and i have configured Corp properties for the server DB and store properties for client DB, when i insert data (insert new records) into server DB data is replicating into client DB for the http setup for sync url in corp and registration url in store.
it has worked for me in the above scenario and i have referred the below document (section 5.8.4)
https://www.symmetricds.org/doc/3.4/html/advanced-topics.html#encrypted-passwords
By referring the above document i have generated keys and update the my sync and registration url to https in the respective property files after generated keys it added the sym.cer file in the corp when i start the servers for corp and store i encountered the below error on starting my store DB.
DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
The "unsupported or unrecognized SSL message" can happen if you specify a sync_url with a protocol of HTTPS but the port is for a HTTP server. Unless you changed port numbers, the default port of 31417 is for HTTPS.
Thanks Eric for the reply
i have enabled the https port in respective crop and store nodes and i have generated the key by following the below document
https://www.symmetricds.org/doc/3.4/html/advanced-topics.html#encrypted-passwords
it was working for the http setup and later when i have geneated the keys and enabled the https port i was getting the below error.
DataLoaderService - Failed to process batch javax.net.ssl.SSLException: Unsupported or unrecognized SSL message
You will need to make sure that you have set up in your conf/symmetric-server.properties file the following properties:
https.enable=true
https.port=31417
https.allow.self.signed.certs=true
https.verified.server.names=all
Then, in the engine property file, you will need to make sure that the sync.url property is pointing to this port that is set up for HTTPS (make sure to change the string "someservername" to the actual host name):
sync.url=https://someservername:31417/sync/corp-000
And because the communication is not working at all, you will have to update the record in the client database by executing the following SQL statement at the client database (make sure to change the string "someservername" to the actual host name):
update sym_node set sync_url='https://someservername:31417/sync/corp-000' where node_id='000';