<?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: Get thread and pool numbers in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343596#M111339</link>
    <description>&lt;P&gt;&lt;A href="https://community.qlik.com/s/profile/005390000069RuGAAU"&gt;@rhall&lt;/A&gt;&amp;nbsp;&amp;nbsp;We are reworking a suite of Talend jobs which a consultancy firm created for our company. The way they had chosen to create logs in these jobs was to use the tLogRow and then give the testing team access to the tesb.log on the ESB server which is extrememly bad practice and not fit to go into production. I've updated them so the jobs now log to an external file away from the ESB server, however, the testers have stated that they use the thread number in the tesb.log to trace a request through the system. I could obviosuly create some kind of ID which persistes end to end but thought if it was easy to replicate the tesb.log functionality then I'd do that.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jun 2019 10:22:25 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-06-04T10:22:25Z</dc:date>
    <item>
      <title>Get thread and pool numbers</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343594#M111337</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;I've noticed that in the tesb.log files Talend logs the pool and thread id numbers&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;2019-05-30T11:03:45,356 | INFO | &lt;STRONG&gt;pool-36-thread-85&lt;/STRONG&gt; |&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Is there a way to get this programmatically to add to a custom log file? I've tried&amp;nbsp;Thread.currentThread() but this seems to be something different as i get i.e.&amp;nbsp;Thread[main,5,main]&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 05:42:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343594#M111337</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T05:42:19Z</dc:date>
    </item>
    <item>
      <title>Re: Get thread and pool numbers</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343595#M111338</link>
      <description>&lt;P&gt;I'm not sure how useful this will be to you, but you might want to look here:&amp;nbsp;&lt;A href="https://www.journaldev.com/1069/threadpoolexecutor-java-thread-pool-example-executorservice" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.journaldev.com/1069/threadpoolexecutor-java-thread-pool-example-executorservice&lt;/A&gt;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;What sort of logging are you trying to achieve? I think there might be more useful mechanisms for you to make use of.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 11:21:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343595#M111338</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-31T11:21:32Z</dc:date>
    </item>
    <item>
      <title>Re: Get thread and pool numbers</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343596#M111339</link>
      <description>&lt;P&gt;&lt;A href="https://community.qlik.com/s/profile/005390000069RuGAAU"&gt;@rhall&lt;/A&gt;&amp;nbsp;&amp;nbsp;We are reworking a suite of Talend jobs which a consultancy firm created for our company. The way they had chosen to create logs in these jobs was to use the tLogRow and then give the testing team access to the tesb.log on the ESB server which is extrememly bad practice and not fit to go into production. I've updated them so the jobs now log to an external file away from the ESB server, however, the testers have stated that they use the thread number in the tesb.log to trace a request through the system. I could obviosuly create some kind of ID which persistes end to end but thought if it was easy to replicate the tesb.log functionality then I'd do that.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2019 10:22:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Get-thread-and-pool-numbers/m-p/2343596#M111339</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-06-04T10:22:25Z</dc:date>
    </item>
  </channel>
</rss>

