Hi Senaka,
+1 for the idea. I also feel that server start-up logs
get lengthier increasingly, So if we do not log some messages or redundant
messages, IMO, the strtup process will look as if its hanging at some
places, since anyway the activities are happening. So maybe we need to
change the way the messages are shown. for an example now, we see
[2012-02-04 17:36:01,415] INFO - DeploymentInterceptor Deploying Axis2
service: XKMS {super-tenant}
[2012-02-04 17:36:02,274] INFO - DeploymentEngine Deploying Web service:
org.wso2.carbon.xkms -
which should be replaced with some common message, so a user may know whats
happening.
Regards,
/Nuwan
On Sat, Feb 4, 2012 at 5:45 PM, Senaka Fernando <[email protected]> wrote:
> Hi all,
>
> I think we can focus on further reducing logs at start-up. For example,
> I'm getting these logs when starting the ESB 4.0.3. I'm just taking this as
> an example, but the same applies to other products as well.
>
> [2012-02-04 17:35:43,674] INFO - InputOutputAdaptersComponent There is no
> adapters-component.conf.. Using the default configuration
>
> A better way to log this would be to log nothing when the
> adapters-component.conf is not present but log something when the file is
> present, that way in the default setup (where the file is not available),
> there won't be any logs written. Might not be the best example, but for
> instance this one:
>
> [2012-02-04 17:35:50,551] INFO - ClusterBuilder Clustering has been
> disabled
>
> is not necessary. What's better is to log something like below when
> clustering is enabled (so that people would understand what they turned on
> is working) but log nothing when it is disabled (which is the default).
>
> [2012-02-04 17:35:50,551] INFO - ClusterBuilder Clustering is enabled
>
> The same applies to deploying services where we can make these two logs
> into one. For some services you actually see one log, but for some you see
> two. But, just one log saying it was successful would do, unless it failed
> and you print several logs.
>
> [2012-02-04 17:36:01,415] INFO - DeploymentInterceptor Deploying Axis2
> service: XKMS {super-tenant}
> [2012-02-04 17:36:02,274] INFO - DeploymentEngine Deploying Web service:
> org.wso2.carbon.xkms -
>
> These redundant logs can of course be DEBUG logs, but the idea is that you
> see a minimum @ INFO level by default, making it much easier for someone to
> understand what's going on. WDYT?
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
--
*Thanks & Regards,
Nuwan Bandara
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
http://nuwan.bandara.co
*
<http://www.nuwanbando.com/>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
