I am using the Symmetric DS Version 3.5.11. Everything worked fine for Java 1.7.0_55. One month ago I replace my Java to 1.8.0_25. After Upgrading to Java 1.8, one of my table have SYNC problem with Server. Here is my Server and Client Info. Any Immediate help will be appreciated.
Server configuration:
Database: MS SQL Server 2012
Symmetric Version: 3.5.11
I think you'll need to provide a bit more information about what the actual "sync problem" is. I haven't heard reports of the Java version affecting synchronization, but it does it would be good to know about.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have several messages that affect the client database contents. Each message has a Symmetric transaction that captures all of the database table changes (in H2 database) and transfers to the server using pub/sub (using symmetric extension). The changes are then automatically entered into the server database (SQl Server). During recent testing only ONE message has a problem where the server database is not updated. Our troubleshooting has determined if we go back to Java 1.7.0_55 ALL messages synchronize properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am using the Symmetric DS Version 3.5.11. Everything worked fine for Java 1.7.0_55. One month ago I replace my Java to 1.8.0_25. After Upgrading to Java 1.8, one of my table have SYNC problem with Server. Here is my Server and Client Info. Any Immediate help will be appreciated.
Server configuration:
Database: MS SQL Server 2012
Symmetric Version: 3.5.11
Client Machine:
Database: H2 1.3.168
Symmetric Version: 3.5.11
Table in MS SQL 2012:
CREATE TABLE attachment(
ATTACHMENT_GUID uniqueidentifier NOT NULL,
lkp_storage_type_id int NULL,
embedded_data varbinary(max) NULL,
url varchar(255) NULL,
pickup_url varchar(255) NULL,
isbn varchar(255) NULL,
file_name varchar(255) NULL,
document_date datetime NULL,
description varchar(255) NULL,
lkp_file_content_type_id int NULL,
file_size int NULL,
title varchar(255) NULL,
master_routing_guid uniqueidentifier NULL,
create_by varchar(30) NULL,
create_date datetime NULL,
update_by varchar(30) NULL,
update_date datetime NULL,
hash varchar(100) NULL,
dist_stmt varchar(3) NULL,
custody varbinary(max) NULL,
CONSTRAINT pk_attachment PRIMARY KEY NONCLUSTERED (ATTACHMENT_GUID)
)
Here is the old help ticket for more info about our Symmetric Implementation.
https://sourceforge.net/p/symmetricds/discussion/739236/thread/6ac9363c/?limit=25&page=1#322c
I think you'll need to provide a bit more information about what the actual "sync problem" is. I haven't heard reports of the Java version affecting synchronization, but it does it would be good to know about.
We have several messages that affect the client database contents. Each message has a Symmetric transaction that captures all of the database table changes (in H2 database) and transfers to the server using pub/sub (using symmetric extension). The changes are then automatically entered into the server database (SQl Server). During recent testing only ONE message has a problem where the server database is not updated. Our troubleshooting has determined if we go back to Java 1.7.0_55 ALL messages synchronize properly.