When the server status page is accessed, deployment
manager will communicate with all node agents to get the server status.
This could take long time. The status of the servers are not cached. So,
if there are lot of servers, you will notice significant amount of delay
in loading status of all servers.
If you take javacores, the stack for the thread will be similar to one
shown below:
at java.net.Inet4AddressImpl.getLocalHostName(Native Method)
at java.net.InetAddress.getLocalHost(InetAddress.java(Compiled Code))
at org.apache.soap.util.mime.MimeUtils.getUniqueValue(Unknown Source)
at org.apache.soap.rpc.SOAPContext.setRootPart(Unknown Source)
at org.apache.soap.rpc.SOAPContext.setRootPart(Unkkkkkknown Source)
at org.apache.soap.rpc.SOAPContext.setRootPart(Unknown Source)
at org.apache.soap.transport.TransportMessage.save(Unknown Source) at
com.ibm.ws.management.connector.soap.SOAPResponse.writeSOAPResponse(
SOAPResponse.java(Compiled Code))
at
com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java
Compiled Code))
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest
(SOAPConnection.java(Compiled CODE))
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled
Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled code)
........
|