IV33069: 'THE SERVICEREGISTRY APPLICATION SHOULD WAIT FOR THE SIB MESSAGINGENGINE TO BE STARTED BEFORE STARTING ITSELF.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Upon start up WSRR assumes that the ME in the bus is running
    and depends upon it. If the ME fails to start or takes a long
    time to start, then WSRR fails to start.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Service Registry and Repository V8.0.
    
    ****************************************************************
    PROBLEM SUMMARY:
    The ServiceRegistry application requires that the messaging
    engine for the ServiceRegistryBus is started both during
    application startup and while the application is running. In
    some situations the messaging engine may not have completed
    startup before the ServiceRegistry application begins its
    startup process. This causes the ServiceRegistry application
    to abort startup and it must then be started manually once the
    ServiceRegistryBus messaging engine has completed startup.
    

Problem conclusion

  • By default the ServiceRegistry application startup will pause
    and retry the connection to the messaging engine every 5 seconds
    up to a maximum of 2 minutes. If the messaging engine has not
    started after waiting 2 minutes the Service Registry application
    will not start.
    
    The retry interval and maximum retry time can be configured by
    adding 2 WebSphere variables:
    - WSRR_STARTUP_BUS_RETRY_INTERVAL
    - WSRR_STARTUP_BUS_RETRY_MAXIMUM
    
    Both these variables should have values specified in
    milliseconds and be greater than 1000 (1 second). To start the
    ServiceRegistry application even if it cannot connect to the
    messaging engine, set either one of these variables to -1.
    
    This fix is targeted at WSRR V8.0.0.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV33069

  • Reported component name

    SERVICE REGISTR

  • Reported component ID

    5724N7200

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-05

  • Closed date

    2013-04-15

  • Last modified date

    2013-04-15

  • 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

    SERVICE REGISTR

  • Fixed component ID

    5724N7200

Applicable component levels

  • R800 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Service Registry and Repository

Software version:

8.0

Reference #:

IV33069

Modified date:

2013-04-15

Translate my page

Machine Translation

Content navigation