Bug 780135 (SOA-2505) - JBDS 4.0 beta1 - errors are written to stdout of shell from which it invoked
Summary: JBDS 4.0 beta1 - errors are written to stdout of shell from which it invoked
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2505
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: JBDS
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-27 20:55 UTC by Len DiMaggio
Modified: 2011-11-30 19:19 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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


Attachments (Terms of Use)
JBDS_text_returned_to_shell.txt (175.56 KB, text/plain)
2010-10-27 20:56 UTC, Len DiMaggio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2505 0 None None None Never

Description Len DiMaggio 2010-10-27 20:55:45 UTC
project_key: SOA

Sample output - generated by the error in SOA-2504 - is attached.

Comment 1 Len DiMaggio 2010-10-27 20:56:18 UTC
Attachment: Added: JBDS_text_returned_to_shell.txt


Comment 2 Van Halbert 2010-10-28 02:31:01 UTC
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.  

Comment 3 Len DiMaggio 2010-10-28 02:38:59 UTC
Link: Added: This issue is a dependency of JBDS-1386


Comment 4 Van Halbert 2010-10-28 15:50:19 UTC
Link: Added: This issue depends TEIIDDES-691


Comment 5 Van Halbert 2010-10-28 15:50:51 UTC
Link: Removed: This issue depends TEIIDDES-691 


Comment 6 Anne-Louise Tangring 2010-10-28 16:18:44 UTC
Investigate for 5.1.0, if they should be in SOA 5.1.0, Van will set the Fixed Version.

Comment 7 Van Halbert 2010-10-28 19:46:04 UTC
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.

Comment 8 Van Halbert 2010-11-04 12:13:31 UTC
Changes were committed for the next JBDS release.   

Comment 9 Len DiMaggio 2011-11-30 19:19:53 UTC
Not seen in 4.1.1


Note You need to log in before you can comment on or make changes to this bug.