|
Problem(Abstract) |
Why do I receive a CHKW2516E: CELL_DISCOVERY_ADDRESS error
in the "WebSphere Configuration Problems" window? |
|
|
|
Cause |
Here is an example of the error you are seeing in the
"WebSphere Configuration Problems" window:
Scope: cells/<cell name>/nodes/<node
name>/serverindex.xml
If the "Scope" indicates that the Base install serverindex.xml
file does not have this parameter. What is happening is that the Network
Deployment administrative console checks all the serverindex.xml
files and does not care if this is, or is not, a Network Deployment
serverindex.xml file. It only checks that parameter for speed
purposes. Also, the error is an IBM WebSphere Application Server check
error meaning that something failed a check, similar to WebSphere
Application Server V4.0, and the duplicateKeyCheck errors occurs
when starting. |
|
|
Resolving the
problem |
The CELL_DISCOVERY_ADDRESS,
as defined by the WebSphere Application Server V5.1 Information Center, is
an attribute of the deploymentManager object that exists inside
the server. It is the port used to receive the incoming process discovery
messages inside a deployment manager process.
So only the Deployment Manager serverindex.xml file needs this
flag. What you need to look at is the "Scope" for this "Configuration
Problem". The <node name> will determine if the problem is
with the Network Deployment Manager or one of the Base install nodes.
If the "Scope" indicates problems with the Network Deployment Manager,
check the serverindex.xml file for the following lines:
<specialEndpoints
xmi:id="NamedEndPoint_1" endPointName="CELL_DISCOVERY_ADDRESS">
<endPoint xmi:id="EndPoint_1" host="Host name"
port="####"/>
</specialEndpoints> |
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|