[jira] [Updated] (WHIRR-365) Too verbose command line interface logging

["Andrei Savu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Savu updated WHIRR-365:
------------------------------

    Attachment: WHIRR-365.patch

It seems like the previous google groups thread is outdated - there are no root level loggers in sshj. In this patch I've changed log4j.xml for the CLI so that only error log messages will be displayed on the console. I've also changed in ComputeCache the log level from a message from info to debug (created new ComputeServiceContext ...)

> Too verbose command line interface logging
> ------------------------------------------
>
>                 Key: WHIRR-365
>                 URL: https://issues.apache.org/jira/browse/WHIRR-365
>             Project: Whirr
>          Issue Type: Bug
>          Components: cli
>    Affects Versions: 0.6.0
>            Reporter: Andrei Savu
>            Priority: Blocker
>             Fix For: 0.6.0
>
>         Attachments: WHIRR-365.patch
>
>
> When starting services using the command line interface I see a lot of messages like this:
> {noformat}
> Attaching `session` channel (#31)
> Initialized - < session channel: id=31, recipient=1, localWin=[winSize=2097152], remoteWin=[winSize=0] >
> Sending channel request for `pty-req`
> Will request to exec `./jclouds-script-1313376230348 tailerr`
> Sending channel request for `exec`
> Received window adjustment for 2097152 bytes
> Got chan request for `exit-status`
> Got EOF
> Got close
> Sending EOF
> Sending close
> Forgetting `session` channel (#31)
> {noformat}
> I guess they are generated by sshj.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira