IZ67322: Socket bind/connect binds to incorrect local port on dual stack IPV4 AND IPV6 WINDOWS MACHINE AFTER APPLYING IZ54931 IN 5.0 SR10

APAR status

• Closed as program error.

Error description

• Error Message: It was observed that when bind/connect sequence
  call was made by giving the local port that has already been
  bound, the new socket is bound to an ephemeral port instead
  instead of a given one. There is no information that the
  socket is bound to different port and no exception is thrown.
  .
  Stack Trace: N/A
  .
  

Local fix

• Problem can be workaround by using only Ipv4 stack, i.e, by
  using either of -Djava.net.preferIPv4Stack=true or
  -Djava.net.preferIPv6Stack=false.
  

Problem summary

• The problem is caused as JVM makes two sockets on dual stack
  machine, one for Ipv4 and another for Ipv6. The problem is
  caused when Ipv4 socket bind fails but Ipv6 socket bind passes.
  

Problem conclusion

• This defect will be fixed in:
  5.0.0 SR12
  .
  The JVM has been updated to throw the required exception.
  .
  To obtain the fix:
  Install build 20100431 or later
  

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

  JAVA 5 CLASS LI

• Fixed component ID

  620500130

Applicable component levels

• R500 PSN

     UP