PQ56657: CU WANTS THE APPSERVER TO NOT COME UP IF IT CANNOT BIND TO PORT (ALREADY IN USE)


APAR

APAR status
Closed as Permanent restriction.

Error description
CU wants the appserver to not come up if it cannot bind to
the OSE port (already in use).  This behavior occurs in Webspher
e 3.5.  The problem was fixed in 4.0.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who       *
*                 start the AppServer as a non-root user.      *
****************************************************************
* PROBLEM DESCRIPTION: The AppServer is not able to be         *
*                      restarted if the tcpip socket has not   *
*                      finished when the adminserver tries to  *
*                      start the appserver.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the AppServer crashes and the adminserver tries to restart
the appserver, if for some reason the tcpip socket is not
finished, the appserver won't be able to come up if the
appserver is started as a non-root user.  If the appserver was
started with a non-root user, it will rebind to the ose port
again irrespective of any other process holding on to the
port stalling the other process until this process is killed or
exited.
Problem conclusion
Technically speaking for WAS 3.5 the server will always come up
and bind to the port irrespective of any other programs using
the port causing the other program to stall, this feature has
been introduced for the appserver to start easily without
problems after a crash or when the socket is not cleared up
due to some network problems.  The stack that is being seen
may not be due to port in use, it may be a different problem.
In WebSphere Application Server 4.0 this seems to work properly
as expected, because it uses java sockets underneath for the
transport rather than the native sockets from the OSE layer.
To sum up it's a limitation in 3.5 to figure out the ports in
use and the user has to take care of setting the ports unique
to each appserver and make sure it doesn't conflict externally.
Temporary fix
Comments
APAR information
APAR numberPQ56657
Reported component nameWAS STANDARD SU
Reported component ID5648C8302
Reported release350
StatusCLOSED PRS
PENoPE
HIPERNoHIPER
Submitted date2002-01-14
Closed date2002-03-07
Last modified date2002-03-07

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros

Fix information
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ56657
IBM Group: Software Group
Modified date: 2002-03-07