It is not possible to log in to any of the Web GUI servers while the ObjectServer is running.
You cannot log in to any Web GUI servers while the ObjectServer is running. Restarting the ObjectServer does not solve the problem. Restarting both the ObjectServer and the Web GUI servers can resolve the problem, but the problem can reoccur.
The maximum number of connections to the ObjectServer has been reached. The maximum number of connections is configurable. After the maximum number of connections is reached, no new connections can be made.
It is not possible to connect to the ObjectServer if all the connections are used. This restriction also applies to super users, because at the time when the connection is initiated, the user type is not known.
This problem can occur in environments where many Web GUI servers connect to a single ObjectServer, especially if the ObjectServer is at V7.3.1 or earlier.
An example of these environment is a load balancing environment, in which a cluster of V7.3.1 Web GUI servers is configured to use a single ObjectServer.
Diagnosing the problem
Use a UNIX command, for example netstat, to check the number of connections that is used on the ObjectServer hosts.
The TIP_HOME_DIR/profiles/TIPProfiles/logs/ncw/ncw.0.logfile contains entries similar to the following sample:
[2013-04-05T20:06:52]:SEVERE:HEMDA0264E:[NCWBringUpWorker]: Unable to create a connection at <host>:<port>. The server may be down or the maximum number of connections supported by <host>:<port> may have been reached. There are currently <XXXI> connection(s) in the connection pool.
Resolving the problem
Change the size of the connection pool in the Web GUI, and, if applicable, change the number of number of connections that is permitted by the ObjectServer.
The default connection pool size for the Web GUI is a minimum of 5 and a maximum of 10. To change this value edit the WEBGUI_HOME/etc/datasources/ncwDataSourceDefinitions.xml file. For the minimum pool size, change the minPoolSize attribute. For the maximum pool size, change the maxPoolSize attribute. After you change these values, restart the server for the changes to take effect.
The default maximum number of connections in V7.3.1 ObjectServers is 30. The default maximum number of connections in V7.4 ObjectServers is 256. To change this number, change the value of the Connections property in the ObjectServer properties file. After you change this value, restart the ObjectServer for the change to take effect.
Example: For a load balancing environment that contains 5 nodes, the Web GUI connection pools needs 25 to 30 connections, and Tivoli Integrated Portal needs 5 to 10 connections for authentication (if ObjectServer authentication is used). Therefore a connection pool of between 30 and 60 connections is needed. Consequently, the maximum number of connections to the ObjectServer needs to be higher than 60. For Tivoli Netcool/OMNIbus V7.3.1, the default is insufficient and needs to be changed. For V7.4, the default is sufficient.