| Summary: | CLI on Windows outputs everything twice | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jan Martiska <jmartisk> |
| Component: | CLI | Assignee: | Tomaz Cerar <tcerar> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | brian.stansberry, myarboro |
| Target Milestone: | ER7 | ||
| Target Release: | EAP 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-15 16:55:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Could you compare jboss-cli-logging.properties in the bin dir? The logging should be OFF by default. For example, the current config is loggers=org,org.jboss.as.cli logger.org.level=OFF logger.org.jboss.as.cli.level=OFF There is no difference in jboss-cli-logging.properties. The config is just as you said. Observed on Windows Server 2008 and Windows 7. This is fixed upstream; just needs to be backported. Verified on EAP 6.2.0.ER7. |
On Windows, for some reason, CLI outputs everything twice - once as a log and once as the 'normal' output -- It seems that INFO-level logs are by default sent to the console output. This started happening in EAP 6.2.0.ER1 (but I encountered it first with ER6) and wasn't observed on platforms other than Windows. Example from the command line: C:\eap6\ER2\bin>jboss-cli.bat --connect INFO [org.jboss.modules] JBoss Modules version 1.3.0.Beta4 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1 INFO [org.jboss.remoting] JBoss Remoting version 3.2.16.GA-redhat-1 [standalone@localhost:9999 /] /subsystem=weld:read-resource INFO [org.jboss.as.cli.CommandContext] { "outcome" => "success", "result" => {} } { "outcome" => "success", "result" => {} } It doesn't seem like a configuration issue, rather it is somewhere in the CLI module. When I tried overwriting the org.jboss.as.cli module in 6.2.0.ERx with the one from 6.1.1.GA, the issue disappeared.