IBM Support

PI21875: ODR RETURNS 500 BECAUSE OF A NULL POINTER EXCEPTION IN RESPONSE FILTER WHEN THE REQUEST IS SERVED FROM THE CACHE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The stack trace for the NPE is shown below:
    
    [07/03/14 11:30:09:790 EDT] 00000018 HttpFilterCha 3
    BBOO0220E:
    PROX0050E: Caught unhandled exception from doFilter in filter=XD
    trace route response filter.
    
    exception=java.lang.NullPointerException      at
    com.ibm.ws.xd.dwlm.client.filter.TraceRouteResponseFilter.doFilt
    er(Trace
    RouteResponseFilter.java:52) at
    com.ibm.ws.proxy.filter.http.HttpFilterImpl.doFilter(HttpFilterI
    mpl.java
    :98) at
    com.ibm.ws.proxy.filter.http.HttpFilterChain.doLocalResponseFilt
    erChain(
    HttpFilterChain.java:616)    at
    com.ibm.ws.proxy.filter.http.HttpFilterChain.doResponseFilterCha
    in(HttpF
    ilterChain.java:564) at
    com.ibm.ws.proxy.filter.http.HttpFilterChain.processRequestFilte
    rError(H
    ttpFilterChain.java:543)     at
    com.ibm.ws.proxy.filter.http.HttpFilterChain.doRequestFilterChai
    n(HttpFi
    lterChain.java:455)  at
    com.ibm.ws.proxy.filter.http.HttpFilterChain.doRequestFilterChai
    nWrapper
    (HttpFilterChain.java:263)   at
    com.ibm.ws.proxy.filter.http.HttpFilterChain.doRequestFilterChai
    n(HttpFi
    lterChain.java:242)  at
    com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.processReq
    uestWork
    (HttpProxyConnectionLink.java:566)   at
    com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.ready(Http
    ProxyCon
    nectionLink.java:328)        at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
    iminatio
    n(HttpInboundLink.java:453)  at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRe
    quest(Ht
    tpInboundLink.java:515)      at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ
    est(Http
    InboundLink.java:306)        at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpI
    nboundLi
    nk.java:277) at
    com.ibm.ws.tcp.channel.impl.ZAioTCPChannel.newConnectionCommon(Z
    AioTCPCh
    annel.java:754)      at
    com.ibm.ws.tcp.channel.impl.ZAioTCPChannel.readCompletedNewConne
    ction(ZA
    ioTCPChannel.java:579)       at
    com.ibm.ws.tcp.channel.impl.ZAioTCPChannelCPPUtilities.readCompl
    etedNewC
    onnection(ZAioTCPChannelCPPUtilities.java:158).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of Websphere Virtual Enterprise   *
    *                  7.0.0.5/Websphere Virtual Enterprise        *
    *                  8.5.5.3 and below who have the JVM          *
    *                  argument traceRouteHeader set on On Demand  *
    *                  Router(ODR)                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When ODR is started with                *
    *                      with traceRouteHeader as a JVM          *
    *                      argument, for e.g,                      *
    *                      "-DODR.traceRouteHeader=TraceRoute",    *
    *                      and a response is served from the       *
    *                      cache, a null pointer exception is      *
    *                      thrown.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a request is served from the cache in the ODR, the
    destination of the request is the ODR itself. However, we were
    not setting the address of the ODR as the destination.
    Instead, it was null. The Null Pointer Exception was thrown
    when we were trying to use the destination address in trace
    route.
    

Problem conclusion

  • The code has been changed to set the address of the ODR as the
    destination whenever the request is served from the
    cache now. The fix will be available in the
    next available fix pack for WebSphere Virtual Enterprise V7.0
    and V.8.5.5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI21875

  • Reported component name

    WEBSP VIRTUAL E

  • Reported component ID

    5655V6403

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-14

  • Closed date

    2014-09-08

  • Last modified date

    2014-09-08

  • 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

    WEBSP VIRTUAL E

  • Fixed component ID

    5655V6403

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7.0"}]

Document Information

Modified date:
07 September 2021