IC89497: ONMODE -X S (TO DUMP A STACK TRACE) CAN CRASH SERVER WHEN RUN AGAINST NAMED VP CLASS WHERE IDLE_THREAD IS RUNNING

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When you use onmode -X s to dump a stack from a vp, if the vp is
    a named vp class that has at 1 point run a sqlexec thread but
    currently has no running threads, it could crash the instance.
    
    It creates a recursive exception which brings the server down.
    
    The online log would look like this:
    
    13:22:59  stack trace for pid 12297 written to /dump/af.381a0
    13:22:59  stack trace for pid 12297 written to /dump/af.381a0
    13:22:59  Recursive Exception - Server exiting
    13:22:59  Recursive Exception - Server exiting
    13:22:59  Fatal error in ADM VP at mt.c:14033
    13:22:59  Unexpected virtual processor termination, pid = 12297,
    exit = 0x100
    
    13:23:00  PANIC: Attempting to bring system down
    
    The 1st stack trace message for the start of the onmode -X s
    command, then the 2nd for then the onmode command causes the
    signal, which tries to then dump the stack again, which then
    again causes another signal, so a recursive failure, and then
    the server bails.
    
    The af file would look something like this:
    
    13:22:59  Raw hex dump of stack located in /dump/af.381a0.rawstk
    13:22:59  Stack for thread: 0 idle
    13:22:59  Context ptr = 0x00000001015aa5f0
    13:22:59  Siginfo ptr = 0x00000001015aa8d0
    13:22:59  Reg 0      0x0000000000000000 Reg 1(PC)
    0x0000000100f960d4
    13:22:59  Reg 2(NPC) 0x0000000100f960d8 Reg 3
    0x0000000000000000
    13:22:59  Reg 4(g1)  0x0000000100e60650 Reg 5(g2)
    0x0000000101116000
    13:22:59  Reg 6(g3)  0x0000000000101000 Reg 7(g4)
    0x7fffffffffffffff
    13:22:59  Reg 8(g5)  0x0000000101570000 Reg 9(g6)
    0x0000000000000000
    13:22:59  Reg 10(g7) 0xffffffff7f300200 Reg 11(o0)
    0x0000000000000000
    13:22:59  Reg 12(o1) 0x0000000000000002 Reg 13(o2)
    0x00000000000000cb
    13:22:59  Reg 14(o3) 0x000000000010157c Reg 15(o4)
    0x0000000000101400
    13:22:59  Reg 16(o5) 0x0000000000000004 Reg 17(SP)
    0x00000001015aa1d1
    13:22:59  Reg 18(RA) 0x0000000100e61c9c
    13:22:59  Raw hex dump of stack located in /dump/af.381a0.rawstk
    13:22:59  Stack for thread: 0 idle
    
    Again the start of the stack dump up at the time, and it got to
    the point it printed out the thread name "0 idle" and then
    segv'd and started back into dumping out the stack again, and
    then crashes again.
    
    This PC is actually in the function search_evar where the crash
    is happening
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * tech support                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Update to IDS-11.70.xC8                                      *
    ****************************************************************
    

Problem conclusion

  • Problem Fixed In IDS-11.70.xC8
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC89497

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    B70

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-11

  • Closed date

    2014-02-26

  • Last modified date

    2014-02-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INFORMIX SERVER

  • Fixed component ID

    5725A3900

Applicable component levels

  • RB70 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Informix Servers

Software version:

B70

Reference #:

IC89497

Modified date:

2014-02-26

Translate my page

Machine Translation

Content navigation