Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 80140 invoked by uid 500); 3 Dec 2002 12:38:48 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 80128 invoked from network); 3 Dec 2002 12:38:48 -0000 From: Chris Faulkner To: cocoon-users@xml.apache.org Date: Tue, 03 Dec 2002 12:38:42 -0000 X-Priority: 3 (Normal) Reply-To: chrisf@oramap.com Organization: Oramap Ltd In-Reply-To: <008f01c29a15$1a464a00$c801a8c0@deepford> Message-Id: Subject: SVG - java socket exception MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" X-Mailer: Opera 6.04 build 1135 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello I am getting on OK with Cocoon. I like it very much. I am using some JSP code as a generator. This creates some XML data which I apply xsl to transform to SVG. This is then serialised with svgxml and returned to the client. It all works fine. Except that, looking at my logs, very often, the first execution of the JSP returns this to stdout/stderr. java.lang.RuntimeException: java.net.SocketException: Connection aborted by peer : socket write error at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java :3231) at java.lang.Thread.run(Thread.java:479) I can see in the logs that Cocoon automatically seems to fire the same JSP again. It then works on the next shot, I get my SVG displayed in my SVG viewing app and it is just fine. This is obviously slowing things up though. Any ideas - I am using Cocoon 2.0.3 on Tomcat 4.0.1, JDK 1.3.1_06 on W2K. Thanks Chris --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: