IBM Support

JR33268: CORE DUMP IS PRODUCED WHEN XML READER STAGE RETURNS A FILE NOT FOUND EXCEPTION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • osh core dumps with sigsegv when XALAN parse returns file not
    found exception.
    
    message in job log:
    
    Message:: read_XML_file,0: Fatal Error: Fatal: XML input
    document parsing failed. Reason: Xalan fatal error (publicId: ,
    systemId: , line: 0, column: 0): An exception occurred!
    Type:RuntimeException, Message:The primary document entity could
    not be opened. Id=/path/to/invalid/file.xml
    
    Xalan fatal error (publicId: , systemId: , line: 0, column: 0):
    An exception occurred! Type:RuntimeException, Message:The
    primary document entity could not be opened.
    Id=/path/to/invalid/file.xml
    [dscapiop.C:1900]
    
    ENVIRONMENT:
    ------------
    Found in the following version of the product:
    Information Server 8.0.1.1  for Linux 2.6.9-67.0.15.ELsmp x86_64
    
    REPRODUCIBLE:
    -------------
    Core dump occurs when using MPP environment.
    for example when APT_CONFIG_FILE is:
    
    {
    
        node "conductor"
        {
           fastname "serverA"
           pools ""
           resource disk "/path/to/Datasets"       {pools ""}
           resource scratchdisk "/path/to/Scratch" {pools ""}
        }
    
        node "computeNode1"
        {
           fastname "serverB"
           pools ""
           resource disk "/path/to/Datasets1"       {pools ""}
           resource scratchdisk "/path/to/Scratch1" {pools ""}
        }
    
        node "computeNode2"
        {
           fastname "serverC"
           pools ""
           resource disk "/path/to/Datasets2"       {pools ""}
           resource scratchdisk "/path/to/Scratch2" {pools ""}
    }
    
    
    Does NOT occur when using 1 physical server.
    for example when APT_CONFIG_FILE contains 1 physical
    server/fastname:
    
    {
    
        node "conductor"
        {
           fastname "serverA"
           pools ""
           resource disk "/path/to/Datasets"       {pools ""}
           resource scratchdisk "/path/to/Scratch" {pools ""}
        }
    
        node "computeNode1"
        {
           fastname "serverA"
           pools ""
           resource disk "/path/to/Datasets1"       {pools ""}
           resource scratchdisk "/path/to/Scratch1" {pools ""}
        }
    
        node "computeNode2"
        {
           fastname "serverA"
           pools ""
           resource disk "/path/to/Datasets2"       {pools ""}
           resource scratchdisk "/path/to/Scratch2" {pools ""}
    }
    
    
    CORE DUMP INFO:
    ---------------
    <signal>
    
    Core was generated by
    '/path/to/PXEngine/bin/osh -APT_PMsectionLeaderFlag serverA'.
    
    Program terminated with signal 11, Segmentation fault.
    
    </signal>
    
    <stack>
    (gdb)
    #0  0xf7b588a8 in APT_PMMessagePort::makeMessage () from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #1  0xf7b56932 in APT_PMMessagePort::dispatch ()    from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #2  0xf7b5800a in APT_PMMessagePort::poll ()        from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #3  0xf7b59f0e in APT_PMpoll ()                     from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #4  0xf7b4e330 in APT_PMdispatchLoop ()             from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #5  0xf7b859be in APT_PMsectionLeaderMain ()        from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #6  0xf7b7bfe0 in APT_SharedMain ()                 from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #7  0xf7b8eaff in main ()                           from
    /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so
    #8  0x00b3cde3 in __libc_start_main () from /lib/tls/libc.so.6
    #9  0x0804bced in ?? ()
    </stack>
    

Local fix

  • A core dump can be avoided by setting the following parameter at
    either the job or project level:
    
    $APT_DISABLE_COMBINATION=true
    
    The fix for APAR JR30587 also addresses the issue specified in
    this APAR.
    
    This fix is included in 8.0.1 fix pack 3
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    IS 801 Linux
    ****************************************************************
    PROBLEM DESCRIPTION:
    Core dump by xml stage
    ****************************************************************
    RECOMMENDATION:
    PXEngine issue.Apply the Patch
    ****************************************************************
    

Problem conclusion

  • PXEngine issue.
    

Temporary fix

  • Apply the Patch
    

Comments

APAR Information

  • APAR number

    JR33268

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-10

  • Closed date

    2009-08-18

  • Last modified date

    2010-12-09

  • 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

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R801 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
09 December 2010