IBM Support

PM30108: CANNOT FORWARD. RESPONSE ALREADY COMMITTED ON SPNEGO SYSTEM

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The error is observed by following steps.
    
    1) Attempt to hit a security protected Connections page like
    
    /files/login from a non-SPNEGO client system
    
    2) Exception in logs:
    
    [9/9/10 10:03:14:783 CST] 0000004b LotusConnecti E     Cannot
    forward. Response already committed.
    
    java.lang.IllegalStateException:
    Cannot forward. Response already committed.
    at
    com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward
    (WebAppRequestDispatcher.java:169)
     at com.ibm.ws.webcontainer.servlet.FilterProxyServlet.dispatch
    (FilterProxyServlet.java:88)
     at com.ibm.ws.webcontainer.servlet.FilterProxyServlet.service
    (FilterProxyServlet.java:62)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service
    (ServletWrapper.java:1655)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service
    (ServletWrapper.java:1595)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who configure SPNEGO (The Simple     *
    *                  and Protected GSS-API Negotiation           *
    *                  authentication for Lotus Connection         *
    ****************************************************************
    * PROBLEM DESCRIPTION: "Cannot forward. Response already       *
    *                      committed." error is thrown in the log  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When user tries to access Lotus Connection application from a
    machine that is not part of the domain, SPNEGO token is not
    sent to WebSphere Application Server.  In this case, SPNEGO
    authentication fails and the Application Server commits the
    response to show "NTLM Token received" error page.  At the
    same time the Lotus Connection application tries to forward
    the page to its main login page because SPNEGO authentication
    did not happen.  This will cause many error messages in the
    log.  After the error message, user is eventually presented
    Lotus Connection main login page.
    

Problem conclusion

  • Code has been updated in WebSphere Application Server so Lotus
    Connection will not encounter page forwarding error when NTLM
    token is received. The code also handles the case when Lotus
    Connection is not installed so the error page is presented on
    the browser.
    
    APAR is currently targeted for
    inclusion in
    fix pack 7.0.0.17.  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

    PM30108

  • 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

    2011-01-10

  • Closed date

    2011-02-17

  • Last modified date

    2011-02-17

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM30108

Modified date: 17 February 2011