Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 80977 invoked from network); 10 Nov 2005 09:51:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Nov 2005 09:51:49 -0000 Received: (qmail 89174 invoked by uid 500); 10 Nov 2005 09:51:43 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 89144 invoked by uid 500); 10 Nov 2005 09:51:43 -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 List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 89133 invoked by uid 99); 10 Nov 2005 09:51:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Nov 2005 01:51:43 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of felix.roethenbacher@wyona.com designates 195.226.6.68 as permitted sender) Received: from [195.226.6.68] (HELO mx1.wyona.com) (195.226.6.68) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Nov 2005 01:51:35 -0800 Received: from [195.226.6.66] (helo=[192.168.1.41]) by mx1.wyona.com with esmtp (Exim 3.35 #1 (Debian)) id 1Ea95S-0005kX-00 for ; Thu, 10 Nov 2005 10:51:18 +0100 Message-ID: <43731829.4080302@wyona.com> Date: Thu, 10 Nov 2005 10:51:37 +0100 From: =?ISO-8859-1?Q?Felix_R=F6thenbacher?= User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Accept timed out Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi I just updated the Jetty implementation in Lenya to version 5.1.4. There is an issue with SocketTimeoutExceptions which seems to be related to the scheduler. Cocoon_QuartzSchedulerThread DEBUG lenya.scheduler - Got a $Proxy12 from the pool. Cocoon_QuartzSchedulerThread DEBUG scheduler.conn - Pinging database after 27275ms of inactivity. Cocoon_QuartzSchedulerThread DEBUG jdbcjobstore.SimpleSemaphore - Lock 'TRIGGER_ACCESS' is desired by: Cocoon_QuartzSchedulerThread Cocoon_QuartzSchedulerThread DEBUG jdbcjobstore.SimpleSemaphore - Lock 'TRIGGER_ACCESS' is being obtained: Cocoon_QuartzSchedulerThread Cocoon_QuartzSchedulerThread DEBUG jdbcjobstore.SimpleSemaphore - Lock 'TRIGGER_ACCESS' given to: Cocoon_QuartzSchedulerThread Cocoon_QuartzSchedulerThread DEBUG jdbcjobstore.SimpleSemaphore - Lock 'TRIGGER_ACCESS' retuned by: Cocoon_QuartzSchedulerThread This seems to lead to a SocketTimeoutException: java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.mortbay.util.ThreadedServer.acceptSocket(ThreadedServer.java:432) at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:631) What might this exception mean in this context? Thanks for your help - Felix -- Felix R�thenbacher felix.roethenbacher@wyona.com Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org