type Exception report
message java.io.IOException: There is not enough space on the disk
description The server encountered an internal error that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: java.io.IOException: There is not enough space on the disk org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:549) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:460) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) javax.servlet.http.HttpServlet.service(HttpServlet.java:727) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
root cause
java.io.IOException: There is not enough space on the disk java.io.FileOutputStream.writeBytes(Native Method) java.io.FileOutputStream.write(Unknown Source) sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) sun.nio.cs.StreamEncoder.implWrite(Unknown Source) sun.nio.cs.StreamEncoder.write(Unknown Source) java.io.OutputStreamWriter.write(Unknown Source) java.io.BufferedWriter.flushBuffer(Unknown Source) java.io.BufferedWriter.close(Unknown Source) com.bks.jsp.target.CatalogCollection.loadSubscribers(CatalogCollection.java:516) org.apache.jsp.tag.webuse_002dheaders_tag.doTag(webuse_002dheaders_tag.java:224) org.apache.jsp.about.members_005fregion_jsp._jspx_meth_sigla_005fuse_002dheaders_005f0(members_005fregion_jsp.java:226) org.apache.jsp.about.members_005fregion_jsp._jspService(members_005fregion_jsp.java:76) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:727) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) javax.servlet.http.HttpServlet.service(HttpServlet.java:727) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
note The full stack trace of the root cause is available in the Apache Tomcat/7.0.52 logs.