You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leif Mortenson <le...@tanukisoftware.com> on 2003/03/12 13:11:20 UTC
Fortress debug output and default stack traces.
I have been trying to get back into Fortress by using it on a new
project. The current version is kicking out a lot of stack traces
at the debug level of the "fortress" log channel. I have included
them below. None of these are actual problems, so I was wondering
if there is a reason why they are being displayed.
The obvious fix is to disable log output, presto problem goes away.
But the problem there is that all of the components are assigned
loggers which are child loggers of the "fortress" logger. If I want
to have debug output enabled for them, but disabled for fortress,
then I have to configure them each individually in the xlog config
file.
In general showing stack traces for things other than an actually
problem seems like a good thing to avoid. When I first saw them, I
assumed that something was broken.
Cheers,
Leif
DEBUG 2003-03-12 20:15:13.589 [fortress ] (): Could not copy context entry: org.apache.avalon.fortress.RoleManager. Ignoring exception.
org.apache.avalon.framework.context.ContextException: Unable to resolve context key: org.apache.avalon.fortress.RoleManager
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:157)
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:160)
at org.apache.avalon.fortress.util.ContextManager.initializeRoleManager(ContextManager.java:541)
at org.apache.avalon.fortress.util.ContextManager.initialize(ContextManager.java:233)
at org.apache.avalon.fortress.impl.DefaultContainerManager.getInitializedContextManager(DefaultContainerManager.java:123)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:108)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:102)
at com.q_tec.backbone.server.BackboneServer.<init>(BackboneServer.java:152)
at com.q_tec.backbone.server.BackboneServer.main(BackboneServer.java:253)
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.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:102)
at java.lang.Thread.run(Thread.java:536)
DEBUG 2003-03-12 20:15:13.599 [fortress ] (): There is no Configuration already loaded
org.apache.avalon.framework.context.ContextException: Unable to resolve context key: impl.roleManager.config
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:157)
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:160)
at org.apache.avalon.fortress.util.ContextManager.getConfiguration(ContextManager.java:638)
at org.apache.avalon.fortress.util.ContextManager.initializeRoleManager(ContextManager.java:550)
at org.apache.avalon.fortress.util.ContextManager.initialize(ContextManager.java:233)
at org.apache.avalon.fortress.impl.DefaultContainerManager.getInitializedContextManager(DefaultContainerManager.java:123)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:108)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:102)
at com.q_tec.backbone.server.BackboneServer.<init>(BackboneServer.java:152)
at com.q_tec.backbone.server.BackboneServer.main(BackboneServer.java:253)
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.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:102)
at java.lang.Thread.run(Thread.java:536)
DEBUG 2003-03-12 20:15:13.830 [fortress ] (): Could not copy the parameters for the Context, ignoring the exception.
org.apache.avalon.framework.context.ContextException: Unable to resolve context key: impl.parameters
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:157)
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:160)
at org.apache.avalon.fortress.util.ContextManager.copyEntry(ContextManager.java:311)
at org.apache.avalon.fortress.util.ContextManager.initializeContext(ContextManager.java:295)
at org.apache.avalon.fortress.util.ContextManager.initialize(ContextManager.java:237)
at org.apache.avalon.fortress.impl.DefaultContainerManager.getInitializedContextManager(DefaultContainerManager.java:123)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:108)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:102)
at com.q_tec.backbone.server.BackboneServer.<init>(BackboneServer.java:152)
at com.q_tec.backbone.server.BackboneServer.main(BackboneServer.java:253)
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.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:102)
at java.lang.Thread.run(Thread.java:536)
DEBUG 2003-03-12 20:15:13.830 [fortress ] (): There is no Configuration already loaded
org.apache.avalon.framework.context.ContextException: Unable to resolve context key: impl.instrumentManager.config
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:157)
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:160)
at org.apache.avalon.fortress.util.ContextManager.getConfiguration(ContextManager.java:638)
at org.apache.avalon.fortress.util.ContextManager.initializeInstrumentManager(ContextManager.java:841)
at org.apache.avalon.fortress.util.ContextManager.initialize(ContextManager.java:238)
at org.apache.avalon.fortress.impl.DefaultContainerManager.getInitializedContextManager(DefaultContainerManager.java:123)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:108)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:102)
at com.q_tec.backbone.server.BackboneServer.<init>(BackboneServer.java:152)
at com.q_tec.backbone.server.BackboneServer.main(BackboneServer.java:253)
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.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:102)
at java.lang.Thread.run(Thread.java:536)
DEBUG 2003-03-12 20:15:14.080 [fortress ] (): There is no Configuration already loaded
org.apache.avalon.framework.context.ContextException: Unable to resolve context key: impl.configuration
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:157)
at org.apache.avalon.framework.context.DefaultContext.get(DefaultContext.java:160)
at org.apache.avalon.fortress.util.ContextManager.getConfiguration(ContextManager.java:638)
at org.apache.avalon.fortress.util.ContextManager.initializeConfiguration(ContextManager.java:258)
at org.apache.avalon.fortress.util.ContextManager.initialize(ContextManager.java:239)
at org.apache.avalon.fortress.impl.DefaultContainerManager.getInitializedContextManager(DefaultContainerManager.java:123)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:108)
at org.apache.avalon.fortress.impl.DefaultContainerManager.<init>(DefaultContainerManager.java:102)
at com.q_tec.backbone.server.BackboneServer.<init>(BackboneServer.java:152)
at com.q_tec.backbone.server.BackboneServer.main(BackboneServer.java:253)
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.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:102)
at java.lang.Thread.run(Thread.java:536)
DEBUG 2003-03-12 20:15:14.240 [fortress ] (): No Container.LIFECYCLE_EXTENSION_MANAGER is given, installing default lifecycle extension manager with 0 extensions
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress debug output and default stack traces.
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Berin Loritsch wrote:
>That was a result of a change I made to ContextManager when I was
>tracking down an initialization bug--there was an NPE thrown
>somewhere. We can disable the logging for those particular points
>without problems.
>
Ok, I reworked the messages so they no longer display stack traces.
Cheers,
Leif
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Fortress debug output and default stack traces.
Posted by Berin Loritsch <bl...@apache.org>.
Leif Mortenson wrote:
> I have been trying to get back into Fortress by using it on a new
> project. The current version is kicking out a lot of stack traces
> at the debug level of the "fortress" log channel. I have included
> them below. None of these are actual problems, so I was wondering
> if there is a reason why they are being displayed.
>
> The obvious fix is to disable log output, presto problem goes away.
> But the problem there is that all of the components are assigned
> loggers which are child loggers of the "fortress" logger. If I want
> to have debug output enabled for them, but disabled for fortress,
> then I have to configure them each individually in the xlog config
> file.
>
> In general showing stack traces for things other than an actually
> problem seems like a good thing to avoid. When I first saw them, I
> assumed that something was broken.
That was a result of a change I made to ContextManager when I was
tracking down an initialization bug--there was an NPE thrown
somewhere. We can disable the logging for those particular points
without problems.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org