LAWRENCE

Forum Replies Created

Viewing 1 replies (of 1 total)
  • Author
    Replies
  • in reply to: error TCP_SUB_WRITING #120943
    LAWRENCE
    Participant

      We have our networking team, along with Onbase and Epic Interconnect reps, engaged with the troubleshooting.  I will ask our networking team to take another look at the firewall settings (they said they reviewed it, but I’ll pester them a little;)

       

      Here is what is in the process log immediately after the message that fails:

      [msg :Msg :INFO/0:to_t_conv_shp105:10/24/2023 08:42:57] [0.0.147050] Updating the recovery database
      [dbi :rlog:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] [0.0.147050] Update msg in recovery db to state OB post-SMS
      [dbi :log :DBUG/2:to_t_conv_shp105:10/24/2023 08:42:57] log context: type 1, dbn 1, msgRec 10001, mdRec 10002, bodyRec 10003
      [dbi :log :DBUG/2:to_t_conv_shp105:10/24/2023 08:42:57] state 11, mode 1
      [dbi :dbi :DBUG/1:to_t_conv_shp105:10/24/2023 08:42:57] (0) ‘cl_lock: Trying to lock database ‘
      [dbi :dbi :DBUG/1:to_t_conv_shp105:10/24/2023 08:42:57] (0) ‘type=w, rec=10001
      [dbi :dbi :DBUG/1:to_t_conv_shp105:–/–/—- –:–:–] ‘
      [dbi :dbi :DBUG/1:to_t_conv_shp105:10/24/2023 08:42:57] (1) ‘type=w, rec=10002
      [dbi :dbi :DBUG/1:to_t_conv_shp105:–/–/—- –:–:–] ‘
      [dbi :dbi :DBUG/1:to_t_conv_shp105:10/24/2023 08:42:57] (2) ‘type=w, rec=10003
      [dbi :dbi :DBUG/1:to_t_conv_shp105:–/–/—- –:–:–] ‘
      [dbi :dbi :DBUG/1:to_t_conv_shp105:10/24/2023 08:42:57] (0) ‘cl_lock: Succeeded in locking database ‘
      [dbi :log :DBUG/2:to_t_conv_shp105:10/24/2023 08:42:57] update var MD, upd 1, dirty 0
      [diag:leak:DBUG/0:to_t_conv_shp105:10/24/2023 08:42:57] diag imh free 0x0x7fdfb480f390
      [diag:leak:DBUG/0:to_t_conv_shp105:10/24/2023 08:42:57] diag ptm free 0x0x7fdfb47f5c50
      [pti :sche:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] Thread has 1 ready events left.
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has 7 msgs
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has NO work
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has 7 msgs
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has NO work
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has 7 msgs
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has NO work
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has 7 msgs
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has NO work
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has 7 msgs
      [pd :thrd:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] OB-Data queue has NO work
      [pti :sche:DBUG/2:to_t_conv_shp105:10/24/2023 08:42:57] Thread 2 has been enabled
      [pti :sche:INFO/1:to_t_conv_shp105:10/24/2023 08:42:57] Thread has 1 ready events.
      [pti :even:DBUG/0:to_t_conv_shp105:10/24/2023 08:42:57] Processing SOCKET (TCP Client Read) event 0x0x7fdfac3e4490
      [pti :even:DBUG/1:to_t_conv_shp105:10/24/2023 08:42:57] Calling cb 0x501c77
      [tcp :wrte:WARN/0:to_t_conv_shp105:10/24/2023 08:43:12] Write sub thread hung with status “TCP_SUB_WRITING” after 15 seconds.
      [tcp :wrte:WARN/0:to_t_conv_shp105:10/24/2023 08:43:27] Write sub thread hung with status “TCP_SUB_WRITING” after 15 seconds.
      [tcp :wrte:WARN/0:to_t_conv_shp105:10/24/2023 08:43:42] Write sub thread hung with status “TCP_SUB_WRITING” after 15 seconds.
      [tcp :wrte:WARN/0:to_t_conv_shp105:10/24/2023 08:43:57] Write sub thread hung with status “TCP_SUB_WRITING” after 15 seconds.
      [pd :pdtd:INFO/1:to_t_conv_shp105:10/24/2023 08:43:57] Set driver status to PD_STATUS_ERROR
      [tcp :wrte:ERR /0:to_t_conv_shp105:10/24/2023 08:43:57] Write sub thread hung with status “TCP_SUB_WRITING” after a minute.

    Viewing 1 replies (of 1 total)