PK40741: THE SERVER STARTUP MAY FAIL WITH ABEND DC3 RC 000C0008 DUE TO JAVA.NIO.CHANNELS.UNRESOLVEDADDRESSEXCEPTION IN THE CONTROLLER

 Fixes are available

6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for AIX platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for HP-UX platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for OS/400 platform
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Solaris
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Windows platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for AIX platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for HP-UX platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for HP-UX platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for AIX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for AIX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for HP-UX platforms
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Linux platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Solaris
6.0.2.29: WebSphere Application Server V6.0.2 Fix Pack 29 for Windows platforms
6.0.2.27: WebSphere Application Server V6.0.2 Fix Pack 27 for Linux platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Linux platforms
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Solaris
6.0.2.25: WebSphere Application Server V6.0.2 Fix Pack 25 for Windows platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for HP-UX platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for Linux platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for Windows platforms
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for Solaris
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for OS/400 platform
6.0.2.23: WebSphere Application Server V6.0.2 Fix Pack 23 for Linux platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for AIX platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for Windows platforms
6.0.2.21: WebSphere Application Server V6.0.2 Fix Pack 21 for Solaris platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for AIX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for HP-UX platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for OS/400 platform
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Linux platforms
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Solaris
6.0.2.31: WebSphere Application Server V6.0.2 Fix Pack 31 for Windows platforms
V6.0.2: Java SDK 1.4.2 SR11 Cumulative Fix for IBM WebSphere Application Server



APAR status
Closed as program error.

Error description
These condition have to be present for this problem to occur:
1) DCS_UNICAST_ADDRESS is set to '*' as oppose to specific ip
    address or name (see local fix description to find where
    this property is set).
 2) localhost is not defined on the system
 3) the server was started within a very short amount of time
    after it was brought down

The problem is that we are trying to start a connection for a
port that is still in use.  The error path leads down to use
localhost.  If this problem occurs, the controller will abend
with ABEND=SDC3 U0000 REASON=000C0008 AND the log will show the
following exceptions:

BBOO0220E: CHFW0029E: Error initializing chain DCS because of
exception
com.ibm.wsspi.channel.framework.exception
 .ChannelException: java.nio.channels.UnresolvedAddressException

BBOO0220E: CHFW0029E: Error initializing chain DCS-Secure
because of exception com.ibm.wsspi.channel.framework.exception.C
hannelException:
java.nio.channels.UnresolvedAddressException

BBOO0220E: WSVR0009E: Error occurred during startup
 com.ibm.ws.exception.RuntimeError:
com.ibm.ws.exception.RuntimeError:
Unable to start the CoordinatorComponentImpl
 at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServe
   rImpl.java:194)
....
 Caused by:
com.ibm.wsspi.channel.framework.exception.ChainGroupException:
+
 Error starting chain DCS in group DCSChannel,
exception=com.ibm.wsspi.channel.framework.exception.ChannelExcep
tion:
java.nio.channels.UnresolvedAddressException
+
 Error starting chain DCS-Secure in group DCSChannel,
exception=com.ibm.wsspi.channel.framework.exception.ChannelExcep
tion:
java.nio.channels.UnresolvedAddressException
  at com.ibm.ws.channel.framework.impl.ChannelFrameworkImpl.star
    tChainGoup(ChannelFrameworkImpl.java:3652)
Local fix
1) define localhost in /etc/hosts:
   localhost 127.0.0.1
   or
   localhost 1.2.3.4
     where 1.2.3.4 is the system ip address

OR
2) Change DCS_UNICAST_ADDRESS from '*' to specific ip address:
   For an application server, click Servers > Application
      Servers > 'server_name', and then, under Additional
      Properties, click > Ports > DCS_UNICAST_ADDRESS
   For a node agent, click System administration > Node agents >
      'node_name', and then, under Additional Properties, click
      > Ports > DCS_UNICAST_ADDRESS
   For a deployment agent, click System administration >
      Deployment manager, and then, under Additional Properties,
      click > Ports > DCS_UNICAST_ADDRESS

OR
3) Wait longer before you restart the server.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V6.0.1 for z/OS                              *
****************************************************************
* PROBLEM DESCRIPTION: Starting WAS may see it fail due to a   *
*                      java.nio.channels.UnresolvedAddress-    *
*                      Exception. This can happen if the name  *
*                      in the endpoint is unresolvable or if   *
*                      the name is *, then localhost is used.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When starting the listening chains, if there is an error during
the bind request additional checks are made. This includes
making an outbound request to the name and port defined in the
EndPoint for the TCP chain. If the name is *, then localhost is
used. This is where the unresolved address exception is seen.
Problem conclusion
Protective code was added to ensure that the test address is
resolvable before the outbound connect attempt. If it is not,
then the chain start attempts stops and tries again in a few
seconds.

APAR PK40741 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.21 of WebSphere Application Server V6.0.1
for z/OS.
Temporary fix Comments
APAR information
APAR number PK40741
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 601
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2007-03-07
Closed date 2007-07-03
Last modified date 2007-08-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PK40743

Modules/Macros

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSN    UP
R601 PSY UK27100    UP07/07/25 P F707
R610 PSN    UP

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK40741.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 601
Software edition:
Reference #: PK40741
IBM Group: Software Group
Modified date: Aug 3, 2007