topic Re: Capture System.out.println in Talend Studio

Capture System.out.println

root — Sat, 16 Nov 2024 09:59:19 GMT

I am currently running karaf by doing ./trun
This prints out all messages logged on to the console. How to capture these messages when running in background via ./start?
Please advise. Thank you.

Re: Capture System.out.println

vharcq — Fri, 17 Mar 2017 15:30:07 GMT

Then it goes to <karaf>/log/tesb.log

Re: Capture System.out.println

root — Fri, 17 Mar 2017 16:01:33 GMT

Then it goes to <karaf>/log/tesb.log

I checked that, I could not find those system.out.printlns

Re: Capture System.out.println

vharcq — Fri, 17 Mar 2017 23:45:12 GMT

Could you try Log4j logger ?

Re: Capture System.out.println

Anonymous — Sat, 18 Mar 2017 00:23:41 GMT

In Studio under File -> edit project properties there is configuration of log4j (version 1) - there are also some components for log4j logging in Talend Exchange.
This is for any Talend product the same. In case of ESB as we have Karaf instance available there is also karaf Pax logging system, which integrates the Talend log4j. Look at container/etc/org.ops4j.pax.logging.cfg where you can also configure loggers which can be then called from any bundle deployed in following way:
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
...
private final static Logger LOG = LoggerFactory.getLogger(MyService.class);
...
LOGGER.info("Service myservice audittrail: entering the pipeline");
....if you like the pure Java

Re: Capture System.out.println

root — Mon, 20 Mar 2017 15:16:29 GMT

In Studio under File -> edit project properties there is configuration of log4j (version 1) - there are also some components for log4j logging in Talend Exchange.
This is for any Talend product the same. In case of ESB as we have Karaf instance available there is also karaf Pax logging system, which integrates the Talend log4j. Look at container/etc/org.ops4j.pax.logging.cfg where you can also configure loggers which can be then called from any bundle deployed in following way:
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
...
private final static Logger LOG = LoggerFactory.getLogger(MyService.class);
...
LOGGER.info("Service myservice audittrail: entering the pipeline");
....if you like the pure Java

So, when I have my service running using ./trun, it outputs all logs to the console. What is different in doing ./start and not being able to save/ view the logs?