<?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: DI-Component tJMSInput in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357086#M122467</link>
    <description>This is an issue with the way that the component is designed and implements the commit. The component assumes that the job will open a connection, read a message, then close the connection. However, when a job is set up as a service and processes multiple messages, then the job needs to do a commit after each message is processed.
&lt;BR /&gt;I gave Talend the fix for tMomInput a few years ago, but it looks like Talend did not implement the code in tJMSInput - only in tMomInput. Can you use the tMomInput instead of tJMSInput? tMomInput has a check box for "Commit (delete message after read from queue).</description>
    <pubDate>Fri, 20 Sep 2013 15:37:36 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2013-09-20T15:37:36Z</dc:date>
    <item>
      <title>DI-Component tJMSInput</title>
      <link>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357085#M122466</link>
      <description>Dear Sir or Madam! 
&lt;BR /&gt;Talend DI with Talend Open Studio provides the tJMSInput component. The problem is that the message 
&lt;BR /&gt;inside the JMS queue is not removed immediately by tJMSInput, instead that message is removed when 
&lt;BR /&gt;the whole job and its sub jobs are completly finished. However when any runtime exceptions occur that 
&lt;BR /&gt;message is still inside the JMS queue. Regarding to our requirements that behaviour is not what we need. 
&lt;BR /&gt;Could you please give us some hints to fulfill such requirements? 
&lt;BR /&gt;Kind regards 
&lt;BR /&gt;Johannes</description>
      <pubDate>Thu, 19 Sep 2013 16:09:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357085#M122466</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-09-19T16:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: DI-Component tJMSInput</title>
      <link>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357086#M122467</link>
      <description>This is an issue with the way that the component is designed and implements the commit. The component assumes that the job will open a connection, read a message, then close the connection. However, when a job is set up as a service and processes multiple messages, then the job needs to do a commit after each message is processed.
&lt;BR /&gt;I gave Talend the fix for tMomInput a few years ago, but it looks like Talend did not implement the code in tJMSInput - only in tMomInput. Can you use the tMomInput instead of tJMSInput? tMomInput has a check box for "Commit (delete message after read from queue).</description>
      <pubDate>Fri, 20 Sep 2013 15:37:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357086#M122467</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-09-20T15:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: DI-Component tJMSInput</title>
      <link>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357087#M122468</link>
      <description>wrlawton, many thanks! Your explanation helps to gain a more deeper understanding. Thanks a lot!</description>
      <pubDate>Mon, 23 Sep 2013 09:44:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/DI-Component-tJMSInput/m-p/2357087#M122468</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-09-23T09:44:48Z</dc:date>
    </item>
  </channel>
</rss>

