IBM Support

PM67579: UNNECESSARY FFDC GENERATED FOR SCA EJBS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • [4/18/12 17:24:30:937 PDT]     FFDC
    Exception:java.io.FileNotFoundException
    SourceId:com.ibm.ws.metadata.ejb.ByteCodeMetaData.scan
    ProbeId:155
    Reporter:com.ibm.ws.metadata.ejb.ByteCodeMetaData@89e0333c
    java.io.FileNotFoundException: com/ibm/example/Bean_12345.class
    at com.ibm.ws.metadata.ejb.ByteCodeMetaData.scan
    (ByteCodeMetaData.java:150)
    at com.ibm.ws.metadata.ejb.ByteCodeMetaData.
    getByteCodeMethodMetaData(ByteCodeMetaData.java:224)
    at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.
    processAutomaticLightweightTransaction
    (EJBMDOrchestrator.java:7556)
    at com.ibm.ws.metadata.ejb.EJBMDOrchestrator.
    finishBMDInitForReferenceContext(EJBMDOrchestrator.java:8964)
    at com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.
    finishBMDInitForReferenceContext(AbstractEJBRuntime.java:2609)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V8.5 users *
    *                  of Service Component Architecture (SCA)     *
    *                  components or services wired over EJB       *
    *                  bindings                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: An unwanted FFDC incident report is     *
    *                      produced when the EJB is started.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The EJB container attempts to scan class bytecodes for certain
    metadata.  SCA dynamically generates the bean class in memory,
    so the class bytes are not found, and the EJB container
    produces an FFDC incident report.
    

Problem conclusion

  • The FFDC incident report was removed, and an
    equivalent EJBContainer=all trace statement was added.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.0.1.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM67579

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-25

  • Closed date

    2012-07-09

  • Last modified date

    2012-07-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 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:
02 November 2021