THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Now, although there shouldn't be any Exception logged (because the IOException which occurs when the client aborted the connection is ignored), you see strange Exceptions in Tomcat's log which may belong to other Servlets/JSP (at least with Sun/Oracle JVM on Windows), saying that the response has already commitedbeen committed, althought although you didn't write anything to it at that time. For example:
...
To resolve this, I'm using an OutputStream decorater decorator class which decorates Tomcat's OutputStream and prevents any flush() calls. Additionally, when close() is called on that Stream, it nulls-out the reference to Tomcat's OutputStream and prevents any other operations:
| No Format |
|---|
/**
* A OutputStream which can be used to write Images
* with the ImageIO in servlets.
*/
public class MyImageIOOutputStream extends OutputStream {
private OutputStream out;
private volatile boolean isActive = true;
public MyImageIOOutputStream(OutputStream out) {
this.out = out;
}
@Override
public void close() throws IOException {
if (isActive) {
isActive = false; // deactivate
try {
out.close();
} finally {
out = null;
}
}
}
@Override
public void flush() throws IOException {
if(isActive) {
out.flush();
}
// otherwise do nothing (peventprevent polluting the stream)
}
@Override
public void write(byte[] b, int off, int len) throws IOException {
if (isActive)
out.write(b, off, len);
}
@Override
public void write(byte[] b) throws IOException {
if (isActive)
out.write(b);
}
@Override
public void write(int b) throws IOException {
if (isActive)
out.write(b);
}
}
|
...