IBM Support

PI82642: JOB LOG SECTIONS ON THE ENDPOINT TO FAIL ON WRITE WHEN FULL.

Fixes are available

9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Exception:com.ibm.ws.gridcontainer.exceptions.JobLogManagerExcep
    tion
    SourceId:com.ibm.ws.gridcontainer.services.impl.WASJobLogManager
    Impl.get
    JobLogPartList ProbeId:147
    com.ibm.ws.gridcontainer.exceptions.JobLogManagerException:
    Could not
    list Job sub dir /apps/JavaBatch/joblogs/AIMAPRT3_245719
        at
    com.ibm.ws.gridcontainer.services.impl.JobLogManagerImpl.getJobL
    ogPartLi
    st(JobLogManagerImpl.java:311)
        at
    com.ibm.ws.gridcontainer.services.impl.WASJobLogManagerImpl.getJ
    obLogPar
    tList(WASJobLogManagerImpl.java:144)
    .........
    .........
    Caused by: java.lang.Exception: Error.listing.job.dir.{0}
        at Caused by: java.lang.Exception:
    Error.listing.job.dir.Caused by:
    java.lang.Exception:
    Error.listing.job.dir.(JobLogManagerImpl.java:310)
        ... 26 more
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Job log write fails on the              *
    *                      endpoint when job sections are full     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Batch jog logs are written to a "section" directory on the
    file system.  These section directories are created as needed
    by the runtime, with names like: section1, section2 and so on.
    The batch job logs are then written to their own
    subdirectories under those section directories.  The runtime
    code keeps track of how many job log subdirectories exist
    within a section directory to determine whether it is full or
    not.
    On AIX, there is a maximum of 32767 subdirectories.  There are
    already two links within a directory (one to itself and one to
    the parent) that count towards this limit.
    The internal count kept by the runtime was previously not
    taking those into account properly, causing a failure to write
    the job log if this caused the hard limit to be reached on AIX.
    

Problem conclusion

  • A code update has been made to properly account for the two
    exsiting links within a directory, and to cap the number of
    job log subdirectories to 32765 within a section directory.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.0.0.6.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Use the Job Scheduler custom property: MaxJobLogSubdirectories
    
    This property can be set to an integer value greater than 0 to
    set the maximum number of job log subdirectories to use.
    

Comments

APAR Information

  • APAR number

    PI82642

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-06

  • Closed date

    2017-08-24

  • Last modified date

    2017-08-24

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022