Forum Replies Created
-
AuthorReplies
-
Vince: Though my reply is late in coming, thanks for your reply on this and for the diagram you emailed! That gotta be it.. I’m creating a copy.. sending it over to the next thread, but the original stays. this is my tcl proc that moves the msg from thread 2 to thread 3… I’m thinking that this is what makes a copy of the msg and stores it in the recovery DB… You think that is my problem? Code:
######################################################################
# Name: tps_transfer_msg
# Purpose:
# UPoC type: tps
# Args: tps keyedlist containing the following keys:
# MODE run mode (”start”, “run” or “time”)
# MSGID message handle
# ARGS user-supplied arguments:
#
#
# Returns: tps disposition list:
#
#proc tps_transfer_msg { args } {
keylget args MODE mode ;# Fetch modeset dispList {} ;# Nothing to return
switch -exact — $mode {
start {
# Perform special init functions
# N.B.: there may or may not be a MSGID key in args
}run {
# ‘run’ mode always has a MSGID; fetch and process it
keylget args MSGID mh
set overmh [msgcreate -meta {USERECOVERDB true} [msgget $mh]]
lappend dispList “OVER $overmh”
}time {
# Timer-based processing
# N.B.: there may or may not be a MSGID key in args
}
shutdown {
# Doing some clean-up work
}
}return $dispList
}
Actually they are still there.. I changed my search options and all are there.. since Feb 19th! Now I have to figure out why they are staying there even though they successfully get through. Yeah that’s what I was thinking.. but both recovery and error DB are empty. !!! Thanks!!! it works! I think I’ve fixed this issue now with all your help. Thanks.. However I have another post. Yeah I just checked and they message is getting stuck in State 10. See msg below: msg: 0x0xb7c3d03c
msgType : DATA
msgClass : ENGINE
msgState : OB pre-SMS (10)
msgPriority : 5120
msgRecoveryDbState: 3
msgFlags : 0x8002
msgMid : [0.0.1484]
msgSrcMid : [0.0.1479]
msgSrcMidGroup : midNULL
msgOrigSrcThread : tcp_in
msgOrigDestThread : thread2
msgSrcThread : thread1
msgDestThread : thread2
msgXlateThread :
msgSkipXlate : 0
msgSepChars :
msgNumRetries : 0
msgGroupId : 0
msgDriverControl :
msgRecordFormat :
msgRoutes :
msgUserData :
msgStaticIsDirty : 0
msgVariableIsDirty: 0
msgTimeStartIb : 1202243362.448
msgTimeStartOb : 1202243362.594
msgTimeCurQueStart: 1202243362.595
msgTimeTotalQue : 0.002
msgTimeRecovery : 1202243362.595
msgEoConfig : 0x(nil)
msgData (BO) : 0x0xb7c3d120
message : ‘MSH|^
Yeah that error is when the external connection closes I think, which should be fine. However in the status it is showing it failed everytime a message goes to thread2 then the message gets stuck in the rdb. There are no other errors in the logs or output that I can see. Been pretty frustrating trying to figure this out since it works perfect in our dev environment. This is the error: [pdl :PDL :ERR /0: thread1:02/05/2008 15:07:43] read returned error 0 (Success)
[pdl :PDL :ERR /0: thread1:02/05/2008 15:07:43] PDL signaled exception: code 1, msg device error (remote side probably shut down)
Yes you were right, there were messages stuck. Now that goes to my main problem again I guess. Why would messages get stuck in the recovery DB? There could have been messages, but not sure. I did stop and restart the process. Yes I found it after.. Thanks.. but I posted the error in another post. Any idea on that? -
AuthorReplies