SMAT does not Save Inbound – No errors or entries in DB

This topic has 4 replies, 2 voices, and was last updated 14 years, 7 months ago by Jim Kosloskey.

Creator

Topic
May 13, 2010 at 7:49 pm #51752
mark davis
Participant
This thread issue (his_order) is similar to the 2008 thread ‘Rev 2 mlp_tcp’ with a few important differences: 1) my issue is inbound, and 2) hcidbdump has NO entries. Sometimes hcidbinit is run (these tend to be new machines), so there are not many entries in the recovery and error databases, but usually there is at least one entry. The inability to see/capture new transactions inbound has been problematic. Any insight appreciated.

Equipment: Windows Server 2003 R2, SP2, QDX 5.3, client 5.3P_REV5

Procs on his_order (inbound thread): RawHL7Ack (IB)

Procs on gemsit_orders (outbound thread): validate_reply, kill_ob_save, hcitpsmsgkill (OB – OB Only checked on IB thread)

Inbound log attached with enable_all active.
Creator

Topic

Viewing 3 reply threads

Author

Replies
- May 14, 2010 at 1:09 pm #71597
  mark davis
  Participant
  ~~mark davis wrote:~~
  
  [prod:prod:INFO/0: STARTUP_TID] Copyright 1993-2007, Quovadx Inc.
  
  [prod:prod:INFO/0: STARTUP_TID] QDX(TM) Integration Services 5.3P Rev5
  
  [prod:prod:INFO/0: STARTUP_TID] Linked by Administrator on swatch at Mon Apr 23 15:34:29 2007 in C:/cloverrel/cloverleaf/engine/main (build 143)
  
  [prod:prod:INFO/0: STARTUP_TID] Started at Wed May 12 11:34:28 2010
  
  [prod:prod:INFO/0: STARTUP_TID] Engine process is 5080 on host MS720
  
  [prod:prod:INFO/1: inbound_cmd] Msg space limit is 100
  
  [prod:prod:INFO/0: inbound_cmd] DiskQue Minimum # of Messages/que: 50
  
  [prod:prod:INFO/0: inbound_cmd] DiskQue Virtual Memory percent:75.000000
  
  [prod:prod:INFO/0: inbound_cmd] Applying EO config: ”
  
  [prod:prod:INFO/0:inbound_xlate] Applying EO config: ”
  
  [prod:prod:INFO/0: his_order] Applying EO config: ‘enable_all’
  
  [msi :msi :INFO/1: his_order] Initializing statistics for: his_order
  
  [diag:leak:DBUG/0: his_order] diag mtd alloc 0x00AB9410
  
  [diag:leak:DBUG/0: his_order] diag mts alloc 0x00AB94B8
  
  [diag:leak:DBUG/0: his_order] diag mis alloc 0x00AB9588
  
  [diag:leak:DBUG/0: his_order] diag timeval alloc 0x00AB49F8
  
  [diag:leak:DBUG/0: his_order] diag timeval alloc 0x003E7C70
  
  [diag:leak:DBUG/0: his_order] diag ev alloc 0x00AB9438
  
  [diag:leak:DBUG/0: his_order] diag dqe alloc 0x00AB93B8
  
  [pti :even:DBUG/0: his_order] Registering ACTIVE_TIMER () event 0x00AB9438 for tid 2
  
  [diag:leak:DBUG/0: his_order] diag ele alloc 0x00AB93A0
  
  [pti :even:DBUG/0: his_order] Registering ACTIVE_TIMER event for tid 2
  
  [diag:leak:DBUG/0: his_order] diag timeval free 0x003E7C70
  
  [msi :msi :DBUG/1: his_order] msiSetExportTimer: 5 second timer event set
  
  [pd :thrd:INFO/0: his_order] Performing database recovery
  
  [dbi :log :INFO/1: his_order] Scanning Recovery DB for selected messages
  
  [dbi :log :INFO/1: his_order] Messages limited to those owned by:
  
  [dbi :log :INFO/1: his_order] his_order
  
  [pd :thrd:INFO/0: his_order] Database recovery complete
  
  [pd :pdtd:INFO/0: his_order] Initializing Protocol Driver
  
  [diag:leak:DBUG/0: his_order] diag pd alloc 0x00AB6840
  
  [pdl :init:INFO/1: his_order] Initializing
  
  [diag:leak:DBUG/0: his_order] diag pdl alloc 0x00AB9980
  
  [pdl :init:DBUG/0: his_order] PDL Name: ‘mlp_tcp.pdl’
  
  [pdl :open:DBUG/0: his_order] PDL Config: ‘{TYPE tcp-server} {PORT 4001} {NAME mlp_tcp.pdl} {MODE None} {IS_SSL 0} {CA_FILE {}} {CA_PATH {}} {CERT_FILE {}} {PRIVATE_KEY {}} {PASSWORD {}} {CERT_TYPE PEM} {KEY_TYPE PEM}’
  
  [diag:leak:DBUG/0: his_order] diag timeval alloc 0x00AB67F0
  
  [pd :pdtd:INFO/1: his_order] Set driver status to PD_STATUS_OPENING
  
  [pdl :open:INFO/0: his_order] Loading PDL driver ‘mlp_tcp.pdl’
  
  [pdl :PDL :DBUG/0: his_order] Loading driver: c:/gehc-it/ccg/quovadx/qdx5.3/integrator/pdls/mlp_tcp.pdo
  
  [msg :Mid :DBUG/3: his_order] Opening mid ctr file c:gehc-itccgquovadxqdx5.3integratorhis_prod/exec/mid
  
  [dbi :elog:DBUG/3: his_order] [0.0.61611] Looking for mid in error db
  
  [dbi :rlog:DBUG/3: his_order] [0.0.61611] Looking for mid in recovery db
  
  [msg :Mid :DBUG/3: his_order] Assigned mid [0.0.61611] to msg 003EB590
  
  [msg :Msg :DBUG/0: his_order] [0.0.61611] MSG alloc 0x003EB590
  
  [pdl :PDL :DBUG/0: his_order] Loaded: tcpip-mlp (version 2.0)
  
  [pdl :PDL :DBUG/0: his_order] Evaling:
  
  proc hci_pd.write { info } {
  
  global MsgId
  
  keylget info message MsgId
  
  keylset continuations ok write.done
  
  keylset continuations error write.error
  
  keylset continuations timeout
- May 14, 2010 at 2:19 pm #71598
  Jim Kosloskey
  Participant
  Mark,
  
  Maybe I am not reading this correctly but it does not look like a message ever arrived to that connection.
  
  No message – no SMAT and certainly no Recovery DB activity.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- May 14, 2010 at 6:59 pm #71599
  mark davis
  Participant
  Client was bypassing Cloverleaf and connecting directly to application parsing mechanism. Thanks Jim!
- May 14, 2010 at 7:50 pm #71600
  Jim Kosloskey
  Participant
  That’ll do it!!
  
  Every client/user thinks they know better.
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.