Mike,

I had never noticed this, but in my Cocoon deploy I have it too. ServiceMetaManger is the one that goes through looking for servcies.list in all the JARs. None of the JARs in WEB-INF/keel/server/lib have the StoreJanitor listed. On a hunch, since Cocoon uses Avalon as well, I went looking in WEB-INF/lib, and sure enough, there is excalibur-store-20030706.jar in there which does list StoreJanitor.

Looks like this is a classloader issue. Obviously, KeelURLClassloader is preventing classes from the Cocoon JARs from "leaking" into keel-server since ServiceMetaManager can't load the class, which is good. But, ServiceMetaManager is somehow seeing resources from the webapp JARs.

Shash

PS: I have to leave now, or else I would have tried the Struts deploy with full debug, or the openjms-cocoon debug, I bet neither would show this error.

Michael Nash JGlobal.com wrote:

Shash:

In followup to the below issue, I do see one strange thing in the log for the role manager (if you turn everything up to "debug"):

DEBUG   2003-10-05 16:08:26.026   [system.meta] 
(/org.apache.avalon.fortress.impl.role.ServiceMetaManager.initialize(ServiceMetaManager.java:182)):
 Specified service 'org.apache.excalibur.store.StoreJanitor' is not available
java.lang.ClassNotFoundException: org.apache.excalibur.store.StoreJanitor              
                                             at 
java.net.URLClassLoader$1.run(URLClassLoader.java:199)
       at java.security.AccessController.doPrivileged(Native Method)                   
                                            at 
java.net.URLClassLoader.findClass(URLClassLoader.java:187)
       at 
org.keel.core.classloader.KeelURLClassLoader.loadClass(KeelURLClassLoader.java:102)    
                                  at 
java.lang.ClassLoader.loadClass(ClassLoader.java:235)
       at 
org.apache.avalon.fortress.impl.role.ServiceMetaManager.setupImplementations(ServiceMetaManager.java:198)
                at 
org.apache.avalon.fortress.impl.role.ServiceMetaManager.initialize(ServiceMetaManager.java:178)
       at 
org.apache.avalon.fortress.util.ContextManager.initializeMetaInfoManager(ContextManager.java:643)
                        at 
org.apache.avalon.fortress.util.ContextManager.initialize(ContextManager.java:270)
       at 
org.apache.avalon.fortress.impl.DefaultContainerManager.getInitializedContextManager(DefaultContainerManager.java:121)
       at 
org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:106)
                         at 
org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:100)
       at 
org.keel.core.container.KeelContainerBuilder.getContainer(KeelContainerBuilder.java:173)
                                 at 
org.keel.servers.KeelAbstractServer.initialize(KeelAbstractServer.java:111)
       at org.keel.servers.KeelAbstractServer.getContainer(KeelAbstractServer.java:99) 
                                            at 
org.keel.servers.direct.KeelDirectServer.run(KeelDirectServer.java:60)

As far as I can see, we really don't have that class - but why is the meta information/role definition there? Not sure if it's related, but thought I'd better throw it out there in case it makes more sense to you!

Mike

On Sat, 4 Oct 2003 21:44:07 -0400
"Michael Nash JGlobal.com" <[EMAIL PROTECTED]> wrote:



Steve:

You've run into an intermittent issue that both Shash and I have been fighting with for a couple of days now. All I can suggest at the moment is an "ant -Ddeploy.name=yourdeplooy clean" and a new assemble-deploy. We're not entirely sure what is causing it, but we're chasing it down!

Mike

On Sat, 04 Oct 2003 20:14:13 -0500
Stephen Davidson <[EMAIL PROTECTED]> wrote:



Greetings.

At some point, I did a full rebuild sometime after I updated various projects. So I don't know when the update that killed me was downloaded. But now I am getting the attached error on startup.

What package has been added to the minimal list? Or have I done something strange again?

Thanks,
Steve

Startup failure:

Caused by: org.apache.avalon.framework.configuration.ConfigurationException: No class found matching configuration name [name: sequence, location: file:/home/steve/projects/Blueline/keel-build/deploy/jakarta-tomcat-4.1.27/webapps/struts/WEB-INF/keel/server/conf/app-navigate/system.xconf:29:55]

--
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741


http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com


Michael Nash

JGlobal Ltd.
http://www.jglobal.com

Bahamas Commerce and Trade
http://www.bahamascommerce.com

http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com




Michael Nash

JGlobal Ltd.
http://www.jglobal.com

Bahamas Commerce and Trade
http://www.bahamascommerce.com

http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com




http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

Reply via email to