Menu

The outgoing batch failed: Incorrect string value - Symmetricds

Help
2017-07-11
2018-10-29
  • Igor Lopes De Agostin

    Hello guys!

    I've updated my symmetricds.

    Old Version: 3.7.17
    New Version: 3.8.27

    It turns out that when you synchronize the client data with the server the following message is displayed in the client log:

    "2017-07-11 11:14:43,748 ERROR [escola] [AcknowledgeService] [escola-push-default-1] The outgoing batch server-129 failed: [HY000,1366] Incorrect string value: '\xEF\xBF\xBDO D...' for column 'cor' at row 1"

    When querying the server, it is noticed that words with accents or with special characters come from incorrect form.
    Wrong: "N�O DECLARADA"
    Right: "NÃO DECLARADA"

    My setenv file looks like this:

    dp0="`dirname "$0"`/.."
    SYM_HOME="`cd "$dp0" && pwd`"
    export SYM_HOME
    
    SYM_OPTIONS="-Dfile.encoding=windows-1252 \
    -Duser.language=en \
    -Djava.io.tmpdir=$SYM_HOME/tmp \
    -Dorg.eclipse.jetty.server.Request.maxFormContentSize=800000 \
    -Dorg.eclipse.jetty.server.Request.maxFormKeys=100000 \
    -Dsym.keystore.file=$SYM_HOME/security/keystore \
    -Djavax.net.ssl.trustStore=$SYM_HOME/security/cacerts \
    -Dlog4j.configuration=file:$SYM_HOME/conf/log4j.xml \
    -Dsun.net.client.defaultReadTimeout=1800000 \
    -Dsun.net.client.defaultConnectTimeout=1800000 \
    -Djava.net.preferIPv4Stack=true \
    -XX:+HeapDumpOnOutOfMemoryError \
    -XX:HeapDumpPath=$SYM_HOME/tmp"
    export SYM_OPTIONS
    
    SYM_JAVA=java
    if [ "$JAVA_HOME" != "" ]
    then
       SYM_JAVA="$JAVA_HOME/bin/java"
    fi
    export SYM_JAVA
    
    SEP=:
    if uname | grep -i cygwin > /dev/null
    then
       SEP=";"
    fi
    
    CLASSPATH="${SYM_HOME}/patches${SEP}${SYM_HOME}/patches/*${SEP}${SYM_HOME}/lib/*${SEP}${SYM_HOME}/web/WEB-INF/lib/*"
    export CLASSPATH
    

    Can someone help me?

     
  • Klementina Chirico

    Hi Igor,

    This looks like a character set conversion problem. We use utf8 for our internal conversions to handle most characters.

    Just to help us understand what is happening, could you answer these questions?
    1. What database are you running?
    2. Was this also a problem in 3.7.17 or is it something new that you are experiencing in 3.8.27?

    Thanks,
    Klementina

     
  • Mark Michalek

    Mark Michalek - 2018-10-29

    I would guess this is related to the older server having "-Dfile.encoding=windows-1252" and the newer server having "-Dfile.encoding=utf-8"

     

Log in to post a comment.