PI58430: AFTER MIGRATION THE NODEAGENT SERVER THROWS AN EXCEPTION BECAUSE IT IS MISSING THE XDAGENT_PORT ENDPOINT

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

• Customer is seeing the exception below during stopping the
  nodeagent after migration. This does not affect any
  functionality though.
  
  FFDC_1bc1326a_16.01.19_17.19.54_0.txt
  FFDC_31ff4769_16.01.19_17.15.48_0.txt
  FFDC_8b67a4a5_16.01.19_17.22.08_0.txt
  FFDC_92fd7556_16.01.19_11.20.02_0.txt
  
  ------Start of DE processing------ = [16.01.19 17:22:08:339
  GMT+08:00] ,
  key =
  com.ibm.wsspi.channel.framework.exception.InvalidChainNameExcept
  ion
  com.ibm.ws.channel.framework.impl.ChannelFrameworkImpl.stopChain
  2645
  Exception =
  com.ibm.wsspi.channel.framework.exception.InvalidChainNameExcept
  ion
  Source =
  com.ibm.ws.channel.framework.impl.ChannelFrameworkImpl.stopChain
  
  probeid = 2645
  Stack Dump =
  com.ibm.wsspi.channel.framework.exception.InvalidChainNameExcept
  ion:
  Unable to stop unknown chain, XDA_CHAIN
          at
  com.ibm.ws.channel.framework.impl.ChannelFrameworkImpl.stopChain
  (Channel
  FrameworkImpl.java:2975)
          at
  com.ibm.ws.xd.agent.httpservice.runtime.component.HttpInboundCom
  ponentIm
  pl.stopService(HttpInboundComponentImpl.java:125)
          at
  com.ibm.ws.xd.agent.runtime.services.config.RuntimeServiceConfig
  .stop(Ru
  ntimeServiceConfig.java:165)
          at
  com.ibm.ws.xd.agent.runtime.LifeCycleManager.stop(LifeCycleManag
  er.java:
  85)
          at
  com.ibm.ws.xd.agent.runtime.RuntimeManager.stopRuntimeManager(Ru
  ntimeMan
  ager.java:221)
          at
  com.ibm.ws.xd.agent.websphere.runtime.component.XDAComponentImpl
  .stop(XD
  AComponentImpl.java:259)
          at
  com.ibm.ws.runtime.component.ContainerHelper.stopComponent(Conta
  inerHelp
  er.java:477)
          at
  com.ibm.ws.runtime.component.ContainerHelper.stopComponents(Cont
  ainerHel
  per.java:461)
          at
  com.ibm.ws.runtime.component.ContainerImpl.stopComponents(Contai
  nerImpl.
  java:650)
          at
  com.ibm.ws.runtime.component.ContainerImpl.stop(ContainerImpl.ja
  va:638)
          at
  com.ibm.ws.runtime.component.ServerImpl.stop(ServerImpl.java:654
  )
          at
  com.ibm.ws.runtime.component.ServerCollaborator$ShutdownHook$1.r
  un(Serve
  rCollaborator.java:890)
          at
  com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager
  Impl.jav
  a:5477)
          at
  com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM
  anagerIm
  pl.java:5603)
          at
  com.ibm.ws.runtime.component.ServerCollaborator$ShutdownHook.run
  (ServerC
  ollaborator.java:880)
          at
  com.ibm.ws.runtime.component.ServerCollaborator$StopAction.alarm
  (ServerC
  ollaborator.java:832)
          at com.ibm.ejs.util.am._Alarm.runImpl(_Alarm.java:151)
          at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:136)
          at
  com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
  
  
  The error is about an unknown channel name XDA_CHAIN.
  
  When a node is created for a cell, a nodeagent server is added
  and the endpoints are added by code logic versus a template.
  
  Whenever a nodeagent server is migrated from a release prior to
  8.5.5, it will not have an XDAGENT_PORT.  In addition, since
  WebSphere does not provide a nodeagent template for the
  serverindex.xml file this endpoint is not automatically added.
  Usually this endpoint is added during an addNode by a jacl
  script.  Migration will need to also add this endpoint when
  migrating a profile to version 8.5.5.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using the Migration Tools to         *
  *                  migrate a Node to v8.5.5                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: After migration the NodeAgent server    *
  *                      throws an exception because it is       *
  *                      missing the XDAGENT_PORT endpoint.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In version 8.5.5, the WebSphere Virtual Enterprise was
  integrated into the main product, which required the
  XDAGENT_PORT endpoint to be configured as part of the
  nodeagent server.  Since releases prior to 8.5.5 did not have
  this endpoint and WebSphere does not provide a template with
  this in it, migration did not add it.
  

Problem conclusion

• Because of the conditions in the problem summary, the
  migration code will insert this endpoint into nodeagent
  servers.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.10.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• This endpoint can be defined manually after the migration of a
  node.
  

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