PQ61923: OSELISTENER CODE DOES NOT PROPERLY HANDLE THE ERROR "SOCKET_BASED_SERVER_LOOP ACCEPT ERROR 4" PROPERLY AND SERVLET ENGINE HANGS

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
The OSEListener code within the servlet engine does not handle
the following error properly (found in the native.log.was-oop
log): "Error - Socket_based_server_loop accept error 4"
As a result, this error will be followed by the following
errors:
1. Error - Attempts to reopen the listen socket failed after 3
   tries. Server listen shutdown
2. Error - Getting new connection failed
Furthermore, in the stderr of the appserver you will find
the following errors:errors:1. Error - Attempts to reopen the listen socket failed after 3tries. Server listen shutdown2. Error - Getting new connection failedFurthermore, in the stderr of the appserver you will find
1.com.ibm.servlet.engine.oselistener.outofproc. ServerQueueException: Error nativeGetSeviceMessageId error response from server 1 2. java.lang.NullPointerException at com.ibm.servlet.engine.ServletEngine.shutdown The end result is an application server hang.
the following errors:1.com.ibm.servlet.engine.oselistener.outofproc.ServerQueueException: Error nativeGetSeviceMessageId errorresponse from server 12. java.lang.NullPointerExceptionat com.ibm.servlet.engine.ServletEngine.shutdownThe end result is an application server hang.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5.x users     *
*                 with the appserver on a unix system.         *
****************************************************************
* PROBLEM DESCRIPTION: Improper handling of system call error  *
*                      could cause appserver to stop           *
*                      handling requests                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
EINTR weren't being handled correctly in some parts of the
code that made system calls.  It's not a common problem
to run into.  The errors could potentially cause the
appserver to stop handling requests.
Problem conclusion
Fixed the error handling to act correctly on systems that
return EINTR.
Temporary fix
Comments
APAR information
APAR numberPQ61923
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-06-05
Closed date2002-08-02
Last modified date2002-08-02

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
PLUGIN
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ61923
IBM Group: Software Group
Modified date: 2002-08-02