You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Simon Laws <si...@googlemail.com> on 2011/01/27 15:14:45 UTC
Reduce default logging output in 2.x
I'd like to reduce the amount of log output we get by default by, for
example, changing the endpoint registration to be fine rather than
info. Anyone have any concerns about me doing that?
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Reduce default logging output in 2.x
Posted by Luciano Resende <lu...@gmail.com>.
On Thu, Jan 27, 2011 at 6:14 AM, Simon Laws <si...@googlemail.com> wrote:
> I'd like to reduce the amount of log output we get by default by, for
> example, changing the endpoint registration to be fine rather than
> info. Anyone have any concerns about me doing that?
>
> Simon
>
+1, But these are the second best set of info for debugging purposes
when a service is not starting properly, so we should make
documentation on how to enable them very easy to find in our
documentation.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Reduce default logging output in 2.x
Posted by ant elder <an...@apache.org>.
On Mon, Jan 31, 2011 at 4:26 PM, Simon Laws <si...@googlemail.com> wrote:
>>>
>>
>> Ok let me go do that. While doing that i'd also quite like to update
>> the message output by the endpoint registry addEndpoint to include the
>> binding type and binding URI and to not include the Endpoint hashcode,
>> say if anyone has concerns or updates on that.
>>
>> ...ant
>>
>
> Fine by me.
>
> As separate question though about how this is controlled. We have
> properties you can pass into a node now. Have we a list of what
> properties you can provide anywhere?
>
No list no. Its not used that much and at least some of what is used
at present i'd like to change.
For this one for now i'll add a constant to the RuntimeProperties interface.
...ant
Re: Reduce default logging output in 2.x
Posted by Simon Laws <si...@googlemail.com>.
>>
>
> Ok let me go do that. While doing that i'd also quite like to update
> the message output by the endpoint registry addEndpoint to include the
> binding type and binding URI and to not include the Endpoint hashcode,
> say if anyone has concerns or updates on that.
>
> ...ant
>
Fine by me.
As separate question though about how this is controlled. We have
properties you can pass into a node now. Have we a list of what
properties you can provide anywhere?
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Reduce default logging output in 2.x
Posted by ant elder <an...@gmail.com>.
On Mon, Jan 31, 2011 at 3:04 PM, Simon Laws <si...@googlemail.com> wrote:
> On Mon, Jan 31, 2011 at 12:25 PM, Simon Nash <na...@apache.org> wrote:
>> ant elder wrote:
>>>
>>> On Fri, Jan 28, 2011 at 10:55 AM, Simon Nash <na...@apache.org> wrote:
>>>>
>>>> Simon Laws wrote:
>>>>>
>>>>> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>>>>>>
>>>>>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> I'd like to reduce the amount of log output we get by default by, for
>>>>>>> example, changing the endpoint registration to be fine rather than
>>>>>>> info. Anyone have any concerns about me doing that?
>>>>>>>
>>>>>> A couple of months ago i changed the default logging used by the shell
>>>>>> in the binary distribution [1] to suppress all the info messages as
>>>>>> there's so much irrelevant noise but now its really hard to tell whats
>>>>>> going on - you start a composite and nothing happens, no messages
>>>>>> about nodes, or contributions or composites or components or endpoints
>>>>>> or anything, so recently i've been thinking about reverting that
>>>>>> change. What info messages do you think you would still leave coming
>>>>>> out by default? I know you can change the logging properties level to
>>>>>> something finer but then you get literally hundreds of messages which
>>>>>> isn't very helpful either.
>>>>>>
>>>>>> ...ant
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>>>>>
>>>>> What I had been thinking was that we reduce (inrcease?) the level log
>>>>> logging messages so that they don't come out by default. We then have
>>>>> at least two options for providing useful output to users;
>>>>>
>>>>> 1/ users can, either selectively or generally, specify logging levels
>>>>> to get output. We could document certain combinations that produce
>>>>> suitable output.
>>>>>
>>>>> 2/ provide pre-canned reports for use by embedders (like the shell or
>>>>> anybody else) that tell you what composites/components have been
>>>>> started what endpoints are registered etc. There are any number of
>>>>> such reports you can imagine. From an endpoint of view it could even
>>>>> be done incrementally, and if really required, remotely. We should
>>>>> have more info in the domain registry (i.e. the endpoint registry is
>>>>> just one part of it) so my last comment should ultimately be applied
>>>>> to any domain information.
>>>>>
>>>>> We have a very few examples of 2 already that could be re-purposed. For
>>>>> example
>>>>>
>>>>> - dumping built composites. See code at bottom of
>>>>>
>>>>>
>>>>> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>>>>>
>>>>> - dumping out WSDL interfaces. See code from 1.x
>>>>>
>>>>>
>>>>> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>>>>>
>>>>> Simon
>>>>>
>>>> I find the log messages useful, but I'm not the typical user :-)
>>>>
>>>
>>> If having info log messages isn't desirable in some circumstances how
>>> about adding a "quiet mode" to the runtime and have everywhere that
>>> does info logging use fine logging instead when quiet mode is set.
>>>
>>> ...ant
>>>
>>>
>> That sounds fine to me.
>>
>> Simon
>>
>>
>
> Good idea. Sounds like it would do what I want.
>
> Simon
>
Ok let me go do that. While doing that i'd also quite like to update
the message output by the endpoint registry addEndpoint to include the
binding type and binding URI and to not include the Endpoint hashcode,
say if anyone has concerns or updates on that.
...ant
Re: Reduce default logging output in 2.x
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Jan 31, 2011 at 12:25 PM, Simon Nash <na...@apache.org> wrote:
> ant elder wrote:
>>
>> On Fri, Jan 28, 2011 at 10:55 AM, Simon Nash <na...@apache.org> wrote:
>>>
>>> Simon Laws wrote:
>>>>
>>>> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>>>>>
>>>>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com>
>>>>> wrote:
>>>>>>
>>>>>> I'd like to reduce the amount of log output we get by default by, for
>>>>>> example, changing the endpoint registration to be fine rather than
>>>>>> info. Anyone have any concerns about me doing that?
>>>>>>
>>>>> A couple of months ago i changed the default logging used by the shell
>>>>> in the binary distribution [1] to suppress all the info messages as
>>>>> there's so much irrelevant noise but now its really hard to tell whats
>>>>> going on - you start a composite and nothing happens, no messages
>>>>> about nodes, or contributions or composites or components or endpoints
>>>>> or anything, so recently i've been thinking about reverting that
>>>>> change. What info messages do you think you would still leave coming
>>>>> out by default? I know you can change the logging properties level to
>>>>> something finer but then you get literally hundreds of messages which
>>>>> isn't very helpful either.
>>>>>
>>>>> ...ant
>>>>>
>>>>> [1]
>>>>>
>>>>> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>>>>
>>>> What I had been thinking was that we reduce (inrcease?) the level log
>>>> logging messages so that they don't come out by default. We then have
>>>> at least two options for providing useful output to users;
>>>>
>>>> 1/ users can, either selectively or generally, specify logging levels
>>>> to get output. We could document certain combinations that produce
>>>> suitable output.
>>>>
>>>> 2/ provide pre-canned reports for use by embedders (like the shell or
>>>> anybody else) that tell you what composites/components have been
>>>> started what endpoints are registered etc. There are any number of
>>>> such reports you can imagine. From an endpoint of view it could even
>>>> be done incrementally, and if really required, remotely. We should
>>>> have more info in the domain registry (i.e. the endpoint registry is
>>>> just one part of it) so my last comment should ultimately be applied
>>>> to any domain information.
>>>>
>>>> We have a very few examples of 2 already that could be re-purposed. For
>>>> example
>>>>
>>>> - dumping built composites. See code at bottom of
>>>>
>>>>
>>>> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>>>>
>>>> - dumping out WSDL interfaces. See code from 1.x
>>>>
>>>>
>>>> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>>>>
>>>> Simon
>>>>
>>> I find the log messages useful, but I'm not the typical user :-)
>>>
>>
>> If having info log messages isn't desirable in some circumstances how
>> about adding a "quiet mode" to the runtime and have everywhere that
>> does info logging use fine logging instead when quiet mode is set.
>>
>> ...ant
>>
>>
> That sounds fine to me.
>
> Simon
>
>
Good idea. Sounds like it would do what I want.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Reduce default logging output in 2.x
Posted by Simon Nash <na...@apache.org>.
ant elder wrote:
> On Fri, Jan 28, 2011 at 10:55 AM, Simon Nash <na...@apache.org> wrote:
>> Simon Laws wrote:
>>> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>>>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com>
>>>> wrote:
>>>>> I'd like to reduce the amount of log output we get by default by, for
>>>>> example, changing the endpoint registration to be fine rather than
>>>>> info. Anyone have any concerns about me doing that?
>>>>>
>>>> A couple of months ago i changed the default logging used by the shell
>>>> in the binary distribution [1] to suppress all the info messages as
>>>> there's so much irrelevant noise but now its really hard to tell whats
>>>> going on - you start a composite and nothing happens, no messages
>>>> about nodes, or contributions or composites or components or endpoints
>>>> or anything, so recently i've been thinking about reverting that
>>>> change. What info messages do you think you would still leave coming
>>>> out by default? I know you can change the logging properties level to
>>>> something finer but then you get literally hundreds of messages which
>>>> isn't very helpful either.
>>>>
>>>> ...ant
>>>>
>>>> [1]
>>>> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>>>
>>> What I had been thinking was that we reduce (inrcease?) the level log
>>> logging messages so that they don't come out by default. We then have
>>> at least two options for providing useful output to users;
>>>
>>> 1/ users can, either selectively or generally, specify logging levels
>>> to get output. We could document certain combinations that produce
>>> suitable output.
>>>
>>> 2/ provide pre-canned reports for use by embedders (like the shell or
>>> anybody else) that tell you what composites/components have been
>>> started what endpoints are registered etc. There are any number of
>>> such reports you can imagine. From an endpoint of view it could even
>>> be done incrementally, and if really required, remotely. We should
>>> have more info in the domain registry (i.e. the endpoint registry is
>>> just one part of it) so my last comment should ultimately be applied
>>> to any domain information.
>>>
>>> We have a very few examples of 2 already that could be re-purposed. For
>>> example
>>>
>>> - dumping built composites. See code at bottom of
>>>
>>> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>>>
>>> - dumping out WSDL interfaces. See code from 1.x
>>>
>>> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>>>
>>> Simon
>>>
>> I find the log messages useful, but I'm not the typical user :-)
>>
>
> If having info log messages isn't desirable in some circumstances how
> about adding a "quiet mode" to the runtime and have everywhere that
> does info logging use fine logging instead when quiet mode is set.
>
> ...ant
>
>
That sounds fine to me.
Simon
Re: Reduce default logging output in 2.x
Posted by ant elder <an...@gmail.com>.
On Fri, Jan 28, 2011 at 10:55 AM, Simon Nash <na...@apache.org> wrote:
> Simon Laws wrote:
>>
>> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>>>
>>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com>
>>> wrote:
>>>>
>>>> I'd like to reduce the amount of log output we get by default by, for
>>>> example, changing the endpoint registration to be fine rather than
>>>> info. Anyone have any concerns about me doing that?
>>>>
>>> A couple of months ago i changed the default logging used by the shell
>>> in the binary distribution [1] to suppress all the info messages as
>>> there's so much irrelevant noise but now its really hard to tell whats
>>> going on - you start a composite and nothing happens, no messages
>>> about nodes, or contributions or composites or components or endpoints
>>> or anything, so recently i've been thinking about reverting that
>>> change. What info messages do you think you would still leave coming
>>> out by default? I know you can change the logging properties level to
>>> something finer but then you get literally hundreds of messages which
>>> isn't very helpful either.
>>>
>>> ...ant
>>>
>>> [1]
>>> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>>
>>
>> What I had been thinking was that we reduce (inrcease?) the level log
>> logging messages so that they don't come out by default. We then have
>> at least two options for providing useful output to users;
>>
>> 1/ users can, either selectively or generally, specify logging levels
>> to get output. We could document certain combinations that produce
>> suitable output.
>>
>> 2/ provide pre-canned reports for use by embedders (like the shell or
>> anybody else) that tell you what composites/components have been
>> started what endpoints are registered etc. There are any number of
>> such reports you can imagine. From an endpoint of view it could even
>> be done incrementally, and if really required, remotely. We should
>> have more info in the domain registry (i.e. the endpoint registry is
>> just one part of it) so my last comment should ultimately be applied
>> to any domain information.
>>
>> We have a very few examples of 2 already that could be re-purposed. For
>> example
>>
>> - dumping built composites. See code at bottom of
>>
>> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>>
>> - dumping out WSDL interfaces. See code from 1.x
>>
>> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>>
>> Simon
>>
> I find the log messages useful, but I'm not the typical user :-)
>
If having info log messages isn't desirable in some circumstances how
about adding a "quiet mode" to the runtime and have everywhere that
does info logging use fine logging instead when quiet mode is set.
...ant
Re: Reduce default logging output in 2.x
Posted by Simon Nash <na...@apache.org>.
Simon Laws wrote:
> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com> wrote:
>>> I'd like to reduce the amount of log output we get by default by, for
>>> example, changing the endpoint registration to be fine rather than
>>> info. Anyone have any concerns about me doing that?
>>>
>> A couple of months ago i changed the default logging used by the shell
>> in the binary distribution [1] to suppress all the info messages as
>> there's so much irrelevant noise but now its really hard to tell whats
>> going on - you start a composite and nothing happens, no messages
>> about nodes, or contributions or composites or components or endpoints
>> or anything, so recently i've been thinking about reverting that
>> change. What info messages do you think you would still leave coming
>> out by default? I know you can change the logging properties level to
>> something finer but then you get literally hundreds of messages which
>> isn't very helpful either.
>>
>> ...ant
>>
>> [1] http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>
>
> What I had been thinking was that we reduce (inrcease?) the level log
> logging messages so that they don't come out by default. We then have
> at least two options for providing useful output to users;
>
> 1/ users can, either selectively or generally, specify logging levels
> to get output. We could document certain combinations that produce
> suitable output.
>
> 2/ provide pre-canned reports for use by embedders (like the shell or
> anybody else) that tell you what composites/components have been
> started what endpoints are registered etc. There are any number of
> such reports you can imagine. From an endpoint of view it could even
> be done incrementally, and if really required, remotely. We should
> have more info in the domain registry (i.e. the endpoint registry is
> just one part of it) so my last comment should ultimately be applied
> to any domain information.
>
> We have a very few examples of 2 already that could be re-purposed. For example
>
> - dumping built composites. See code at bottom of
> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>
> - dumping out WSDL interfaces. See code from 1.x
> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>
> Simon
>
I find the log messages useful, but I'm not the typical user :-)
I think it would be good to get some user input on this, so I'm
copying this discussion to the user list.
Simon
Re: Reduce default logging output in 2.x
Posted by Simon Nash <na...@apache.org>.
Simon Laws wrote:
> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com> wrote:
>>> I'd like to reduce the amount of log output we get by default by, for
>>> example, changing the endpoint registration to be fine rather than
>>> info. Anyone have any concerns about me doing that?
>>>
>> A couple of months ago i changed the default logging used by the shell
>> in the binary distribution [1] to suppress all the info messages as
>> there's so much irrelevant noise but now its really hard to tell whats
>> going on - you start a composite and nothing happens, no messages
>> about nodes, or contributions or composites or components or endpoints
>> or anything, so recently i've been thinking about reverting that
>> change. What info messages do you think you would still leave coming
>> out by default? I know you can change the logging properties level to
>> something finer but then you get literally hundreds of messages which
>> isn't very helpful either.
>>
>> ...ant
>>
>> [1] http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>
>
> What I had been thinking was that we reduce (inrcease?) the level log
> logging messages so that they don't come out by default. We then have
> at least two options for providing useful output to users;
>
> 1/ users can, either selectively or generally, specify logging levels
> to get output. We could document certain combinations that produce
> suitable output.
>
> 2/ provide pre-canned reports for use by embedders (like the shell or
> anybody else) that tell you what composites/components have been
> started what endpoints are registered etc. There are any number of
> such reports you can imagine. From an endpoint of view it could even
> be done incrementally, and if really required, remotely. We should
> have more info in the domain registry (i.e. the endpoint registry is
> just one part of it) so my last comment should ultimately be applied
> to any domain information.
>
> We have a very few examples of 2 already that could be re-purposed. For example
>
> - dumping built composites. See code at bottom of
> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>
> - dumping out WSDL interfaces. See code from 1.x
> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>
> Simon
>
I find the log messages useful, but I'm not the typical user :-)
I think it would be good to get some user input on this, so I'm
copying this discussion to the user list.
Simon
Re: Reduce default logging output in 2.x
Posted by ant elder <an...@apache.org>.
On Fri, Jan 28, 2011 at 9:48 AM, Simon Laws <si...@googlemail.com> wrote:
> On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
>> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com> wrote:
>>> I'd like to reduce the amount of log output we get by default by, for
>>> example, changing the endpoint registration to be fine rather than
>>> info. Anyone have any concerns about me doing that?
>>>
>>
>> A couple of months ago i changed the default logging used by the shell
>> in the binary distribution [1] to suppress all the info messages as
>> there's so much irrelevant noise but now its really hard to tell whats
>> going on - you start a composite and nothing happens, no messages
>> about nodes, or contributions or composites or components or endpoints
>> or anything, so recently i've been thinking about reverting that
>> change. What info messages do you think you would still leave coming
>> out by default? I know you can change the logging properties level to
>> something finer but then you get literally hundreds of messages which
>> isn't very helpful either.
>>
>> ...ant
>>
>> [1] http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>>
>
> What I had been thinking was that we reduce (inrcease?) the level log
> logging messages so that they don't come out by default. We then have
> at least two options for providing useful output to users;
>
> 1/ users can, either selectively or generally, specify logging levels
> to get output. We could document certain combinations that produce
> suitable output.
>
> 2/ provide pre-canned reports for use by embedders (like the shell or
> anybody else) that tell you what composites/components have been
> started what endpoints are registered etc. There are any number of
> such reports you can imagine. From an endpoint of view it could even
> be done incrementally, and if really required, remotely. We should
> have more info in the domain registry (i.e. the endpoint registry is
> just one part of it) so my last comment should ultimately be applied
> to any domain information.
>
> We have a very few examples of 2 already that could be re-purposed. For example
>
> - dumping built composites. See code at bottom of
> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
>
> - dumping out WSDL interfaces. See code from 1.x
> http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
>
The problem with changing these current INFO messages to be FINE is
that Tuscany code has been using FINE as debug type messages so the
info ones will disappear amongst the flood of other output.
I think "something" needs to come out by default when something is
started. Thats standard practice for pretty much every appserver or
container type thing i've used eg tomcat, websphere, spring, etc, and
you just have to go back in time to when the initial
system.out.println was added to the Tuscany
ServletHost.addServletMapping to see how useful we found that. Would
it be a problem to keep info messages for composite start/stop and
endpoint add/remove?
...ant
Re: Reduce default logging output in 2.x
Posted by Simon Laws <si...@googlemail.com>.
On Thu, Jan 27, 2011 at 10:03 PM, ant elder <an...@gmail.com> wrote:
> On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com> wrote:
>> I'd like to reduce the amount of log output we get by default by, for
>> example, changing the endpoint registration to be fine rather than
>> info. Anyone have any concerns about me doing that?
>>
>
> A couple of months ago i changed the default logging used by the shell
> in the binary distribution [1] to suppress all the info messages as
> there's so much irrelevant noise but now its really hard to tell whats
> going on - you start a composite and nothing happens, no messages
> about nodes, or contributions or composites or components or endpoints
> or anything, so recently i've been thinking about reverting that
> change. What info messages do you think you would still leave coming
> out by default? I know you can change the logging properties level to
> something finer but then you get literally hundreds of messages which
> isn't very helpful either.
>
> ...ant
>
> [1] http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849
>
What I had been thinking was that we reduce (inrcease?) the level log
logging messages so that they don't come out by default. We then have
at least two options for providing useful output to users;
1/ users can, either selectively or generally, specify logging levels
to get output. We could document certain combinations that produce
suitable output.
2/ provide pre-canned reports for use by embedders (like the shell or
anybody else) that tell you what composites/components have been
started what endpoints are registered etc. There are any number of
such reports you can imagine. From an endpoint of view it could even
be done incrementally, and if really required, remotely. We should
have more info in the domain registry (i.e. the endpoint registry is
just one part of it) so my last comment should ultimately be applied
to any domain information.
We have a very few examples of 2 already that could be re-purposed. For example
- dumping built composites. See code at bottom of
http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
- dumping out WSDL interfaces. See code from 1.x
http://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/tools/contrib2wsdl/src/main/java/org/apache/tuscany/tools/contrib2wsdl/Contrib2WSDL.java
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: Reduce default logging output in 2.x
Posted by ant elder <an...@gmail.com>.
On Thu, Jan 27, 2011 at 2:14 PM, Simon Laws <si...@googlemail.com> wrote:
> I'd like to reduce the amount of log output we get by default by, for
> example, changing the endpoint registration to be fine rather than
> info. Anyone have any concerns about me doing that?
>
A couple of months ago i changed the default logging used by the shell
in the binary distribution [1] to suppress all the info messages as
there's so much irrelevant noise but now its really hard to tell whats
going on - you start a composite and nothing happens, no messages
about nodes, or contributions or composites or components or endpoints
or anything, so recently i've been thinking about reverting that
change. What info messages do you think you would still leave coming
out by default? I know you can change the logging properties level to
something finer but then you get literally hundreds of messages which
isn't very helpful either.
...ant
[1] http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/launcher/logging.properties?r1=1037517&r2=1039849