Announcement

Collapse
No announcement yet.

Database related errors in OX logs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Database related errors in OX logs

    I am seeing errors like these every now and then:

    Code:
    The last packet successfully received from the server was 56,953 milliseconds ago.  The last packet sent successfully to the server was 0 milliseconds ago.
    The last packet successfully received from the server was 56,953 milliseconds ago.  The last packet sent successfully to the server was 0 milliseconds ago..' exceptionID=479486133-462
     The last packet successfully received from the server was 56,953 milliseconds ago.  The last packet sent successfully to the server was 0 milliseconds ago..' exceptionID=479486133-462
    The last packet successfully received from the server was 56,309 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.
    The last packet successfully received from the server was 56,309 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.' exceptionID=479486133-40
    The last packet successfully received from the server was 56,309 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.' exceptionID=479486133-40
     The last packet successfully received from the server was 56,309 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.' exceptionID=479486133-40
    What's interesting is the numeric value is sometimes same.

    configdb.properties looks like this:

    Code:
    useSeparateWrite=true
    readDriverClass=com.mysql.jdbc.Driver
    readUrl=jdbc:mysql://127.0.0.1:13306/configdb
    readProperty.1=user=ox
    readProperty.2=password=pass
    readProperty.3=useUnicode=true
    readProperty.4=characterEncoding=UTF-8
    readProperty.5=autoReconnect=true
    readProperty.6=useServerPrepStmts=false
    readProperty.7=useTimezone=true
    readProperty.8=serverTimezone=UTC
    readProperty.9=connectTimeout=15000
    readProperty.10=socketTimeout=15000
    writeDriverClass=com.mysql.jdbc.Driver
    writeUrl=jdbc:mysql://1.2.3.4/configdb
    writeProperty.1=user=ox
    writeProperty.2=password=passwd
    writeProperty.3=useUnicode=true
    writeProperty.4=characterEncoding=UTF-8
    writeProperty.5=autoReconnect=true
    writeProperty.6=useServerPrepStmts=false
    writeProperty.7=useTimezone=true
    writeProperty.8=serverTimezone=UTC
    writeProperty.9=connectTimeout=15000
    writeProperty.10=socketTimeout=15000
    cleanerInterval=10000
    minIdle=0
    maxIdle=-1
    maxIdleTime=60000
    maxActive=200
    maxWait=10000
    maxLifeTime=600000
    exhaustedAction=BLOCK
    testOnActivate=false
    testOnDeactivate=true
    testOnIdle=false
    testThreads=false
    writeOnly=false
    I would be glad if someone can guess the issue. Thanks

  • #2
    Hi,

    do you have some kind of MySQL monitoring in place? Looks like you're dealing with load peaks/timeouts or temporary unavailability of the database backed.

    Greetings
    Martin
    Last edited by Martin Heiland; 01-24-2013, 04:18 PM.

    Comment


    • #3
      It's an almost idle server so it's not definitely load/temp unavailability.. It could be related to timeout. Can you help as to how can I solve this?

      Comment


      • #4
        Well, timeouts may happen by hickups at your network infrastructure or other unplanned stuff. Not much i can do from remote. You may check the MySQL/System logs for the corresponding timeframe to debug more. Also, MySQL monitoring comes very handy sometimes

        Comment

        Working...
        X