PK71789: INTERMITTENT NULLPOINTEREXCEPTION IN FINISHRESPONSEMESSAGE

Fixes are available

APAR status

Closed as program error.

Error description

When multiple Asynchronous Request Dispatcher (ARD) clients
are used to stress the server, some intermittent
NullPointerExceptions occur.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server       *
*                  Version 7.0.0.0                             *
****************************************************************
* PROBLEM DESCRIPTION: This APAR covers several related        *
*                      webcontainer problems as described      *
*                      below.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1.     When multiple Asynchronous Request Dispatcher (ARD)
clients are used to stress the server, some intermittent
NullPointerExceptions occur.
    The partial stack is shown here.
[8/19/08 14:11:00:585 CDT] 0000004b channel    E
com.ibm.ws.webcontainer.channel.WCChannelLink fini
shBufferAsynch Exception in finishBufferAsynch:
            java.lang.NullPointerException
        at
com.ibm.ws.ard.channel.ARDHttpServiceContext.finishResponseMessa
ge(ARDHttp
ServiceContext.ja
va:136)
        at
com.ibm.ws.webcontainer.channel.WCChannelLink.finishBufferAsynch
(WCChannel
Link.java:483)
        at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin
k.java:198
)
        at
com.ibm.ws.ard.channel.ARDChannelConnLink.handleDiscrimination(A
RDChannelC
onnLink.java:183a
t
com.ibm.ws.ard.channel.ARDChannelConnLink.ready(ARDChannelConnLi
nk.java:90)

2.  The client side aggregation feature of ARD fails when
running through the WebSphere proxy. No output is shown.

3.  ARD with Dynamic Caching enabled fails sometimes with a
NullPointerException like the following:

[9/10/08 10:53:33:376 CDT] 00000037 servlet       E
com.ibm.ws.webcontainer.servlet.ServletWrapper s
ervice SRVE0068E: Uncaught exception created in one of the
service methods of the servlet /ARDPriceQ
uoteJSPAutoGen.jsp in application ERWW_Pyxis_08_16_2008e.
Exception created : java.lang.NullPointerE
xception
        at
java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.jav
a:779)
        at
com.ibm.ws.cache.servlet.FragmentComposer.getARDChildFragmentCom
poser(FragmentComposer.ja
va:1915)
        at
com.ibm.ws.cache.servlet.CacheARDHook.returnARDChild(CacheARDHoo
k.java:171)
        at
com.ibm.ws.cache.servlet.CacheHook.cleanup(CacheHook.java:304)
        at
com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:
259)
        at
com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.j
ava:259)
        at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1443)
        at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1384)
        at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
FilterChain.java:131)
        at
pricequote.ARDThreadIdFilter.doFilter(ARDThreadIdFilter.java:40)
        at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi
lterInstanceWrapper.java:
184)

4. Java Servlet Specification Version 2.4 applications saw a
performance degradation due to unoptimized functioning of the
annotations scanner. This occured even if they were not
configured to use annotations.

5. When ARD is run with Dynamic Caching enabled, there are
intermittent ConcurrentModificationExceptions such as the
following:

[9/16/08 16:50:46:160 CDT] 00000042 servlet    E
com.ibm.ws.webcontainer.servlet.ServletWrapper s
ervice SRVE0068E: Uncaught exception created in one of the
service methods of the
servlet /AsyncRequ
estDispatcherJSPManual.jsp in application
ERWW_ARD_JSP_Client_05_21_2008. Exception
created : com.ib
m.websphere.servlet.error.ServletErrorReport:
com.ibm.wsspi.ard.exception.ARDException: com.ibm.wssp
i.ard.exception.ARDException:
java.util.ConcurrentModificationException
        at
org.apache.jasper.runtime.PageContextImpl.handlePageException(Pa
geContextI
mpl.java:693)
        at
com.ibm._jsp._AsyncRequestDispatcherJSPManual._jspService(_Async
RequestDis
patcherJSPManua
l.java:114)
        at
com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:98)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at
com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWr
apper.java
:307)
        at
com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java
:574)
        at
com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:
250)
        at
com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.j
ava:259)

6. Microsoft Internet Explorer Memory Leak analyzers showed a
leak when using ARD client side aggregation. Eventually, the
browser could come unresponsive after many requests.


7. When running the WebSphere Administrative Agent, some
validation errors are seen in the administrative console.

The error was the following:

CHKW3630E: Load of platform features from
/wasv7config/bboadma/bboadma/AdminAgent/profiles/default/config/
cells/bbobase/bbonode/node-metadata.properties failed with
exception
/wasv7config/bboadma/bboadma/AdminAgent/profiles/default/config/
cells/bbobase/bbonode/node-metadata.properties (EDC5129I No
such file or directory.  (errno2=0x05620062)).

Full URI:
cells/bbobase/cell.xml

Validator classname:
com.ibm.websphere.validation.base.config.CellValidator

Problem conclusion

1. The ARD Channel code was changed to fix the order of
connection closing.
2. The URL for retrieving asynchronous include results was
modified to be context root relative so that the proxy can
determine where to route the request.
3. Request attributes required by dynacache were improperly
being removed. The change prevents them from being removed.
4. Application server code was optimized to use a stubbed out
annotation scanner for Java Servlet Specification Version 2.4
applications.
5. ThreadLocal implementation was used to pass the information
causing the ConcurrentModificationException.
6. Objects were properly dereferened.
7. Correct directories paths were used to point to the missing
properties file.

The fix for this APAR is currently targeted for inclusion
in fix pack 7.0.0.1.
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
PK71789
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-09
Closed date
2008-10-13
Last modified date
2008-10-13

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
23 October 2021

Tips

PK71789: INTERMITTENT NULLPOINTEREXCEPTION IN FINISHRESPONSEMESSAGE

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

Document Information

Share your feedback

Need support?