Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
nfz11
Creator III
Creator III

Having more than one tFileFetch in your job causes error: "Duplicate local variable: myhttps"

It seems the Java code generator does not create the variables with unique names so if you have more than one tFileFetch component you will get an error.

 

 

org.apache.commons.httpclient.protocol.Protocol myhttps  = new org.apache.commons.httpclient.protocol.Protocol("https", new SocketFactory_<%=cid%>(), 443);
org.apache.commons.httpclient.protocol.Protocol.registerProtocol("https", myhttps);

If you change myhttps to myhttps_<%=cid%>  in tFileFetch_main.javajet and rebuild your project it will fix the error but this is a bug in Talend that should be fixed there.

 

I am using:

Talend Cloud Real-Time Big Data Platform

Version: 7.0.1
Build id: 20180411_1414

 

I am also attaching the installation details.

 

Thanks in advance for any help.

 

Labels (5)
1 Solution

Accepted Solutions
nfz11
Creator III
Creator III
Author

A support ticket for this issue has been accepted by Talend development here

https://talendsupport.force.com/CustomerCommunity/5003900002HK77PAAT?btdid=5003900002HK77PAAT

A fix for this will be incorporated in the next Talend release so I am marking this topic as solved.

View solution in original post

3 Replies
nfz11
Creator III
Creator III
Author

Note, I upgraded to 7.1.1 and this did not fix the issue.

nfz11
Creator III
Creator III
Author

A support ticket for this issue has been accepted by Talend development here

https://talendsupport.force.com/CustomerCommunity/5003900002HK77PAAT?btdid=5003900002HK77PAAT

A fix for this will be incorporated in the next Talend release so I am marking this topic as solved.

lennelei
Creator III
Creator III

Hi,

Unless I'm mistaken, you should have the issue only when the tFileFetch are linked with a data row which is not necessary the most logical way to use them.
You should'nt have the issue if your tFileFetch are linked with a onComponentOk or onSubjobOk.
Regards