PI42955: A NumberFormatException occurs during container reconnect or restart scenarios.

APAR status

• Closed as program error.

Error description

• When a container server goes through a reconnect or restart
  scenario to automatically reconnect to the catalog server, after
  failure event, a java.lang.NumberFormatException can occur in
  the FFDC logs.
  
  [6/2/15 5:39:24:762 MSK]     FFDC Exception:java.lang.NumberForm
  java.lang.NumberFormatException: null
  at java.lang.Integer.parseInt(Integer.java:465)
  at java.lang.Integer.parseInt(Integer.java:538)
  at com.ibm.ws.objectgrid.server.container.ServerAgent.createMemb
  at com.ibm.ws.objectgrid.server.container.ServerAgent.batchProce
  at com.ibm.ws.objectgrid.server.impl.ServerImpl.batchProcess(Ser
  at com.ibm.ws.objectgrid.server.xio.ServerActor.batchProcess(Ser
  at com.ibm.ws.objectgrid.server.xio.ServerActor.receive(ServerAc
  at com.ibm.ws.xs.xio.actor.impl.XIOReferableImpl.dispatch(XIORef
  at com.ibm.ws.xsspi.xio.actor.XIORegistry.sendToTarget(XIORegist
  at com.ibm.ws.xs.xio.transport.channel.XIORegistryRunnable.run(X
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolE
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
  at
  com.ibm.ws.objectgrid.thread.XSThreadPool$Worker.run(XSThread
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere eXtreme Scale users with the      *
  *                  container server reconnect option enabled.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: FFDC logs a                             *
  *                      java.lang.NumberFormatException after a *
  *                      container server reconnect event.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a container server goes through a reconnect or restart
  scenario to automatically reconnect to the catalog server,
  after
  a failure event, a java.lang.NumberFormatException can occur in
  the FFDC logs.
  [6/2/15 5:39:24:762 MSK]     FFDC
  Exception:java.lang.NumberFormatException
  SourceId:com.ibm.ws.objectgrid.server.xio.ServerActor.receive
  ProbeId:109
  Reporter:com.ibm.ws.objectgrid.server.xio.ServerActor@c78bd9a1
  java.lang.NumberFormatException: null
  at java.lang.Integer.parseInt(Integer.java:465)
  at java.lang.Integer.parseInt(Integer.java:538)
  at
  com.ibm.ws.objectgrid.server.container.ServerAgent.createMembers
  (ServerAgent.java:244)
  at
  com.ibm.ws.objectgrid.server.container.ServerAgent.batchProcess(
  ServerAgent.java:318)
  at
  com.ibm.ws.objectgrid.server.impl.ServerImpl.batchProcess(Server
  Impl.java:2964)
  at
  com.ibm.ws.objectgrid.server.xio.ServerActor.batchProcess(Server
  Actor.java:148)
  at
  com.ibm.ws.objectgrid.server.xio.ServerActor.receive(ServerActor
  .java:83)
  at
  com.ibm.ws.xs.xio.actor.impl.XIOReferableImpl.dispatch(XIORefera
  bleImpl.java:110)
  at
  com.ibm.ws.xsspi.xio.actor.XIORegistry.sendToTarget(XIORegistry.
  java:981)
  at
  com.ibm.ws.xs.xio.transport.channel.XIORegistryRunnable.run(XIOR
  egistryRunnable.java:88)
  at
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
  utor.java:1176)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
  cutor.java:641)
  at
  com.ibm.ws.objectgrid.thread.XSThreadPool$Worker.run(XSThreadPoo
  l.java:309)
  Paired with the FFDC, a CWOBJ1773I is logged that lists both
  host:port and server names. The server names cause the
  NumberFormationException.
  ServerImpl    I   CWOBJ1773I: This server received an updated
  high availability (HA) defined set from the catalog server,
  version 1 with the set now containing the servers:
  container1,hostname1:52615
  There is a timing window during the server reconnect where the
  sever name is used in the CWOBJ1773I message. The situation
  self corrects and uses the host:port in later logging of the
  message.
  

Problem conclusion

• The processing of the data listed in the CWOBJ1773I message was
  fixed.
  

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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP