IBM Support

Unknown status in the Administration Console caused by java.io.EOFException

Troubleshooting


Problem

All NodeAgents, Application Servers, and Enterprise Applications display in the Administration Console in "unknown" state even though they are all up and running.

Symptom

The following can be seen in a trace when "Admin=all" tracing is enabled on the Deployment Manager:


[5/21/07 11:03:40:699 CDT] 420f24d9 AdminServiceI > queryNames          
                                 WebSphere:type=DeploymentManager,*
...        

[5/21/07 11:03:40:744 CDT] 473ca4d9 AdminServiceS d serializer
org.apache.soap.encoding.soapenc.CollectionSerializer          
...

[5/21/07 11:03:40:762 CDT] 473ca4d9 SOAPConnector < invokeTemplate -    
failed                                                                  
                                 queryNames                              
[SOAPException: faultCode=SOAP-ENV:Client; msg=java.io.EOFException: null; targetException=java.lang.IllegalArgumentException: java.io.EOFException: null]
at org.apache.soap.rpc.Call.invoke(Unknown Source)                      
at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnector
Client.java:547)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java
:111)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAP
ConnectorClient.java:544)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.queryNames(SOAPConn
ectorClient.java:384)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnecto
rClient.java:324)
at $Proxy0.queryNames(Unknown Source)                                  
at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:87)
at com.ibm.ws.management.AdminServiceImpl.queryNames(AdminServiceImpl.java:279)
at com.ibm.ws.console.core.mbean.MBeanHelper.getMBean(MBeanHelper.java:64)
at com.ibm.ws.console.core.mbean.DistributedMBeanHelper.getDeploymentManagerMBe
an(DistributedMBeanHelper.java:210)
at com.ibm.ws.console.core.mbean.DistributedMBeanHelper.getDeploymentManagerNod
eName(DistributedMBeanHelper.java:140)
at com.ibm.ws.console.core.servlet.StatusServlet.getNodeStatus(StatusServlet.java:117)
at com.ibm.ws.console.core.servlet.StatusServlet.getStatus(StatusServlet.java:64)
at com.ibm.ws.console.core.servlet.StatusServlet.doGet(StatusServlet.java:31)
at ....


The problem is caused by another JAR in the classpath with Apache SOAP classes which are conflicting with the WebSphere Application Server SOAP implementation. The JAR is likely to have these classes which do not come with the SOAP package shipped with IBM® WebSphere® Application Server:

org.apache.soap.encoding.SOAPMappingRegistry
org.apache.soap.encoding.soapenc.CleanSerializer
org.apache.soap.encoding.soapenc.CollectionSerializer

Resolving The Problem

Find the .jar file with the conflicting classes and remove it from the WebSphere Application Server classpath.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"System Management\/Repository","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;7.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21271831