PI50985: Collective controller does not start

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

• user makes an upgrade to 8.5.5.7 and sees controller failure
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile Collectives          *
  ****************************************************************
  * PROBLEM DESCRIPTION: V8.5.5.7 collective controller does not *
  *                      start                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A user installs or upgrades a collective controller at level
  8.5.5.7.  The controller might start once but will not restart
  after that. The error seen in logs might be similar to this:
  
  Exception = java.io.StreamCorruptedException
  Source =
  com.ibm.ws.frappe.utils.paxos.persistent.impl.CollectionInFile.r
  eadInternal
  probeid = 2207
  Stack Dump = java.io.StreamCorruptedException: invalid stream
  header: 20010000
  at
  java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.jav
  a:886)
  at java.io.ObjectInputStream.<init>(ObjectInputStream.java:347)
  at
  com.ibm.ws.frappe.utils.paxos.utils.SimpleNodeId.readExternal(Si
  mpleNodeId.java:215)
  at
  com.ibm.ws.frappe.utils.dsf.util.Externalizer.readExternalNoReso
  lver(Externalizer.java:263)
  at
  com.ibm.ws.frappe.utils.paxos.BallotNumber.readExternalUnResolve
  d(BallotNumber.java:105)
  at
  com.ibm.ws.frappe.utils.paxos.ConfigId.readExternal(ConfigId.jav
  a:93)
  at
  com.ibm.ws.frappe.utils.paxos.Config.readExternal(Config.java:13
  1)....
  

Problem conclusion

• A problem is corrected where IPv6 addresses were being parsed
  incorrectly.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.8.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Start the JVM with a generic JVM argument to disable IPV6:  -
  Djava.net.preferIPv4Stack=true
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP