BW Engine fails writing to stdout from Java activities to its own log file fails.
Article ID: KB0088897
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
Description
----------------
No logs are generated when invoking an external Java class from within a BW Java code activity with the external Java class having the following statement:
System.out.println("Here is a log line");
Resolution
---------------
The system.out.println statement used in Java code/Java method activity will be logged in the stdout.log when tested from Designer. In Admin, you can use log4j to direct log output to the standard BW log, which is the recommended way to handle logs. Refer to the "BW palette Reference/Chapter 7 Java Palette/ Common Features of Java Code and Java Method/
Sending Messages to the TIBCO BW log4j File".
Description
----------------
No logs are generated when invoking an external Java class from within a BW Java code activity with the external Java class having the following statement:
System.out.println("Here is a log line");
Resolution
---------------
The system.out.println statement used in Java code/Java method activity will be logged in the stdout.log when tested from Designer. In Admin, you can use log4j to direct log output to the standard BW log, which is the recommended way to handle logs. Refer to the "BW palette Reference/Chapter 7 Java Palette/ Common Features of Java Code and Java Method/
Sending Messages to the TIBCO BW log4j File".
Issue/Introduction
BW Engine fails writing to stdout from Java activities to its own log file fails.
Additional Information
BW Palette Reference.
Feedback
Yes
No
Powered by
