You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by "Geoffrey T. Falk" <gt...@cirp.org> on 2003/06/11 07:28:56 UTC
James 2.1.3 has incompatible cornerstone.jar
I am having trouble trying to build and run James 2.1.3 with Phoenix
4.0.4.
There is an incompatible cornerstone.jar in the James lib directory
distributed with 2.1.3. This cornerstone.jar contains a
more-than-2-years-old version of some packages, including the class
org.apache.avalon.cornerstone.blocks.scheduler.DefaultTimeScheduler
(the first place where I run into trouble).
Why do the latest distributions not work together?
What is the correct order of building Avalon, Excalibur and Phoenix
components in order to get James to work?
TIA
Geoffrey
------------------
boojum% bin/run.sh
Using PHOENIX_HOME: /home/gtf/java-apps/james-2.1.3/dist/james-2.1.3
Using PHOENIX_TMPDIR: /home/gtf/java-apps/james-2.1.3/dist/james-2.1.3/temp
Using JAVA_HOME: /usr/local/jdk1.4.1
Running Phoenix:
Phoenix 4.0.4
org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component named "scheduler" failed to pass through the Starting stage. (Reason: java.lang.NoSuchMethodError: org.apache.avalon.excalibur.thread.ThreadPool.execute(Ljava/lang/Runnable;)Lorg/apache/avalon/excalibur/thread/ThreadControl;).
at org.apache.excalibur.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:289)
at org.apache.excalibur.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:159)
at org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:481)
at org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:429)
at org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:365)
at org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:139)
at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:251)
at org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(DefaultKernel.java:178)
at org.apache.avalon.phoenix.components.kernel.DefaultKernel.addApplication(DefaultKernel.java:254)
at org.apache.avalon.phoenix.components.deployer.DefaultDeployer.deploy(DefaultDeployer.java:353)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployFile(DefaultEmbeddor.java:498)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployFile(DefaultEmbeddor.java:491)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployFiles(DefaultEmbeddor.java:476)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.deployDefaultApplications(DefaultEmbeddor.java:466)
at org.apache.avalon.phoenix.components.embeddor.DefaultEmbeddor.execute(DefaultEmbeddor.java:224)
at org.apache.avalon.phoenix.frontends.CLIMain.run(CLIMain.java:158)
at org.apache.avalon.phoenix.frontends.CLIMain.execute(CLIMain.java:144)
at org.apache.avalon.phoenix.frontends.CLIMain.main(CLIMain.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.avalon.phoenix.launcher.Main.startup(Main.java:94)
at org.apache.avalon.phoenix.launcher.Main.main(Main.java:46)
Caused by: java.lang.NoSuchMethodError: org.apache.avalon.excalibur.thread.ThreadPool.execute(Ljava/lang/Runnable;)Lorg/apache/avalon/excalibur/thread/ThreadControl;
at org.apache.avalon.cornerstone.blocks.scheduler.DefaultTimeScheduler.start(DefaultTimeScheduler.java:253)
at org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:251)
at org.apache.excalibur.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:152)
... 22 more
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: James 2.1.3 has incompatible cornerstone.jar
Posted by Oki DZ <ok...@pindad.com>.
Hi,
I'm pretty new on this list; ready to upgrade to 2.2.x.
On Tue, Jun 10, 2003 at 11:56:17PM -0600, Geoffrey T. Falk wrote:
> On 10 Jun, To: james-user@jakarta.apache.org wrote:
> > I am having trouble trying to build and run James 2.1.3 with Phoenix
> > 4.0.4.
>
> FYI: James 2.2.0a4 has the same problem. Only now I get the error at
> compile-time:
Mine was on run-time. I don't remember what version; 2.1.3 or 2.2.0a4.
The problem was on execute method that couldn't be found on some class
(was it ThreadPool?). Anyway, the one from the binary download
directory works fine now.
Oki
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
RE: James 2.1.3 has incompatible cornerstone.jar
Posted by "Noel J. Bergman" <no...@devtech.com>.
>>>Asnwer #1: You don't. You use the binary distribution of Phoenix that is
>>>packaged with James.
>> Thanks, but I really want to build this stuff from source. That way I
>> know there is not any voodoo magic going on :-) plus I can study the
>> source. I will wait for the next version if I have to.
>I can assure you there is voodoo magic going on. :) Anyone who could
>identify what source James is using and help us or the Avalon folks tag
>their CVS modules would be owed favors by many.
Don't bother trying. :-) I've done it for some modules, as did Stephen
McConnell. Some of the stuff we were given to use not only isn't tagged, it
is barely in the CVS. More than a few are actually in the Attic. They
completely reorganized their CVS modules, deprecated classes, moved classes,
etc. Just to build a compatible version of the ThreadManager was a
multi-hour (I think it took me about 6 hours) scavenger hunt to find the
matching sources.
> The next release of James and Avalon are many many months away at best.
Avalon has Release builds of Logkit (we have that in both branches),
Frameworks and Excalibur. They are about to start working on Cornerstone.
The priority is to have the classes that James needs in the release. Once
they have completed their release cycle, which is just bugfixes and getting
a coordinated build of their own packages, it probably makes sense for us to
pick it up. That would address the current sitution, where not even Avalon
knows what they gave us to use. :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: James 2.1.3 has incompatible cornerstone.jar
Posted by Serge Knystautas <se...@lokitech.com>.
Geoffrey T. Falk wrote:
>>Asnwer #1: You don't. You use the binary distribution of Phoenix that is
>>packaged with James.
>
>
> Thanks, but I really want to build this stuff from source. That way I
> know there is not any voodoo magic going on :-) plus I can study the
> source. I will wait for the next version if I have to.
I can assure you there is voodoo magic going on. :) Anyone who could
identify what source James is using and help us or the Avalon folks tag
their CVS modules would be owed favors by many. The next release of
James and Avalon are many many months away at best.
> PS: Am I the only one bewildered by the Avalon documentation?
For people who know object-oriented design patterns, Avalon should be
extremely straight-forward and a nice implementation of that. But for
most of us slackers, it is incredibly challenging to get your head
around it.
For learning Avalon, I would start with their examples and build a
"hello world" style program and go from there.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com/
p. 1.301.656.5501
e. sergek@lokitech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
RE: James Articles Posted
Posted by Erik Beijnoff <er...@beijnoff.com>.
> >
> > Feature articles about James (by me ;-) published yesterday on IBM's
> > DeveloperWorks::
> >
> > Feature entry point (click on the email image):
> >
> > http://www-106.ibm.com/developerworks/
> >
> > Direct links to articles:
> >
> > http://www-106.ibm.com/developerworks/java/library/j-james1.html
> >
> > http://www-106.ibm.com/developerworks/java/library/j-james2.html
> >
> >
Great article! Thank you very much! Exactly what I needed.
/Erik Beijnoff
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
RE: James Articles Posted
Posted by Danny Angus <da...@apache.org>.
Excellent stuff Claude.
I've posted a news item on http://james.apache.org and on http://jakarta.apache.org
> -----Original Message-----
> From: Claude Duguay [mailto:claude.duguay@verizon.net]
> Sent: 11 June 2003 23:41
> To: James Users List
> Subject: James Articles Posted
>
>
> Feature articles about James (by me ;-) published yesterday on IBM's
> DeveloperWorks::
>
> Feature entry point (click on the email image):
>
> http://www-106.ibm.com/developerworks/
>
> Direct links to articles:
>
> http://www-106.ibm.com/developerworks/java/library/j-james1.html
>
> http://www-106.ibm.com/developerworks/java/library/j-james2.html
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-user-help@jakarta.apache.org
>
James Articles Posted
Posted by Claude Duguay <cl...@verizon.net>.
Feature articles about James (by me ;-) published yesterday on IBM's
DeveloperWorks::
Feature entry point (click on the email image):
http://www-106.ibm.com/developerworks/
Direct links to articles:
http://www-106.ibm.com/developerworks/java/library/j-james1.html
http://www-106.ibm.com/developerworks/java/library/j-james2.html
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
RE: James 2.1.3 has incompatible cornerstone.jar
Posted by "Geoffrey T. Falk" <gt...@cirp.org>.
On 11 Jun, Noel J. Bergman wrote:
>> What is the correct order of building Avalon, Excalibur and Phoenix
>> components in order to get James to work?
>
> Asnwer #1: You don't. You use the binary distribution of Phoenix that is
> packaged with James.
Thanks, but I really want to build this stuff from source. That way I
know there is not any voodoo magic going on :-) plus I can study the
source. I will wait for the next version if I have to.
PS: Am I the only one bewildered by the Avalon documentation?
Geoffrey
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
RE: James 2.1.3 has incompatible cornerstone.jar
Posted by "Noel J. Bergman" <no...@devtech.com>.
> There is an incompatible cornerstone.jar in the James lib directory
> distributed with 2.1.3.
It is compatible with the version of Phoenix used in James v2.x.
> Why do the latest distributions not work together?
There are various historical reasons (such as interfaces changing with no
notice, or even with a CVS tag), but you probably don't really want to know
them. You just want the code to work. :-) So do we.
Avalon is in the midst of a coordinated release process to resolve these
sorts of issues. They have only just gotten to looking at Cornerstone. You
should be aware that it is presently contemplated to deprecate or possibly
remove portions of Cornerstone. One of the things that I gave to them last
week was a list of all Cornerstone services used by James. Those have a
high priority. The Avalon Committers are very serious about supporting
James.
> What is the correct order of building Avalon, Excalibur and Phoenix
> components in order to get James to work?
Asnwer #1: You don't. You use the binary distribution of Phoenix that is
packaged with James.
Answer #2: You have to use the code in the James v3 branch (the main trunk),
which has been converted to the new Avalon interfaces. Stephen McConnell is
one of the Avalon Committers working with James, and has been pulling over
code as it has been readied by the Avalon project. There is a newer
Cornerstone, but it isn't a release candidate, yet. Stephen does have James
(v3 branch) working with the latest Avalon code (albiet the Merlin, not
Phoenix, container).
Fair warning: no one has audited the new Avalon code for memory leaks and
other long term stability issues; at least no one associated with James.
Once Avalon has completed their release cycle, we expect James v3 to work
with their code as released, and will certainly be doing stability tests.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: James 2.1.3 has incompatible cornerstone.jar
Posted by "Geoffrey T. Falk" <gt...@cirp.org>.
On 10 Jun, To: james-user@jakarta.apache.org wrote:
> I am having trouble trying to build and run James 2.1.3 with Phoenix
> 4.0.4.
FYI: James 2.2.0a4 has the same problem. Only now I get the error at
compile-time:
compile:
[echo] Compiling James Java sources
[mkdir] Created dir: /home/gtf/java-apps/James/build/classes
[javac] Compiling 206 source files to /home/gtf/java-apps/James/build/classes
[javac] /home/gtf/java-apps/James/src/java/org/apache/james/util/thread/DefaultThreadPool.java:73: org.apache.james.util.thread.DefaultThreadPool should be declared abstract; it does not define execute(org.apache.excalibur.thread.Executable) in org.apache.james.util.thread.DefaultThreadPool
[javac] public class DefaultThreadPool
[javac] ^
[javac] /home/gtf/java-apps/James/src/java/org/apache/james/util/thread/DefaultThreadPool.java:196: execute(org.apache.avalon.framework.activity.Executable) in org.apache.james.util.thread.DefaultThreadPool cannot implement execute(org.apache.avalon.framework.activity.Executable) in org.apache.avalon.excalibur.thread.ThreadPool; attempting to use incompatible return type
[javac] found : org.apache.avalon.excalibur.thread.ThreadControl
[javac] required: org.apache.excalibur.thread.ThreadControl
[javac] public ThreadControl execute( final Executable work )
[javac] ^
[javac] /home/gtf/java-apps/James/src/java/org/apache/james/util/thread/DefaultThreadPool.java:184: execute(java.lang.Runnable) in org.apache.james.util.thread.DefaultThreadPool cannot implement execute(java.lang.Runnable) in org.apache.excalibur.thread.ThreadPool; attempting to use incompatible return type
[javac] found : org.apache.avalon.excalibur.thread.ThreadControl
[javac] required: org.apache.excalibur.thread.ThreadControl
[javac] public ThreadControl execute( final Runnable work )
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 3 errors
BUILD FAILED
Thanks
Geoffrey
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org