JR44584: OUT OF MEMORY OCCURS WHEN DEPLOYING A PROCESS VIA PROCESS CENTER WHICH CONTAIN A JDBC ADAPTER.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The customer receives an out of memory error on the deployment
    manager when deploying an application/process via the Process
    Center. It is related to the generation of the SCA databindings.
    In one case the customer had a JDBC binding with around 100
    operations defined.
    
    The issue occured during this deployment task:
    com.ibm.ws.sca.binding.j2c.deploy.J2CGenerateDataBindingTask
    
    The issue occured during this method
    [8/21/12 15:57:01:367 EDT] 00000172 J2CBinding    >
    com.ibm.ws.sca.binding.j2c.deploy.J2CGenerateDataBindingTask
    Enter
    findTypeInSchemaList Entry >>
    

Local fix

  • Use less operations per adapter binding
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Deploying applications on Process Center    *
    *                  with defined SCA databindings.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Slow deployment of application leads    *
    *                      eventually leads to                     *
    *                      OutOfMemoryException.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When deploying a process application with SCA databinding
    implementations, the deployment of this application may lead
    to an out of memory situation. The deployment of the
    application may take up to an hour depending on how many
    databindings are defined and eventually hit a out of memory
    error. In the trace it can be seen the deployment process may
    be hung at this package :
    com.ibm.ws.sca.binding.j2c.deploy.J2CGenerateDataBindingTask
    An example of the hung trace point may be:
    [8/21/12 15:57:01:367 EDT] 00000172 J2CBinding    >
    com.ibm.ws.sca.binding.j2c.deploy.J2CGenerateDataBindingTask
    Enter
    findTypeInSchemaList Entry >>
    

Problem conclusion

  • Code changes have been made to databinding generation code to
    efficiently generate all the databinding types during
    deployment.
    
    An interim fix for Business Process Manager Version 8.0.0.0 has
    been published to Fix Central.  Please refer to the separate
    file that is automatically downloaded with the interim fix
    for prerequisite information and installation/uninstallation
    instructions.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44584

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-30

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-29

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R800 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Business Process Manager Advanced

Software version:

8.0

Reference #:

JR44584

Modified date:

2013-01-29

Translate my page

Machine Translation

Content navigation