PQ72720: RESPONSE OBJECT IS NOT COMMITTED AFTER SENDREDIRECT() FOR THE FIRST TIME SERVLET IS CALLED. | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Response object is not commited after sendRedirect() for the first time. From second time onwards, response object is committed after sendRedirect() Actually, response should be committed after the sendRedirect(). . Customer also noticed that sometimes, even in subsequent sendRedirects() response will not be committed.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server Version 4.0 * * users of HttpServletResponse.sendRedirect(). * **************************************************************** * PROBLEM DESCRIPTION: After calling sendRedirect(), the check * * for isCommitted fails to return true. * * This is in violation of the Servlet * * 2.2 specification. * **************************************************************** * RECOMMENDATION: * **************************************************************** A sendRedirect() relies on flushing the response buffer to commit. The buffer is not fully initialized and the buffer can be empty. In that case, the flush buffer does nothing and the response is not committed.Problem conclusion A sendRedirect should call commit() explicitly. The commit() flushes the buffer when necessary, and sets the committed status to true.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ72720
IBM Group: Software Group
Modified date: Apr 29, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.