Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 1186 invoked by uid 500); 3 Apr 2003 14:07:56 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 1170 invoked from network); 3 Apr 2003 14:07:56 -0000 Received: from onramp.i95.net (205.177.132.17) by daedalus.apache.org with SMTP; 3 Apr 2003 14:07:56 -0000 Received: from apache.org ([66.208.12.130]) by onramp.i95.net (8.12.9/8.12.9) with ESMTP id h33E7u0G023059 for ; Thu, 3 Apr 2003 09:07:56 -0500 Message-ID: <3E8C403C.8090904@apache.org> Date: Thu, 03 Apr 2003 09:07:56 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: AbstractMethodError: org/apache/excalibur/event/impl/Abstract Queue.enqueue References: <3E8C2F4E.7040505@apache.org> <3E8C3E28.1000002@apache.org> In-Reply-To: <3E8C3E28.1000002@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Berin Loritsch wrote: > Berin Loritsch wrote: > >> Jonathan Spaeth wrote: >> >>> Did anybody ever figure out this problem? I seem to be experiencing >>> it as well. >>> >>> I am running a tomcat application server version 4.1.24 on a freebsd >>> server. >>> I just compiled a fresh snapshot of the cvs repository and have >>> received this error exploding through my logs. >>> >>> What I mean by "exploding through my logs" is that the first time the >>> cocoon webapp is initialized, the exceptions start flowing and they >>> do not stop. They are stored in the log files and the log files just >>> keep growing because the exceptions are being constantly thrown. >>> >>> Has anybody else experienced this? >> >> > > I applied the current prerelease JAR (which is what Event-1.0.2 was) > to CVS. I ran the tests and have not received any abstract queue > errors. I am running docs now, and will examine the logs. > > There *shouldn't* be any problems. I will report back when the > docs are built. All is well. Please get a fresh checkout from CVS and retry. One major thing to watch out for: make sure you do not have conflicing JARs in your classpath. If you have an old version of Event in your WEB-INF/lib directory along with the new one, there is a good chance you are not seeing a new abstract method because the old class is being loaded. Please double-check your JARs