getOutputStream has already been called for this response

Question

I google the error message getOutputStream   has already been called for this response and many people said it is because of the space or newline after  lt   or   gt   but in my code   there is no a space or a newline  I am using tomcat6 on linux    lt        page import  java servlet        javax servlet http        java io        java util        com lowagie text pdf        com lowagie text          gt  lt       response setContentType  application pdf        Document document   new Document        try          ByteArrayOutputStream buffer   new ByteArrayOutputStream            PdfWriter getInstance document  buffer           document open            PdfPTable table   new PdfPTable 2           table addCell  1            table addCell  2            table addCell  3            table addCell  4            table addCell  5            table addCell  6            document add table           document close            DataOutput dataOutput   new DataOutputStream response getOutputStream             byte   bytes   buffer toByteArray            response setContentLength bytes length           for int i   0  i  lt  bytes length  i                      dataOutput writeByte bytes i                   catch DocumentException e           e printStackTrace             gt       org apache jasper JasperException  java lang IllegalStateException  getOutputStream   has already been called for this response     org apache jasper servlet JspServletWrapper handleJspException JspServletWrapper java 522      org apache jasper servlet JspServletWrapper service JspServletWrapper java 410      org apache jasper servlet JspServlet serviceJspFile JspServlet java 342      org apache jasper servlet JspServlet service JspServlet java 267      javax servlet http HttpServlet service HttpServlet java 717    root cause   java lang IllegalStateException  getOutputStream   has already been called for this response     org apache catalina connector Response getWriter Response java 610      org apache catalina connector ResponseFacade getWriter ResponseFacade java 198      org apache jasper runtime JspWriterImpl initOut JspWriterImpl java 125      org apache jasper runtime JspWriterImpl flushBuffer JspWriterImpl java 118      org apache jasper runtime PageContextImpl release PageContextImpl java 188      org apache jasper runtime JspFactoryImpl internalReleasePageContext JspFactoryImpl java 118      org apache jasper runtime JspFactoryImpl releasePageContext JspFactoryImpl java 77      org apache jsp Account Domain testPDF jsp  jspService testPDF jsp java 94      org apache jasper runtime HttpJspBase service HttpJspBase java 70      javax servlet http HttpServlet service HttpServlet java 717      org apache jasper servlet JspServletWrapper service JspServletWrapper java 374      org apache jasper servlet JspServlet serviceJspFile JspServlet java 342      org apache jasper servlet JspServlet service JspServlet java 267      javax servlet http HttpServlet service HttpServlet java 717

User · Answer

JSP is s presentation framework  and is generally not supposed to contain any program logic in it  As skaffman suggested  use pure servlets  or any MVC web framework in order to achieve what you want

User · Answer

I just experienced this problem    The problem was caused by my controller method attempting return type of String  view name  when it exits  When the method would exit  a second response stream would be initiated    Changing the controller method return type to void resolved the problem   I hope this helps if anyone else experiences this problem

User · Answer

This error was occuring in my program because the resultset was calling more columns to be displayed in the PDF Document than the database contained  For example  the table contains 30 fields but the program was calling 35  resultset getString 35

User · Answer

Here is what worked for me in similar case   After you finish writing into the Servlet OutputStream just call response sendRedirect  yourPage jsp     That would cause initiation of a new request from the browser  therefore avoid writing into the same output stream

User · Answer

Ok  you should be using a servlet not a JSP but if you really need to     add this directive at the top of your page    lt    page trimDirectiveWhitespaces  true    gt    Or in the jsp-config section your web xml   lt jsp-config gt     lt jsp-property-group gt       lt url-pattern gt   jsp lt  url-pattern gt       lt trim-directive-whitespaces gt true lt  trim-directive-whitespaces gt     lt  jsp-property-group gt   lt  jsp-config gt    Also flush close the OutputStream and return when done   dataOutput flush    dataOutput close    return

User · Answer

In some cases this case occurs when you declare                               Writer out response getWriter      after declaring or using RequestDispatcher    I encountered this similar problem while creating a simple LoginServlet  where I have defined Writer after declaring RequestDispatcher   Try defining Writer class object before RequestDispatcher class

User · Answer

Use Glassfish 4 0 instead  This turns out to be a problem only in Glassfish 4 1 1 release    PT-BR  Use o Glasfish 4 0  Este parece ser um problema apenas no Glassfish 4 1 1

User · Answer

I had this problem only the second time I went to export  Once I added   response getOutputStream   flush    response getOutputStream   close      after the export was done  my code started working all of the time

User · Answer

The issue here is that your JSP is talking directly to the response OutputStream  This technically isn t forbidden  but it s very much not a good idea   Specifically  you call response getOutputStream   and write data to that  Later  when the JSP engine tries to flush the response  it fails because your code has already  claimed  the response  An application can either call getOutputStream or getWriter on any given response  it s not allowed to do both  JSP engines use getWriter  and so you cannot call getOutputStream   You should be writing this code as a Servlet  not a JSP  JSPs are only really suitable for textual output as contained in the JSP  You can see that there s no actual text output in your JSP  it only contains java

User · Answer

I didn t use JSP but I had similar error when I was setting response to return JSON object by calling  PrintWriter s flush   method or return statement  Previous answer i e wrapping return-statement into a try-block worked kind of  the error disappeared because return-statement makes method to ignore all code below try-catch  specifically in my case  line redirectStrategy sendRedirect request  response  destination addr string  which seem to modify the already committed response that causes the error  The simpler solution in my case was just to remove the line and let client app to take care of the redirection

User · Answer

I got the same problem  and I solved just adding  return    at the end of the FileInputStream   Here is my JSP   x000D   x000D   lt    page language  java  contentType  text html  charset ISO-8859-1  x000D   pageEncoding  ISO-8859-1   gt  x000D   lt    page import  java io     gt  x000D   lt    page trimDirectiveWhitespaces  true   gt  x000D   x000D   lt   x000D   x000D   try   x000D    FileInputStream ficheroInput   new FileInputStream  C   export x web pdf    x000D    int tamanoInput   ficheroInput available    x000D    byte   datosPDF   new byte tamanoInput   x000D    ficheroInput read datosPDF  0  tamanoInput   x000D   x000D    response setHeader  Content-disposition    inline  filename export sise web pdf    x000D    response setContentType  application pdf    x000D    response setContentLength tamanoInput   x000D    response getOutputStream   write datosPDF   x000D   x000D    response getOutputStream   flush    x000D    response getOutputStream   close    x000D   x000D    ficheroInput close    x000D    return  x000D   x000D     catch  Exception e    x000D   x000D     x000D    gt  x000D   x000D   lt  body gt  x000D   lt  html gt  x000D   x000D   x000D

User · Answer

Add the following inside the end of the try catch to avoid the error that appears when the JSP engine flushes the response via getWriter    out clear       where out is a JspWriter out   pageContext pushBody      As has been noted  this isn t best practice  but it avoids the errors in your logs

User · Answer

I got the same error by using response getWriter   before a request getRequestDispatcher path  forward request  response    So start works fine when I replace it by response getOutputStream

[java] getOutputStream() has already been called for this response

Examples related to java

Examples related to jsp

Examples related to tomcat