PH07466: CRASH IN ULB DISPATCHER AFTER UPDATE TO 8.5.5.14 ON ZLINUX

9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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

• After update Edge uLB from 8.5.5.11 customer reports that
  dispatched it not started and a crash occur, generating a
  core.
  
  
  dsserver.log shows
  
  java.lang.NullPointerException
  
   at
  com.ibm.internet.nd.common.CMN_IpAddr.getMAC(CMN_IpAddr.java:231
  )
  
   at
  com.ibm.internet.nd.server.SRV_ConfigServer.main(SRV_ConfigServe
  r.java:324)
  
   at
  com.ibm.internet.nd.server.SRV_KNDConfigServer.main(SRV_KNDConfi
  gServer.java:27)
  
  
  
  sever.log starts with :
  
  Jan14 18:28:57.873 CET SRV: Operating Architecture: s390x
  
  Jan14 18:28:57.874 CET SRV: Local Host: 127.0.0.2/lbprod2 MAC:
  null
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Load       *
  *                  Balancer for IPv4 and IPv6                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Crash occurs on backup load balancer    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Load Balancer for IPv4 and IPv6 can experience a crash on
  the backup LB if a port is defined for "conn+affin" or
  affinity forwarding and a stickytime is not defined.
  

Problem conclusion

• During garbage collection, the backup LB only clears
  connection information if the stickytime period has expired.
  If using the default stickytime on affinity based forwarding,
  a divide by 0 error can occur and cause a crash.
  
  A fix has been made to prevent the divide by zero and
  eliminate the crash.
  Fix provided in :
  8.5.5.16
  9.0.0.11
  

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 EDGE LB IPV4

• Fixed component ID

  5724H8812

Applicable component levels

• R850 PSY

     UP