Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 52079 invoked from network); 15 Nov 2003 15:44:20 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Nov 2003 15:44:20 -0000 Received: (qmail 24908 invoked by uid 500); 15 Nov 2003 15:44:06 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 24887 invoked by uid 500); 15 Nov 2003 15:44:06 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 24873 invoked from network); 15 Nov 2003 15:44:06 -0000 Received: from unknown (HELO tsunami.skynet.be) (195.238.2.85) by daedalus.apache.org with SMTP; 15 Nov 2003 15:44:06 -0000 Received: from dboxp (194-78-168-55.pro.turboline.skynet.be [194.78.168.55]) by tsunami.skynet.be (8.12.9/8.12.9/Skynet-OUT-2.21) with SMTP id hAFFi2XB014677 for ; Sat, 15 Nov 2003 16:44:02 +0100 (envelope-from ) From: "Danny Bols" To: Subject: Cocoon 2.1.3 / Woody / Flow - Endless Loop? Date: Sat, 15 Nov 2003 16:44:01 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-RAVMilter-Version: 8.4.3(snapshot 20030212) (tsunami.skynet.be) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello, since a few days I have been using the new released Cocoon 2.1.3 and after a while without doing any requests to the server the java process spontaneously claims 100% of the CPU. Java behaves like it is in an endless loop. The only solution in that case is to hard kill the tomcat server! This behaviour only seems to happen when there has been a previously request (or requests) to the server which activated a woody flow form. Does anybody have any clue? Which component could possibly, without any client request, activate a process on the server? -- Danny --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org