You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Stephen McConnell <mc...@apache.org> on 2003/02/08 08:18:48 UTC

[PHOENIX] excalibur-thread issue

Hi all:

James has recently beeen updated to use the cornerstone packages.  The 
cornerstone-threads-1.0 package incorporates the new constructor in 
excalibur-threads-1.1 that allows passing of the max thread parameter 
when creating a thread pool. This introduces a dependency between the 
cornerstone threads jar file and excalibur-threads-1.1.  Unfortunately 
there is a conflict when running under Phoenix in that the Phoenix 
version of excalibur-threads is 1.0 which is not compatible.  I have 
includes the excalibur-threads-1.1 in the James sar lib - however, it 
appears that the Phoenix version of the jar is taking priority (which 
kind of suprised me).

I've included the Phoenix stack-dump below:

Any suggestions?

Cheers, Steve.


Phoenix 4.1alpha

org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: 
Component named "thread-manager" failed to pass through the Configurati
on stage. (Reason: java.lang.NoSuchMethodError: 
org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.<init>(Ljava/lang/String;IILorg/ap
ache/excalibur/threadcontext/ThreadContext;)V).
        at 
org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:283)
        at 
org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:156)
        at 
org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:498)
        at 
org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:446)
        at 
org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:377)
        at 
org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:148)
        at 
org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:298)
        at 
org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(DefaultKernel.java:190)
        at 
org.apache.avalon.phoenix.components.kernel.DefaultKernel.addApplication(DefaultKernel.java:271)
        at 
org.apache.avalon.phoenix.components.deployer.DefaultDeployer.deploy(DefaultDeployer.java:290)
        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:225)
        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:88)
        at org.apache.avalon.phoenix.launcher.Main.main(Main.java:40)
Caused by: java.lang.NoSuchMethodError: 
org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.<init>(Ljava/lang/String;IILorg/apache/exc
alibur/threadcontext/ThreadContext;)V
        at 
org.apache.avalon.cornerstone.blocks.threads.DefaultThreadManager.configureThreadPool(DefaultThreadManager.java:73)
        at 
org.apache.avalon.cornerstone.blocks.threads.DefaultThreadManager.configure(DefaultThreadManager.java:54)
        at 
org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:239)
        at 
org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:123)
        ... 22 more
There was an uncaught exception:


-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net



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


Re: [PHOENIX] excalibur-thread issue

Posted by Paul Hammant <Pa...@yahoo.com>.
> I've upgraded (and fixed) an number of jar dependancies, but only in 
> HEAD.  The 402 branch depends on the now-missing excalibur-containerkit.


Actually, the upgraded SARs work just fine in the 402 branch after 
excalibur-thread.jar is upgraded.  

Regards,

- Paul












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


Re: [PHOENIX] excalibur-thread issue

Posted by Paul Hammant <Pa...@yahoo.com>.
Stephen,

The lib jars are not hidden from the hosted client applications for 
Phoenix.  Only Kernel impl is hidden.  Of course apps are hidden from 
each other.

I've upgraded (and fixed) an number of jar dependancies, but only in 
HEAD.  The 402 branch depends on the now-missing excalibur-containerkit. 
 I'll do some work to upgrade that to use the new location for container 
kit.

Regards,

- Paul

> James has recently beeen updated to use the cornerstone packages.  The 
> cornerstone-threads-1.0 package incorporates the new constructor in 
> excalibur-threads-1.1 that allows passing of the max thread parameter 
> when creating a thread pool. This introduces a dependency between the 
> cornerstone threads jar file and excalibur-threads-1.1.  Unfortunately 
> there is a conflict when running under Phoenix in that the Phoenix 
> version of excalibur-threads is 1.0 which is not compatible.  I have 
> includes the excalibur-threads-1.1 in the James sar lib - however, it 
> appears that the Phoenix version of the jar is taking priority (which 
> kind of suprised me).
>
> I've included the Phoenix stack-dump below:
>
> Any suggestions?
>
> Cheers, Steve.
>
>
> Phoenix 4.1alpha
>
> org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleException: 
> Component named "thread-manager" failed to pass through the Configurati
> on stage. (Reason: java.lang.NoSuchMethodError: 
> org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.<init>(Ljava/lang/String;IILorg/ap 
>
> ache/excalibur/threadcontext/ThreadContext;)V).
>        at 
> org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.fail(LifecycleHelper.java:283) 
>
>        at 
> org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:156) 
>
>        at 
> org.apache.avalon.phoenix.components.application.DefaultApplication.startup(DefaultApplication.java:498) 
>
>        at 
> org.apache.avalon.phoenix.components.application.DefaultApplication.doRunPhase(DefaultApplication.java:446) 
>
>        at 
> org.apache.avalon.phoenix.components.application.DefaultApplication.runPhase(DefaultApplication.java:377) 
>
>        at 
> org.apache.avalon.phoenix.components.application.DefaultApplication.start(DefaultApplication.java:148) 
>
>        at 
> org.apache.avalon.framework.container.ContainerUtil.start(ContainerUtil.java:298) 
>
>        at 
> org.apache.avalon.phoenix.components.kernel.DefaultKernel.startup(DefaultKernel.java:190) 
>
>        at 
> org.apache.avalon.phoenix.components.kernel.DefaultKernel.addApplication(DefaultKernel.java:271) 
>
>        at 
> org.apache.avalon.phoenix.components.deployer.DefaultDeployer.deploy(DefaultDeployer.java:290) 
>
>        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:225) 
>
>        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:88)
>        at org.apache.avalon.phoenix.launcher.Main.main(Main.java:40)
> Caused by: java.lang.NoSuchMethodError: 
> org.apache.avalon.excalibur.thread.impl.DefaultThreadPool.<init>(Ljava/lang/String;IILorg/apache/exc 
>
> alibur/threadcontext/ThreadContext;)V
>        at 
> org.apache.avalon.cornerstone.blocks.threads.DefaultThreadManager.configureThreadPool(DefaultThreadManager.java:73) 
>
>        at 
> org.apache.avalon.cornerstone.blocks.threads.DefaultThreadManager.configure(DefaultThreadManager.java:54) 
>
>        at 
> org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:239) 
>
>        at 
> org.apache.avalon.phoenix.containerkit.lifecycle.LifecycleHelper.startup(LifecycleHelper.java:123) 
>
>        ... 22 more
> There was an uncaught exception:
>
>



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