PQ77226: DISCOVERY OF THE NODE AGENT AND DEPLOYMENT MANAGER FAILS IN MULTIHOME ENVIRONMENT | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When configuring Deployment Manager on the system with multiple TCP/IP stacks, discovery between the servers might fail. In this case, DMGR could not discover the Node Agent and vice versa. There were no failure messages without the trace, but the expected messages were not there: -In DMGR: ADMD0023I: Process discovered (name: I21A, type: NodeAgent, . -In Node Agent: ADMD0023I: Process discovered (name: dmgr, type: DeploymentManager . With com.ibm.ws.management.*=all=enabled, the following traces in the Node Agent can be found: Trace: 2003/08/05 13:12:11.888 01 t=9CBCF0 c=UNK key=P2 (13007002) FunctionName: com.ibm.ws.management.discovery.transport.TcpMessenger SourceId: com.ibm.ws.management.discovery.transport.TcpMessenger Category: DEBUG ExtendedMessage: InetAddress, port: ; ip.address.com/1.2.3.4, 9277 Trace: 2003/08/05 13:12:11.897 01 t=9CBCF0 c=UNK key=P2 (13007002) FunctionName: com.ibm.ws.management.discovery.transport.TcpMessenger SourceId: com.ibm.ws.management.discovery.transport.TcpMessenger Category: DEBUG ExtendedMessage: connection refused; java.net.ConnectException: EDC8128I Connection refused. (errno2=0x76630291) . On the DMGR side,the folowing traces: Trace: 2003/08/05 13:14:40.105 01 t=9F9060 c=UNK key=S2 (13007002) FunctionName: com.ibm.ws.management.discovery.EndpointAddress SourceId: com.ibm.ws.management.discovery.EndpointAddress Category: ENTRY ExtendedMessage: EndpointAddress; tcp://XYZ:9277 Note XYZ does not match ip.address.com - therefore Connectin Refuse message in Node Agent. . MD17635Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Support is needed which provides a way * * to disable the default multihome * * support for the discovery and SOAP * * transports on z/OS hosts. * **************************************************************** * RECOMMENDATION: * **************************************************************** The default behaviour of WebSphere on zOS is to support multihome hosts on the SOAP and discovery ports. Support is needed which provides a way to disable this support if WebSphere is to be restricted to listen on only a specific IP in a multihomed configuration.Problem conclusion Support has been provided such that the default multihome support can be disabled by setting the following java system property" "com.ibm.websphere.network.useMultiHome=false" for each server. (deployment manager, node agent, application servers). If this property is specified the SOAP and discovery ports will be bound to the configured host name and not all available IPs. The following WebSphere V5.0 for z/OS documentation change is required as a result of APAR PQ77226: A new article, titled "Example: Setting Custom JVM Properties" will be added to the z/OS view of the WebSphere Application Server Version 5 InfoCenter. This article will be available in the next refresh of the InfoCenter. The new article will consist of the following description of the com.ibm.websphere.network.useMultiHome property: com.ibm.websphere.network.useMultiHome Specifies whether or not multihome support is enabled for the SOAP and node/cell discovery ports. If the property is set to false, then WebSphere Application Server will only listen on the configured host name for discovery and SOAP messages. The default value is true. You can change the value through the administrative console. Modify the defaults by setting the value for the server, deploymentmanager, and node agent. In order for these changes to take place, you must restart the server. Steps for this task 1. To set this property, connect to the administrative console and navigate to the indicated page. Application Server > server1 > Process Definition > Control > Java Virtual Machine > Custom Properties Deployment manager System Administration > Deployment Manager > Process definition Control > Java Virtual Machine > Custom Properties Node agent System Administration > Node Agent > nodeagent > Process definition > Control > Java Virtual Machine > Custom Properties 2. If the com.ibm.websphere.network.useMultiHome property is not present in the list, create a new property name and indicate its value. 3. Restart the server. APAR PQ77226 is associated with SERVICE LEVEL W500104 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ77226.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ77226
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.