(SAVEOK_SAVE/to_star_rx) FATAL ERROR!

[Rentian Huang]

Greetings Cloverleafers!!!

V5.2 on AIX

Hope everyone have a great time in the Annual User Group 🙂

I am having a lot of this errors in my edb, where am I doing wrong???

---

prod_orders_results:/hci/quovadx/qdx5.2/integrator/prod_orders_results>hcidbdump -e -m 7591295 -c

                       C

                       l T

                       a y F

                       s p w

Created  Message Id     s e d Prio State Length Source          Dest

---

---

– – – —-

---

---

---

---

13:55:06  [0.0.7591295] P D N 5120   402    911 fr_psyche       to_star_rx

Tcl error:

       msgId   = message1

       proc    = ‘sendOK_save’

       args    = ”

       result  = ‘(SAVEOK_SAVE/to_star_rx) FATAL ERROR! Attempt to save over message ‘message0’ with message ‘message1”

       errorInfo: ‘

(SAVEOK_SAVE/to_star_rx) FATAL ERROR! Attempt to save over message ‘message0’ with message ‘message1’

   while executing

“error $errmsg”

   (“run” arm line 27)

   invoked from within

“switch -exact — $mode {

       start {

           # Initialize the ob_save global if needed

           if ![info exists ob_save

Done.

Topic

[Rentian Huang]

this is my sendOK_save.  

__________________________________________________________

proc sendOK_save { args } {

   keylget args MODE mode              ;# What mode are we in

   global ob_save ;# OB message saved here

   global HciConnName

   if ![info exists HciConnName] { set HciConnName UNKNOWN }

   set module “(SAVEOK_SAVE/$HciConnName)”

   keylget args ARGS uarg

   switch -exact — $mode {

       start {

   # Initialize the ob_save global if needed

   if ![info exists ob_save] {

set ob_save “”

   }

   return “”

}

       run {

   keylget args CONTEXT ctx

           keylget args MSGID mh

   if ![cequal $ctx send_data_ok] {

echo “$module Called with invalid context!”

echo “$module Should be SEND OK for OB DATA only.”

echo “$module Continuing msg.”

return “{CONTINUE $mh}”

   }

   if [cequal $ob_save “”] {

set ob_save $mh

# Do NOT return msg to the engine

return

   }

   # Something bad happened.  Proc that uses the saved msg

   # did not clean up after itself!

   set errmsg “$module FATAL ERROR! Attempt to save over

   message ‘$ob_save’ with message ‘$mh'”

   echo “$module $errmsg”

   echo “$module Existing msg:”

   msgdump $ob_save

   echo “$module New msg:”

   msgdump $mh

   error $errmsg; # Put msg in errdb

       }

       default {

   echo “Unknown mode in : ‘$mode'”

           return “”                   ;# Dont know what to do

       }

   }

}

[Anonymous]

This means that the ob_save global variable from a previous message isn’t being cleaned when the next message begins processing.  My first thought would be to look to see if I’m using the ‘kill_ob_save’ proc in the IB reply TPS.  If it’s there then is it in the right order with hcitpsmsgkill, it should be kill_ob_save first and then hcitpsmsgkill.

If all that is right then you’ll have to look at the content of the procedures becuase the clearing of the ob_save variable isn’t taking place.

[Rentian Huang]

Greg,

this happens together with my previous email on ERROR: Unsupported Trxid (101). These err msgs come in pairs, means that ERROR: Unsupported Trxid (101) triggers this error too.

Sam

[Author]

Replies