Hello Shane, latest build from CVS still generates this error periodically. | [#|2007-12-05T13:48:50.106-0500|SEVERE|sun-appserver9.1|org.jboss.seam.remoting.Remoting|_ThreadID=20;_ThreadName=httpSSLWorkerThread-38080-1;_RequestID=b24ed108-c908-43e6-81c5-bbf9ccc60b3b;|Error | org.dom4j.DocumentException: Error on line 1 of document : Premature end of file. Nested exception: Premature end of file. | at org.dom4j.io.SAXReader.read(SAXReader.java:482) | at org.dom4j.io.SAXReader.read(SAXReader.java:365) | at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:57) | at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) | at org.jboss.seam.servlet.SeamResourceServlet.doGet(SeamResourceServlet.java:75) | at org.jboss.seam.servlet.SeamResourceServlet.doPost(SeamResourceServlet.java:92) | "shane.bryzak(a)jboss.com" wrote : The request packet looks well-formed and complete, it's not clear why the exception is being thrown. Just to try something different, I've wrapped the request's InputStream in an InputStreamReader for the parsing of the xml. You can try this in the latest CVS version. | | "samdoyle" wrote : | | Some questions though. | | | | 1.) Why are each of the response packets incrementing in conversation id? | | 2.) Why do sometimes when I make a request it appears I get pack an empty response followed by a valid response? | | | | 1. Unless you explicitly set the conversation ID yourself (see the remoting docs) then whatever conversation ID is current at the end of the request will be sent back in the remoting response. | 2. I've never seen anything like this, could you give me an example? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110675#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...