If the Business Rules user interface EJB is installed in the clustered environment, WebSphere® Application
Server might not start all of the servers in the cluster due to the callback timeout. This behavior is
because the Business Rules user interface EJB creates the dynamic permissions for all the
Business Rules tables when the server starts.
Symptom:
For example, the following error might be logged in the WebSphere Application
Server log:
org.omg.CORBA.NO_IMPLEMENT: No Cluster Data Available vmcid: 0x49421000 minor code: 42 completed:
No
Solution:
To prevent such a scenario, add the optional parameter called
IBM_CLUSTER_CALLBACK_TIMEOUT=180000. This parameter bypasses any callback timeout situation
within the clustered servers. For more information about this WebSphere Application
Server cell custom property,
see the WebSphere Application
Server documentation.