JR48807: JSP BUFFER OVERFLOW IN CUSTOM JSP

IBM InfoSphere Master Data Management Collaboration Server Version 11.4.0, Fix Pack 3
InfoSphere Information Server, Version 11.3 for Microsoft Windows
InfoSphere Information Server, Version 11.3 for AIX
InfoSphere Information Server, Version 11.3 for Linux
IBM InfoSphere Information Server Enterprise Edition V11.3 for Windows

APAR status

• Closed as program error.

Error description

• When customer attempted to output large data via custom jsp,
  they will get the UI error while openning the custom tool.
  
  For example, create the following custom tool script and save:
  <%
  for(var i=0; i<=1500;i++){
  out.println("<table><tr><td>" + i + "</td></tr></table>");
  }
  %>
  
  When you open this custom tool from menu, you will get UI error
   HTTP500: The webpage can not be displayed.
  
  Meanwhile, the following error stack can be found in
  appsvr/default.log:
  2013-12-11 08:30:33,813 [jsp_485: /utils/custom_page.jsp] ERROR
  jsp.footer - CWPCM0002E:Generic error / Exception: Not an
  AustinException, Exception:jsp.error.overflow
  java.io.IOException: jsp.error.overflow
          at
  org.apache.jasper.runtime.JspWriterImpl.bufferOverflow(JspWriter
  Impl.java:318)
          at
  org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java
  :538)
          at
  org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java
  :548)
          at utils.custom_page._jspService(Unknown Source)
          at
  com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspB
  ase.java:103)
          at
  javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
          at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
  apper.java:1225)
          at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
  vletWrapper.java:775)
          at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
  vletWrapper.java:457)
          at
  com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest
  (ServletWrapperImpl.java:178)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(We
  bAppFilterChain.java:136)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
  FilterChain.java:97)
          at
  com.ibm.ccd.ui.filters.FuzaoRequestFilter.doFilter(FuzaoRequestF
  ilter.java:82)
          at
  com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi
  lterInstanceWrapper.java:195)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
  FilterChain.java:91)
          at
  com.ibm.ccd.ui.filters.ResponseHeaderFilter.doFilter(ResponseHea
  derFilter.java:72)
          at
  com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi
  lterInstanceWrapper.java:195)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
  FilterChain.java:91)
          at
  com.ibm.ccd.ui.filters.ResponseHeaderFilter.doFilter(ResponseHea
  derFilter.java:72)
          at
  com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi
  lterInstanceWrapper.java:195)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
  FilterChain.java:91)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
  ppFilterManager.java:928)
          at
  com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters
  (WebAppFilterManager.java:1025)
          at
  com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:
  3761)
          at
  com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.j
  ava:304)
          at
  com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
  java:975)
          at
  com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai
  ner.java:1662)
          at
  com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin
  k.java:195)
          at
  com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
  imination(HttpInboundLink.java:459)
          at
  com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRe
  quest(HttpInboundLink.java:526)
          at
  com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ
  est(HttpInboundLink.java:312)
          at
  com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet
  e(HttpICLReadCallback.java:87)
          at
  com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp
  leted(AioReadCompletionListener.java:165)
          at
  com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn
  cFuture.java:217)
          at
  com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC
  hannelFuture.java:161)
          at
  com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
          at
  com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
          at
  com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand
  ler.java:775)
          at
  com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
          at
  com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1815)
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Master Data Management Collaboration Server              *
  * implementations are affected by this issue.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Custom tool script / JSP attempting to output data greater   *
  * than 64 KB resulted in buffer overflow exception.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * IBM recommends that customers facing the issue reported by   *
  * this APAR apply Master Data Management Collaboration Server  *
  * version 11.0.0-FP3 to gain resolution to this problem.       *
  ****************************************************************
  

Problem conclusion

• A fix for this problem has been included in Master Data
  Management Collaboration Server version 11.0.0-FP3.
  

Temporary fix

Comments

APAR Information

• 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

  MDM SERVER FOR

• Fixed component ID

  5724V5100

Applicable component levels

• RB00 PSY

     UP