| Summary: | JBDS 4.0 beta1 - errors are written to stdout of shell from which it invoked | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||
| Component: | EDS | Assignee: | Van Halbert <vhalbert> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.1.0.ER3 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | JBDS | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2505 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
SOA-P 5.1 ER3
Version: 4.0.0.Beta1
Build id: v201010052359R
|
|||||
| Last Closed: | 2011-11-30 19:19:53 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: | |||||
| Attachments: |
|
||||||
|
Description
Len DiMaggio
2010-10-27 20:55:45 UTC
Attachment: Added: JBDS_text_returned_to_shell.txt ModeShape is using Log4j logger, and its calling logger.trace() for a lot of the calls that I've identified. Not sure how tracing was turned on in eclipse. Link: Added: This issue is a dependency of JBDS-1386 Link: Added: This issue depends TEIIDDES-691 Link: Removed: This issue depends TEIIDDES-691 Investigate for 5.1.0, if they should be in SOA 5.1.0, Van will set the Fixed Version. I execute the modeshape-client.jar directly to publish files and I don't see any logging to stdout. My guess is who ever is running this has a log4j properties file somewhere that has the log level turned up. Changes were committed for the next JBDS release. Not seen in 4.1.1 |