PK21377: JVM HUNG AT DNS LOOKUP -IY63631/IY74810 CAUSED THIS PROBLEM

APAR status
Closed as program error.

Error description
This problem happens after applying 
IY74810 .
Application hangs when 1.3.1 SR9 build is applied. The
hung threads seem to be having the following stack trace
at the time of the hang:
{libhpi.a}{sysRecv}
{libjvm.a}{JVM_Recv}
{libnet.a}{Java_java_net_SocketInputStream_socketRead}
{java/net/SocketInputStream}{socketRead}
{java/net/SocketInputStream}{read}
{java/net/SocketInputStream}{read}
{http/sublayer/WtransConnectHandler}{pumpSocketData}
{http/sublayer/WtransConnectHandler}{handle}
{http/sublayer/WtransMultiProtocolHandler}{handleConnect}
{http/sublayer/WtransHttpProtocolInterpreter}{tunneling}
{http/sublayer/HttpProtocolInterpreter}{readFromSource}
{http/sublayer/HttpProtocolInterpreter}{interpretProtocol}
{sublayer/pluggable/RequestSolicitor}{createSublayerRequest}
{pluggable/RequestSolicitor$PluggableSublayerRunnable}{run}
{com/ibm/wbi/pool/ThreadPool$PoolThread}{run}
MMI GLUE
{libjvm.a}{mmipExecuteJava}
{libjvm.a}{xeRunDynamicMethod}
{libjvm.a}{threadRT0}
{libjvm.a}{xmExecuteThread}
{libjvm.a}{threadStart}
{libhpi.a}{_start}
{libpthreads.a}{_pthread_body}
The other thread doing the close() will have the following
stack trace:
(ip)=D026FC5C  at  libc.a  .res_nclose + 0024
unwinding (old_sp=414FA854 old_ip=D026FC5C)
(ip)=D0270E2C  at  libc.a  .res_nsend + 1178
unwinding (old_sp=414FAB74 old_ip=D0270E2C)
(ip)=D02A5CE8  at  libc.a  .res_nquery + 0124
unwinding (old_sp=414FAFD4 old_ip=D02A5CE8)
(ip)=D02A5774  at  libc.a  .res_nquerydomain + 0160
unwinding (old_sp=414FB444 old_ip=D02A5774)
(ip)=D02A5A10  at  libc.a  .res_nsearch + 0244
unwinding (old_sp=414FB8C4 old_ip=D02A5A10)
(ip)=D027A878  at  libc.a  .res_search + 00A0
unwinding (old_sp=414FB924 old_ip=D027A878)
(ip)=D028BA04  at  libc.a  .ho_byname2 + 012C
unwinding (old_sp=414FBD84 old_ip=D028BA04)
(ip)=D02A3C38  at  libc.a  .ho_byname + 0290
unwinding (old_sp=414FBDE4 old_ip=D02A3C38)
(ip)=D026EDD4  at  libc.a  .gethostbyname + 01B0
unwinding (old_sp=414FBE34 old_ip=D026EDD4)
(ip)=D03284A8  at  libc.a  .gethostbyname_r + 007C
unwinding (old_sp=414FBE84 old_ip=D03284A8)
(ip)=D1F91AD4  at  libnet.a  \
.Java_java_net_InetAddressImpl_lookupAllHostAddr + 00D0
unwinding (old_sp=414FD204 old_ip=D1F91AD4)
(cc)=30FCDEE8  at  \
java/net/InetAddressImpl.lookupAllHostAddr  \
(Ljava/lang/String;){{B  native
This problem can happen after application of APARs

IY74810 or 
IY63631.
Defect number sov 100629 .
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server version 5.02    *
*                 users                                        *
****************************************************************
* PROBLEM DESCRIPTION: JVM hung at DNS lookup                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem happens due to a programming error existing
in the JVM which allows interruptible I/O like recv(),
read(), write() etc to be retried on a file descriptor
that has already been closed. This would essentially
result in an application hang or a bad file descriptor
error.
Problem conclusion
When a file descriptor is supposed to be close()d, the
thread executing close() will signal all the other threads
doing I/O on that file descriptor to terminate the I/O
operation. This signal would cause the threads doing I/O
to be interrupted. But, in some situations, due to a
programming error, the threads doing I/O could retry the
I/O on the closing file descriptor. This can result in
I/Os being performed on wrong file descriptors and
unpredictable results or a bad file descriptor error would
be returned by the JVM.
.
To obtain the fix:
Install build 20060310 or later
Temporary fix Comments
APAR information
APAR number PK21377
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2006-03-13
Closed date 2006-03-13
Last modified date 2006-03-13

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

APAR is sysrouted TO one or more of the following:

Modules/Macros
JDK          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R00A PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PK21377
IBM Group: Software Group
Modified date: Mar 13, 2006