IBM Support

PM76557: DEFER MESSAAGING ENGINE (ME) STARTUP UNTIL AFTER THE SERVER START UP MESSAGE IS ISSUED

Fixes are available

7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Messaging Engine should not start until after the 'Server Start
    Message' is issued.  Individual Servant Region Address Spaces
    can be started and available prior to the full server being
    initialized.  The start of the Messaging Engine prior to the
    Server being fully initialized can cause problems.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0, V8.0, and V8.5                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Messaging Engine should not start       *
    *                      until after the 'Server Start           *
    *                      Message' is issued.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Messaging Engine should not start until after the 'Server Start
    Message' is issued.  Individual Servant Region Address Spaces
    can be started and available prior to the full server being
    initialized.  The start of the Messaging Engine prior to the
    Server being fully initialized can cause problems.
    

Problem conclusion

  • To enable synchronous startup of critical Messaging Engines
    with the WebSphere Application Server for z/OS, two custom
    properties and three WebSphere variables were introduced
    with this APAR.
    
    1. sib.property.isMECritical is a messaging engine custom
    property, for which a value of true marks a Messaging Engine
    as critical.
    
    2. synchWithControlRegion is a Scheduler custom property.When
    its defined as true ,the Scheduler will not attempt to run any
    work until the WebSphere Application Server for z/OS server is
    open for e-business.
    
    3. adjunct_region_start_synchronized is a WebSphere
    Application Server for z/OS environment variable, which
    can be defined as 1 or 0. When this property is set to 1, the
    WebSphere Application Server for z/OS server will wait for all
    critical Messaging Engines to start before opening for
    e-busines.
    
    4. adjunct_region_start_sib_waittime is a WebSphere
    Application Server for z/OS environment variable which
    defines how many seconds a server start should wait for
    the Messaging Engine marked critical to become active.This
    variable only applies when adjunct_region_start_synchronized
    is set to 1.This property controls how long we wait for BOTH
    the Adjunct region to start AND the critical MEs to start.
    
    5. adjunct_region_start_sib_abend is a WebSphere Application
    Server for z/OS variable that defines what action should take
    place when a critical Messaging Engine takes too long to
    start. A value of 0 means no action and a value of 1 means that
    the entire application server will ABEND.  WLM will not
    restart anything because the entire server will be down
    
    If the adjunct_region_start_sib_waittime expires before the
    Adjunct and all critical MEs have started, then an action
    specified by adjunct_region_start_sib_abend will be taken.
    
    APAR PM76557 requires changes to documentation.
    
    NOTE: Periodically, we refresh the documentation on our Web
    site, so the changes might have been made before you read this
    text. To access the latest on-line documentation, go to the
    product library page at:
    http://www.ibm.com/software/webservers/appserv/library
    Changes to the WebSphere Application Server Version 7.0
    Information Center will be made available in January, 2014.
    
    The following paragraph will be added to step 4 of the topic
    "Configuring schedulers using the administrative console"
    
    If you do not want the scheduler to attempt to run any work
    until the WebSphere Application Server for z/OS server is open
    for e-business, navigate to Resources > Schedulers > (scheduler)
    > , click Custom Properties > New  to add the
    synchWithControlRegion custom property to the scheduler
    configuration settings, and set the property to true. When this
    property is set to true the Scheduler waits until WebSphere
    Application Server for z/OS server is open for e-business before
    attempting to run any work. The default value is false.
    
    The topic "Service integration custom properties" will be
    updated to include following description of the
    sib.property.isMECritical custom property:
    
    sib.property.isMECritical
    
    Use this property to mark a messaging engine as critical. This
    property is used in conjunction with the
    adjunct_region_start_sib_abend,
    adjunct_region_start_sib_waittime, and
    adjunct_region_start_sib_abend, environment variables. See the
    topic "Application
    server custom properties for z/OS" for a description of these
    environment variables.
    
    Data Type:   Boolean
    Default:        False
    
    The topic "Application server custom properties for z/OS" will
    be updated to include the following descriptions of the
    adjunct_region_start_sib_abend,
    adjunct_region_start_sib_waittime, and
    adjunct_region_start_sib_abend, environment variables:
    
    adjunct_region_start_sib_abend
    
    Specifies what action should take place when a critical
    messaging engine takes too long to start.
    
    If you specify a value of 0 for this property, warning message
    BBOO0418W is issued.
    
    If you specify a value of 1 for this property, the entire
    application server abnormally terminates
    Data Type
    Integer
    Valid Values
    1 or 0
    Default
    0
    Used by Daemon
    No
    
    
    adjunct_region_start_sib_waittime
    
    Specifies how many seconds the server start-up process should
    wait for a critical messaging engine to become active.
    
    This  variable only applies if the
    adjunct_region_start_synchronized environment variable is set to
    1. This property controls how long the startup process waits for
    both  the adjunct region and the critical messaging engine to
    start. A value of 0 disables the timeout, and the startup
    process waits indefinitely for the adjunct region and the
    critical messaging engine to start.
    Data Type
    Integer
    Default
    300
    Used by Daemon
    No
    
    
    adjunct_region_start_synchronized
    
    Specifies whether the startup process waits for all  critical
    messaging engines to start before starting to process e-business
    applications.
    
    If you set this property to 1, the startup process waits for all
    critical messaging engines to start before starting to process
    e-business applications.
    
    If you specify a value of 0 for this property, the startup
    process does not wait for the critical messaging engines to
    start.
    
    Data Type
    Integer
    Valid Values
    1 or 0
    Default
    0
    Used by Daemon
    No
    
    APAR PM76557 is currently targeted for inclusion in WebSphere
    Application Server Fix Packs 7.0.0.31, 8.0.0.9, and 8.5.5.2
    of WebSphere Application Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76557

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-06

  • Closed date

    2013-12-17

  • Last modified date

    2014-02-05

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI13725

       UP14/01/11 P F401

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM76557

Modified date: 05 February 2014