PI38495: LOGS FULL OF XNMI0004E ERROR MESSAGES IN CELL WITH SOME NODES THAT DO NOT HAVE INTELLIGENT MANAGEMENT RUNNING

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• WAS logs are being filled by many errors like this:
  
  DefaultStatsC E   XNMI0004E: Bad
  response from remote agent: {Content-type=[unknown/unknown]}
  
  
  The issue is being caused by faulty logic in the
  DefaultStatsCollector plugin when handling nodes that do not
  have Intelligent Management (Virtual Enterprise) running on
  them. The issue can be surfaced by having either unmanaged node
  definitions or federated nodes configured that are not running
  Intelligent Management where the host definition on those nodes
  is reachable, port 9980 is listening on those hosts, and
  capable of responding to http/https request originating from
  the dmgr.
  

Local fix

• There are several workarounds. The issue will go away once the
  entire cell is upgraded to 8.5.x.x.
  
  Alternatively for each unmanagmed node and each federated node
  that is not running Intelligent Management a custom property
  named stats.collector.remote.agent.port can be created at the
  node level with an integer value representing a port number for
  which it is known that there is no listening endpoint on that
  host corresponding to the port number chosen.
  
  Lastly the ORB_LISTENER_ADDRESS for MANSettlementServer1 could
  be changed from 9980 to some other value so that the http/https
  requests being made won't reach a destination capable of
  responding.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Virtual              *
  *                  Enterprise component of IBM Websphere       *
  *                  Application Server Network Deployment       *
  *                  edition, version 8.5 to 8.5.5.5.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: System out logs of deployment manager   *
  *                      are filled with XNMI0004E: Bad          *
  *                      response from remote agent messages     *
  *                      repeatedly.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is caused due to repeated polling by
  DefaultStatsCollector plugin(Statistics collector) of an
  external remote agent which is not running. There was no way
  to disable the stats collector when not required.
  

Problem conclusion

• We have introduced an option to disable the stats collector
  when not required. This can be done by setting a cell level
  custom property - "external.node.stats.collector.disabled" -
  to true.
  
  When the remote agent is used, this fix requires the
  specification of remote agent port that is given by the custom
  property - "stats.collector.remote.agent.port" - for stats
  collection.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP