Maxwell Pettit

Hello, It's tough to tell what the issue is here. Could you copy/paste the whole error stack trace so that we can have context as to when exactly this error occurs? One suggestion would be to try using the JTDS driver rather than the mssql driver, as that what we use by default for MS SQL Server. http://jtds.sourceforge.net/ Thanks, Max

We have some documentation for the rest api here: https://www.symmetricds.org/doc/3.5/javadoc/org/jumpmind/symmetric/web/rest/RestService.html You can query data from a node by using the getQueryNode function: https://www.symmetricds.org/doc/3.5/javadoc/org/jumpmind/symmetric/web/rest/RestService.html#getQueryNode(java.lang.String) Thanks, Max

Matthew, You are correct, these would go in sym_service.conf. These lines may look like: wrapper.java.additional.24=-Dhttp.proxyHost=mydomain.com wrapper.java.additional.25=-Dhttp.proxyPort=3125 wrapper.java.additional.26=-Dhttp.proxyUser=UserName wrapper.java.additional.27=-Dhttp.proxyPassword=Password Thanks, Max

Hello, This is a tricky problem because after you restore your database, you won't know what data has been sent and not been sent before the restore. For this reason, I would advise against deleting any potential outgoing data otherwise you may delete data that has not yet been sent. The server will ignore duplicate batch ids from the client database that is restored, so in that case you wouldn't be getting any duplicate data on the server. However this also presents an issue, since once you restore...

Hello, It sounds like the culprit for this behavior is the parameter: initial.load.defer.create.constraints I would set this parameter to false and try your load again. Thanks, Max

Hi Oded, I was actually not referring to registration redirect, instead I was suggesting using 2 registration servers. Registration redirect is used for a similar scenario, but not the exact scenario you have. In a typical setup, the "master" node is the only registration server. What I was suggesting to you is that you can treat your DB2 AND DB3 nodes as independent registration servers. So in this scenario, you would setup DB2 as a master node. Then, you could create a new node for DB3 that registers...

Hi Oded, You can actually register a node with another node that is not a master node. So for example, you could have DB2 as your only 'true' master node (i.e. not registered with any other node). Then you could register DB3 with DB2. Then you could still register DB4 with DB3, the only requirement is that the INITIAL_LOAD_TIME in SYM_NODE_SECURITY on DB3 must not be null. You can either initial load DB2 -> DB3 or just set the value in SYM_NODE_SECURITY to the current timestamp manually. Does this...

Hello again, Let us know if you have any more questions about our terminology. Perhaps we should consider adding a "Glossary" of terms to our documentation to help with this. As for you questions: 1.) This makes sense for this scenario to use DB2 and DB3 as the master nodes. These still be in different node groups, you'd just need to register DB1 and DB4 with the master node that it can communicate with. And you are correct, each node requires exactly 1 engine properties file regardless of whether...