Monitoring initialization could fail in some large deployment environments where WebSphere eXtreme Scale container and catalog servers are embedded in WebSphere Application Server
The message center notification support in the catalog and container servers may encounter an ORB connection time out (CORBA.NO_RESPONSE: Request XXX timed out) error for the initial attempt to register JMX notification broadcasters. This problem occurs when you have installed WebSphere eXtreme Scale with WebSphere Application Server Version 8.5, 8.0, or 7.0.
You will see message center notifications such as "ClientNotifForwarder NotifFetcher-run Failed to fetch notification, stopping thread. Error is: java.rmi.RemoteException: CORBA NO_RESPONSE", and the error logs will show the same error message, one for each catalog and container server configured in the grid.
Diagnosing the problem
Check the message center for the following notification: "ClientNotifForwarder NotifFetcher-run Failed to fetch notification, stopping thread. Error is: java.rmi.RemoteException: CORBA NO_RESPONSE".
Resolving the problem
You may be able to prevent this error by starting each catalog and container server one at a time (allowing each to start to completion).
More support for:
WebSphere eXtreme Scale
Software version: 8.6
Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS
Reference #: 1619132
Modified date: 04 December 2012