Panic indicates variant, could it be timestamp related?

[Jill Fredericks]

We have experienced two Panics this week. During the second, the logging was on and indicated a problem with the variant, but we could not reproduce. We did however notice two messages with the exact same date/timestamp (MSH-7) passing through the xlate, 20120322162149. When we try to SMAT the file for a time range that includes this time, we only get the first message and have to use other search criteria to bring in the second message.  Could this be an issue or should we continue to assume it has something to do with the variant? Cloverleaf Version 5.5PRev1 on AIX 5.3

[msg :RecD:DBUG/3:test_epic_orders_xlate:03/22/2012 16:21:50] HCIROOT= /qdx/qdx5.5/integrator, HCISITEDIR= /qdx/qdx5.5/integrator/prod_inpatient

[msg :RecD:DBUG/3:test_epic_orders_xlate:03/22/2012 16:21:50] opening variant non-batch (/qdx/qdx5.5/integrator/prod_inpatient/formats/hl7/2.3/310_epic_to_agfa_oru/messages/ORU)

[msg :RecD:INFO/1:test_epic_orders_xlate:03/22/2012 16:21:50] Unable to get HL7 segment information: Undefined field id ‘00755’ at line 1

[msg :RecD:INFO/1:test_epic_orders_xlate:03/22/2012 16:21:50] Unable to load segment definition ‘PD1’.

[msg :RecD:ERR /0:test_epic_orders_xlate:03/22/2012 16:21:50] Unable to load segment ‘PD1’

[msg :RecD:INFO/1:test_epic_orders_xlate:03/22/2012 16:21:50] Unable to find message definition ‘ORU’.

PANIC: “(hr)->hr_vmi != ((struct VvMsgInfo *) 0)”

PANIC: Calling “pti” for thread test_epic_orders_cmd

Topic

[Jim Lohe]

Jill Fredericks wrote:

We have experienced two Panics this week. During the second, the logging was on and indicated a problem with the variant, but we could not reproduce. We did however notice two messages with the exact same date/timestamp (MSH-7) passing through the xlate, 20120322162149. When we try to SMAT the file for a time range that includes this time, we only get the first message and have to use other search criteria to bring in the second message.

[Author]

Replies