Hi, I'm running a Restlet (1.0.7) webserver and recently implemented an AJAXish call using the Yahoo UI Connect library. It normally works but on some edge case I haven't found, it causes the server to spurt a literally endless stream of these exceptions:
Jan 25, 2008 6:01:45 PM com.noelios.restlet.util.FormReader addParameters WARNING: Unable to parse a form parameter. Skipping it. java.io.IOException: Stream closed at simple.http.MonitoredInputStream.ensureOpen(MonitoredInputStream.java:184) at simple.http.MonitoredInputStream.read(MonitoredInputStream.java:83) at java.io.FilterInputStream.read(FilterInputStream.java:66) at com.noelios.restlet.util.FormReader.readNextParameter(FormReader.java:231) at com.noelios.restlet.util.FormReader.addParameters(FormReader.java:308) at com.noelios.restlet.util.FormUtils.parsePost(FormUtils.java:92) at com.noelios.restlet.Engine.parse(Engine.java:815) at org.restlet.data.Form.<init>(Form.java:73) at org.restlet.data.Form.<init>(Form.java:99) at org.restlet.data.Message.getEntityAsForm(Message.java:150) ...from calling request.getEntityAsForm() in a Restlet handler. It got stuck in an endless loop of these lines and was stuck there for almost 24 hours before I noticed the logfile was eating up the disk (not to mention near 100% of the CPU). Anyone have experience with this or any ideas of what to look for if I trap an IOException coming from this call? (I've wrapped the getEntityAsForm() call in a try/catch handler, so hopefully the first time an IOException is fired I can just kill the request.) Thanks, Mike
