RE: AbstractMethodError: org/apache/excalibur/event/impl/Abstract Queue.enqueue

[Jonathan Spaeth <Jo...@networktelephone.net>]

Berin

I am still experiencing the same behavior when trying to build the latest
cocoon.  I am unable to find any references to Event-1.0.2.  Are you
speaking of the excalibur-event-20030403.jar?
Either way, here is a list of the jar files in my environment:

TOMCAT LIBS:
common/endorsed:
xercesImpl.jar
xmlParserAPIs.jar

common/lib:
activation.jar
ant.jar
commons-collections.jar
commons-dbcp.jar
commons-logging-api.jar
commons-pool.jar
jasper-compiler.jar
jasper-runtime.jar
jdbc2_0-stdext.jar
jndi.jar
jta.jar
mail.jar
naming-common.jar
naming-factory.jar
naming-resources.jar
servlet.jar

server/lib:
catalina-ant.jar
catalina.jar
commons-beanutils.jar
commons-digester.jar
commons-fileupload-1.0-beta-1.jar
commons-logging.jar
commons-modeler.jar
jaas.jar
jakarta-regexp-1.2.jar
mx4j-jmx.jar
servlets-common.jar
servlets-default.jar
servlets-invoker.jar
servlets-manager.jar
servlets-webdav.jar
tomcat-coyote.jar
tomcat-http11.jar
tomcat-jk.jar
tomcat-jk2.jar
tomcat-util.jar
tomcat-warp.jar

COCOON LIBS:
altrmi-common-0.9.2.jar
altrmi-registry-0.9.2.jar
altrmi-server-impl-0.9.2.jar
altrmi-server-interfaces-0.9.2.jar
avalon-framework-4.1.4.jar
axis-1.0.jar
axis-jaxrpc-1.0.jar
axis-saaj-1.0.jar
bsf-2.2.jar
castor-0.9.4.2-xml.jar
cocoon-2.1-dev-deprecated.jar
cocoon-2.1-dev-scratchpad.jar
cocoon-2.1-dev.jar
cocoon-authentication-fw-block.jar
cocoon-axis-block.jar
cocoon-bsf-block.jar
cocoon-databases-block.jar
cocoon-hsqldb-block.jar
cocoon-html-block.jar
cocoon-linkrewriter-block.jar
cocoon-lucene-block.jar
cocoon-mail-block.jar
cocoon-naming-block.jar
cocoon-portal-fw-block.jar
cocoon-precept-block.jar
cocoon-proxy-block.jar
cocoon-session-fw-block.jar
cocoon-taglib-block.jar
cocoon-xmldb-block.jar
commons-cli-1.0.jar
commons-collections-2.1.jar
commons-discovery.jar
commons-httpclient-20030210.jar
commons-jexl-1.0-beta-1.jar
commons-jxpath-1.1.jar
commons-lang-1.0.1.jar
commons-logging-1.0.2.jar
excalibur-collections-20020820.jar
excalibur-component-1.1.jar
excalibur-concurrent-20020820.jar
excalibur-datasource-vm13-20021121.jar
excalibur-event-20030403.jar
excalibur-i18n-1.0.jar
excalibur-instrument-1.0.jar
excalibur-instrument-manager-1.0.jar
excalibur-instrument-manager-interfaces-1.0.jar
excalibur-io-1.1.jar
excalibur-logger-1.0.1.jar
excalibur-monitor-20020820.jar
excalibur-naming-1.0.jar
excalibur-pool-1.2.jar
excalibur-sourceresolve-20030404.jar
excalibur-store-20030317.jar
excalibur-util-1.0.jar
excalibur-xmlutil-20030317.jar
hsqldb-1.7.1.jar
jakarta-regexp-1.2.jar
jaxen-core-1.0-FCS.jar
jaxen-dom-1.0-FCS.jar
jdom-dev-20020131.jar
jdtcore2.0.2.jar
jing-20020724.jar
jisp-2.0.1.jar
jstyle.jar
jtidy-04aug2000r7-dev.jar
logfactor5-1.2.8.jar
logkit-1.2.jar
lucene-1.2.jar
pizza-1.1.jar
resolver-20021114.jar
rhino1.5r4-continuations-20030323.jar
saxpath-1.0-FCS.jar
util.concurrent-1.3.1.jar
velocity-1.4-dev-20030301.jar
wsdl4j.jar
xalan-2.4.1.jar
xercesImpl-2.1.0.jar
xml-apis.jar
xmldb-api-20011111.jar
xsltc-20030211.jar

Thanks for your help,
Jon

-----Original Message-----
From: Berin Loritsch [mailto:bloritsch@apache.org]
Sent: Thursday, April 03, 2003 8:08 AM
To: cocoon-dev@xml.apache.org
Subject: Re: AbstractMethodError:
org/apache/excalibur/event/impl/Abstract Queue.enqueue


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