IBM Support

JR54100: IN PROCESS CENTER STATIC CODE OF COMMON JAVA ASSETS DOES NOT RUN FOR EACH SNAPSHOT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If managed assets are common between snapshots, the static code
    for Java assets runs only once in IBM Process Center. For
    example, if you run code in ProcessApp1 for snapshot 1.0, the
    static code block is loaded and used. If you then run code in
    ProcessApp1 for snapshot 1.1, the static code block loaded from
    snapshot 1.0 is used again.
    

Local fix

Problem summary

  • In Process Center, the same ManagedAssetClassLoader is used
    across multiple snapshots of a process application if the assets
    are common. This is unexpected behavior and not the same
    behavior as on IBM Process Server.
    

Problem conclusion

  • When this APAR is installed and the trace
    com.ibm.ws.classloader.*=all is set, information about the BPM
    Managed Asset Class loader is printed to the trace file. This
    can be used for diagnostic purposes.
    com.lombardisoftware.server.core.ManagedAssetClassLoader
    initial cache size={0}
    com.lombardisoftware.server.core.ManagedAssetClassLoader
    current classloaderMap size={1}
    com.lombardisoftware.server.core.ManagedAssetClassLoader
    initial resourceMapSize={2}
    com.lombardisoftware.server.core.ManagedAssetClassLoader
    current resourceMap.size()={3}
    com.lombardisoftware.server.core.ManagedAssetClassLoader
    current locationMap.size()={4}
    A fix will be available for IBM BPM V8.0.1.3 that creates a
    ManagedAssetClassLoader for each snapshot and tip of a process
    application. Therefore, the static code block (and static
    initialization code) of a managed Java class asset will run for
    every snapshot and tip.
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR54100:
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    2. Select APAR or SPR, enter JR54100, and click Continue.
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR54100

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-19

  • Closed date

    2015-10-20

  • Last modified date

    2016-03-10

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 March 2016