[
https://issues.apache.org/jira/browse/WHIRR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Savu reopened WHIRR-365:
-------------------------------
I'm reopening this because it seems like the patch only works for the
development build but I still see a long list of log messages on the binary
release.
My guess is this is a classpath ordering issue generated by the fact that we
have many log4j.xml files in the project. Should I update them all or are am I
doing something wrong?
> 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
> Assignee: 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
