cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9701] - Cocoon with avalon-framework-20020603.jar don't run with Tomcat (4.01, 4.03 and 4.04b3) and jdk1.3.0_02
Date Wed, 19 Jun 2002 09:17:21 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9701>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9701

Cocoon with avalon-framework-20020603.jar don't run with Tomcat (4.01, 4.03 and 4.04b3) and
jdk1.3.0_02

stuart.roebuck@adolos.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Critical
         OS/Version|Linux                       |All



------- Additional Comments From stuart.roebuck@adolos.co.uk  2002-06-19 09:17 -------
I think this bug is probably the same as my recent 12 hour nightmare of trying
to get 2.0.3 mounted on our main server.
The code worked fine on Mac OS X, but failed on our FreeBSD based
server (which has been happily running 2.0.2 for some considerable time), coming
up with a method not found error on the Initialize() method of
org.apache.avalon.excalibur.component.ComponentHandler.

I tried *a lot* of different configurations including Tomcat 4.0.1, 4.0.4 and
4.1, all of which resulted in the same output.  I tried all the different
configuration options suggested in the Cocoon FAQ for dealing with issues with
Tomcat 4.0.3 and had no luck.  I confirmed that there was only one instance of
the excalibur classes in the classpath.  Eventually I had to revert back to
2.0.2.

My guess having spent a long time trawling the archives, is that there is some
problem with the current packaged jar of avalon-excalibur-20020612.jar or
avalon-framework-20020603.jar which is interacting badly with the native code in the Java
VM on FreeBSD and Linux but not on Mac OS X.

I would really like to know what's wrong here as our workflow involves testing
on Mac OS X and deploying on FreeBSD, and up until two nights ago that workflow
worked very reliably indeed.

(Could this also be related to recent reports on cocoon-users or cocoon-dev of fixing Java
1.4 related problems by rebuilding excalibur?)

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message