Troubleshooting
Problem
WebSphere Process Server v7 custom profiles created using the Profile Management Tool or the manageprofiles command do not include the IPC_CONNECTOR_ADDRESS endpoint definition in the serverindex.xml file. The same problem occurs with WebSphere Enterprise Service Bus custom profiles. Nodeagent and deployment manager definitions are not affected.
Symptom
Server startup error message in SystemOut.log:
JMXConnectors E ADMC0069E:
The endpoint definition is empty for the IPC connector; the IPC connector will not be available
Server shutdown error message in SystemOut.log:
IPCConnectorS E ADMC0073E:
Failed to stop channel chain IPCCInboundChain.Default_IPC_Connector_Name/LC_IPCCInboundChain.Default_IPC_Connector_Name due to exception java.lang.NullPointerException
Resolving The Problem
To solve the problem for existing profiles that generate these errors, add the interprocess communication (IPC) connector port definition. You can use a script to add the information, or you can use the administrative console.
To use the administrative console, perform the following steps:
- Navigate to Servers > Server types > WebSphere application servers > servername > Ports.
- Select New to add a port with a port number that is not in use in your environment.
- In the Port name - User-defined Port field, enter: IPC_CONNECTOR_ADDRESS
- In the Host field, enter: hostname/localhost
- In the Port field, enter a port number that is not in use.
See "Port number settings for WebSphere Application Server versions" for the default port numbers used. - Save your changes.
See "Configure port settings" for information on how to change or add port numbers through scripting.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21427959