<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: tLogCatcher - stacktrace in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308481#M79804</link>
    <description>In this case I would not use the tLogCatcher instead I would use the direction of the standard out to a log file to get all stack traces.</description>
    <pubDate>Fri, 26 Sep 2014 13:50:01 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2014-09-26T13:50:01Z</dc:date>
    <item>
      <title>tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308480#M79803</link>
      <description>Hello All, 
&lt;BR /&gt;We are using Talend 5.3.1. Our customer requires for exceptions the whole stacktrace written to log files. 
&lt;BR /&gt;Unfortunately tLogCatcher gives you just the exception message but nothing more. Is there currently a way 
&lt;BR /&gt;to get the complete stacktrace? 
&lt;BR /&gt;Kind regards, 
&lt;BR /&gt;Hilderich</description>
      <pubDate>Fri, 26 Sep 2014 12:21:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308480#M79803</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-09-26T12:21:29Z</dc:date>
    </item>
    <item>
      <title>Re: tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308481#M79804</link>
      <description>In this case I would not use the tLogCatcher instead I would use the direction of the standard out to a log file to get all stack traces.</description>
      <pubDate>Fri, 26 Sep 2014 13:50:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308481#M79804</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-09-26T13:50:01Z</dc:date>
    </item>
    <item>
      <title>Re: tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308482#M79805</link>
      <description>Hello Jan,&lt;BR /&gt;What's the name of the component you are talking about? Can this approach the same as tLogCatcher can do?&lt;BR /&gt;Kind regards,&lt;BR /&gt;Hilderich</description>
      <pubDate>Fri, 26 Sep 2014 13:58:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308482#M79805</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-09-26T13:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308483#M79806</link>
      <description>This is not a component, it is the redirection of the output of the standalone exported job.
&lt;BR /&gt;But of course there is also a possibility to get the logs in a readable way into log files:
&lt;BR /&gt;You could use the components tJobInstanceStart + tJobInstanceEnd from Talend Exchange. These suite allows using Log4J and catches automatically all outputs from System.out/err and what is send over the Talend logging components.
&lt;BR /&gt;The logging can be configured via the typically log4j configuration or within the component to a log file or log table.
&lt;BR /&gt;But these components are more dedicated to replace the AMC database.
&lt;BR /&gt;Also in the TAC in the log file you see the stack traces.</description>
      <pubDate>Fri, 26 Sep 2014 15:16:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308483#M79806</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-09-26T15:16:22Z</dc:date>
    </item>
    <item>
      <title>Re: tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308484#M79807</link>
      <description>Hello Jan,&lt;BR /&gt;above you told me &lt;B&gt;...I would use the direction of the standard out to a log file to get all stack traces.&lt;/B&gt;&lt;BR /&gt;How can I do that when the job is deployed by TAC on a Job Server? How can i log standard out to a logfile? &lt;BR /&gt;Is this general linux (OS) stuff?&lt;BR /&gt;Kind regards,&lt;BR /&gt;Hilderich</description>
      <pubDate>Wed, 01 Oct 2014 16:19:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308484#M79807</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-10-01T16:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308485#M79808</link>
      <description>I guess you mean something like this: 
&lt;BR /&gt; 
&lt;A href="https://community.qlik.com/s/feed/0D53p00007vCnlfCAC" rel="nofollow noopener noreferrer"&gt;https://community.talend.com/t5/Design-and-Development/How-to-redirect-standard-output-to-a-file/td-p/90451&lt;/A&gt;</description>
      <pubDate>Wed, 01 Oct 2014 16:38:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308485#M79808</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-10-01T16:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: tLogCatcher - stacktrace</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308486#M79809</link>
      <description>In the Job view in the section Extras&amp;amp;Logs you can set a log file or a database log table. I would use this feature at first.</description>
      <pubDate>Thu, 02 Oct 2014 21:49:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tLogCatcher-stacktrace/m-p/2308486#M79809</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2014-10-02T21:49:20Z</dc:date>
    </item>
  </channel>
</rss>

