PM50450: SERVER HANG WITH WEB CONTAINER THREADS WAITING ON COM/IBM/WS/HTTP/HTTPTRANSPORT.REINITIALIZE

Fixes are available

APAR status

Closed as program error.

Error description

Server hang with javacores with webcontainer threads that are
waiting on the following:
"Non-deferrable Alarm : 3" J9VMThread:0x35202D00,
j9thread_t:0x351CA9DC
java/lang/Thread:0x915AC6D0, state:CW, prio=5
       (native thread ID:0x5C10039, native priority:0x5, native
policy:UNKNOWN)
      Java callstack:
          at java/lang/Thread.sleep(Native Method)
          at java/lang/Thread.sleep(Thread.java:851(Compiled
Code))
          at
com/ibm/ws/http/HttpTransport.reinitialize(HttpTransport.java:13
9)
          at
com/ibm/ws/management/connector/soap/SOAPServer.stateChanged(SOA
PServer.
java:82)
          at
com/ibm/ws/ssl/config/SSLConfigManager.notifySSLConfigChangeList
ener(SSL
ConfigManager.java:3125)
          at
com/ibm/ws/ssl/config/SSLConfigManager.initializeServerSSL(SSLCo
nfigMana
ger.java:278)
          at
com/ibm/ws/security/core/distSecurityComponentImpl.configChanged
(distSec
urityComponentImpl.java:1866)
          at
com/ibm/ws/management/component/ConfigChangeHandler$ConfigChange
EventDis
patcher.run(ConfigChangeHandler.java:344)
          at
com/ibm/ws/management/component/ConfigChangeHandler.alarm(Config
ChangeHa
ndler.java:158)
          at
com/ibm/ejs/util/am/_Alarm.run(_Alarm.java:127(Compiled
Code))
          at
com/ibm/ws/util/ThreadPool$Worker.run(ThreadPool.java:1550(Compi
led
Code))
.
There is a while-loop in HttpTransport that is prone to an
infinite loop if the server socket does not close cleanly when
the SOAP server is trying to reinitialize. The SSL change
triggers the SOAP server to reinitialize to pick up the
new SSL configuration. This infinite loop occurs if the server
socket does not close in 1.2 seconds. Each javacore was taken
about every 3 minutes and each shows the same thread blocking
the other threads, which confirms that the server socket failed
to close in less than 1.2 seconds and the infinite loop occurs.
.
Fix to eliminate the possibility that the code can go into an
infinite loop (loop caused by the server socket not closing
in the 1.2 seconds window).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 and V8.0                        *
****************************************************************
* PROBLEM DESCRIPTION: The logic to reinitialize a server      *
*                      socket could cause a hang in the        *
*                      WebSphere process if the socket is      *
*                      not closed quickly enough.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A hanging socket could cause the WebSphere process to hang.
Java callstack:
at java/lang/Thread.sleep(Native Method)
at java/lang/Thread.sleep(Thread.java:851(CompiledCode))
at
com/ibm/ws/http/HttpTransport.reinitialize(HttpTransport.java:13
9)
at
com/ibm/ws/management/connector/soap/SOAPServer.stateChanged(SOA
PServer.java:82)
at
com/ibm/ws/ssl/config/SSLConfigManager.notifySSLConfigChangeList
ener(SSLConfigManager.java:3125)
at
com/ibm/ws/ssl/config/SSLConfigManager.initializeServerSSL(SSLCo
nfigManager.java:278)
at
com/ibm/ws/security/core/distSecurityComponentImpl.configChanged
(distSecurityComponentImpl.java:1866)
at
com/ibm/ws/management/component/ConfigChangeHandler$ConfigChange
EventDispatcher.run(ConfigChangeHandler.java:344)
at
com/ibm/ws/management/component/ConfigChangeHandler.alarm(Config
ChangeHandler.java:158)
at
com/ibm/ejs/util/am/_Alarm.run(_Alarm.java:127(CompiledCode))
at
com/ibm/ws/util/ThreadPool$Worker.run(ThreadPool.java:1550(Compi
ledCode))

Problem conclusion

The code was updated to prevent a process hang in the event
that a server socket is slow to close.  If the socket does not
close in 1.2 seconds the operation will fail, and an FFDC
entry will be logged, rather than wait indefinitely.

Some operating systems might be slow to close sockets, in that
case the JVM property
com.ibm.ws.http.HttpTransport.reinitialize.waittime can be set
to the desired wait time in milliseconds.

For information on how to set a JVM property see:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
topic=/com.ibm.websphere.nd.doc/info/ae/ae/xrun_jvm.html


The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.23 and 8.0.0.3. Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM50450
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-10-19
Closed date
2012-01-05
Last modified date
2013-07-22

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM50450: SERVER HANG WITH WEB CONTAINER THREADS WAITING ON COM/IBM/WS/HTTP/HTTPTRANSPORT.REINITIALIZE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?