IBM Support

JR52824: STOPPING PROCESS FEDERATION SERVER TAKES 5 MINUTES, ELASTICSEARCH SERVICE STARTS TO SHUT DOWN, BECOMES UNRESPONSIVE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Requests to stop the Process Federation Server are not processed
    immediately. After 5 minutes, you see the following error
    messages in the messages.log file:
    
    [3/3/15 14:27:27:388 CST] 00000098
    org.apache.aries.blueprint.container.BlueprintExtender       I
    Destroying BlueprintContainer for bundle
    com.ibm.bpm.federated.query.rest.impl
    [3/3/15 14:32:27:392 CST] 00000098
    org.apache.aries.blueprint.container.ReferenceRecipe         I
    Timeout expired when waiting for mandatory OSGi service
    reference (objectClass=javax.transaction.TransactionManager)
    [3/3/15 14:32:27:394 CST] 00000098
    .blueprint.container.AbstractServiceReferenceRecipe$Listener E
    Error calling listener method public void
    com.ibm.bpm.federated.query.rest.blueprint.$Elasti
    
    Then the server finally stops.
    
    Also, when you update the elasticSearch configuration property
    in the server.xml file, the elasticSearch service starts to shut
    down and becomes unresponsive to subsequent queries.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    

Local fix

Problem summary

  • Stopping the Process Federation Server takes so long because the
     Process Federation Server waits for another component to shut
    down, ultimately timing out after 5 minutes of waiting, and then
     shutting down.
    
    The elasticSearch service starts to shut down because the
    configuration was updated. It restarts with outdated component
    references.
    

Problem conclusion

  • A fix for IBM BPM V8.5.6.0 is available that fixes the component
     shutdown and restart logic. This fix is superseded by JR52828.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52828:
    
     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 JR52828, 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

Comments

APAR Information

  • APAR number

    JR52824

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-16

  • Closed date

    2015-03-23

  • Last modified date

    2015-03-23

  • 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

  • R856 PSY

       UP

  • R855 PSN

       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":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 March 2015