topic Re: Upgraded to 7.2 Data integration open studio in Installing and Upgrading

Upgraded to 7.2 Data integration open studio

Anonymous — Sat, 16 Nov 2024 04:01:03 GMT

Hi All,

Receiving an error

Exception in thread "main" java.lang.NoSuchMethodError: org.apache.commons.beanutils.PropertyUtils.addBeanIntrospector(Lorg/apache/commons/beanutils/BeanIntrospectorV
at com.sforce.ws.bind.XmlObjectWrapper.<clinit>(XmlObjectWrapper.java:47)
at com.sforce.ws.bind.XmlObject.extractChildElement(XmlObject.java:355)
at com.sforce.ws.bind.XmlObject.loadAfterStartTag(XmlObject.java:311)
at com.sforce.ws.bind.XmlObject.load(XmlObject.java:294)
at com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674)
at com.sforce.ws.bind.TypeMapper.readArray(TypeMapper.java:580)
at com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:558)
at com.sforce.soap.partner.QueryResult.setRecords(QueryResult.java:115)
at com.sforce.soap.partner.QueryResult.loadFields1(QueryResult.java:210)
at com.sforce.soap.partner.QueryResult.loadFields(QueryResult.java:181)
at com.sforce.soap.partner.QueryResult.load(QueryResult.java:175)
at com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674)
at com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:556)
at com.sforce.soap.partner.QueryResponse_element.setResult(QueryResponse_element.java:48)
at com.sforce.soap.partner.QueryResponse_element.loadFields1(QueryResponse_element.java:107)
at com.sforce.soap.partner.QueryResponse_element.loadFields(QueryResponse_element.java:83)
at com.sforce.soap.partner.QueryResponse_element.load(QueryResponse_element.java:77)
at com.sforce.ws.bind.TypeMapper.readSingle(TypeMapper.java:674)
at com.sforce.ws.bind.TypeMapper.readObject(TypeMapper.java:556)
at com.sforce.ws.transport.SoapConnection.bind(SoapConnection.java:180)
at com.sforce.ws.transport.SoapConnection.receive(SoapConnection.java:154)
at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:99)
at com.sforce.soap.partner.PartnerConnection.query(PartnerConnection.java:1197)
at org.talend.components.salesforce.runtime.SalesforceInputReader.executeSalesforceQuery(SalesforceInputReader.java:163)
at org.talend.components.salesforce.runtime.SalesforceInputReader.start(SalesforceInputReader.java:105)
at org.talend.codegen.flowvariables.runtime.FlowVariablesReader.start(FlowVariablesReader.java:73)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tSalesforceInput_7Process(NAV_SF_Contract_Sync_Update.java:64468)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tHashInput_2Process(NAV_SF_Contract_Sync_Update.java:26050)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tHashInput_1Process(NAV_SF_Contract_Sync_Update.java:21734)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tLoop_1Process(NAV_SF_Contract_Sync_Update.java:11312)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tMysqlCommit_2Process(NAV_SF_Contract_Sync_Update.java:3142)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tMysqlRow_1Process(NAV_SF_Contract_Sync_Update.java:3005)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tFixedFlowInput_1Process(NAV_SF_Contract_Sync_Update.java:2771)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tJava_1Process(NAV_SF_Contract_Sync_Update.java:58224)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tSalesforceConnection_1Process(NAV_SF_Contract_Sync_Update.java:58626)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.tMysqlConnection_1Process(NAV_SF_Contract_Sync_Update.java:58386)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.runJobInTOS(NAV_SF_Contract_Sync_Update.java:517)
at productionnochanges.nav_sf_contract_sync_update_1_0.NAV_SF_Contract_Sync_Update.main(NAV_SF_Contract_Sync_Update.java:65252)

A colleague has the same setup but I am receivbing this nosuchmethod error around a tsalsforceinput component however I about 6 other tsalesforce components are working before this one. Any ideas? Tsalesforceinput_7 seems to be the issue

Cheers

Truez

Re: Upgraded to 7.2 Data integration open studio

Anonymous — Wed, 27 Nov 2019 07:55:34 GMT

Hello,

Does this issue only repro on this specific job? I suppose this could be a problem of alignment of jars.

Best regards

Sabrina

Re: Upgraded to 7.2 Data integration open studio

Anonymous — Wed, 27 Nov 2019 10:08:45 GMT

Hi Sabrina,

I've not tried other jobs yet as I have a requirement to get this working!

I want to say it's because talend cannot find the beanutils jar. So I went to here to download the jar. And then used module to import the jar in.

But this hasn't reolved the issue.

The last installation of talend I didn't receive any of this so I am a little mythed as to why this is occurring. I've also used the same installation as a colleague and he can import the job and run it without issue.

Cheers

Truez

Re: Upgraded to 7.2 Data integration open studio

Anonymous — Thu, 28 Nov 2019 06:46:27 GMT

Hello,

Does your Talend Studio have a secure Internet connection? Are you working behind a network proxy? What's JDK version are you using?

Did you follow up this online documentation about:TalendHelpCenter:Installing external modules manually using the Modules view to install beanutils jar by manual? More information will be preferred.

Best regards

Sabrina

Re: Upgraded to 7.2 Data integration open studio

Anonymous — Thu, 28 Nov 2019 07:58:11 GMT

Hi Sabrina,

Internet connection - Yes

Using the latest and greatest of AdoptOpenJDK

Followed those instructions but still getting the error.

I have limited the fields which the Tsalesforceinput is pulling and this seems to fix the issue, The schema appears to be the issue however it's the same schema on my old machine with talend 7.0.1 and I do not have any issues so I am wondering if something in the Tsalesforceinput component schema retrieval is playing up. We've considered it could be some funky data however it's why does it work with my old setup which is confusing me.

i imported the jobs and the contexts which I think I am going to rebuild if I cannot get this fixed because it seems like the jump to talend 7.2 isn't a good move without rebuilding. I've only done the upgrade because of a new laptop and we are currently setting a new production environment.

Cheers

Truez

Re: Upgraded to 7.2 Data integration open studio

Anonymous — Thu, 05 Dec 2019 10:03:05 GMT

Hi Sabrina,

The issue is related to two fields in the Schema coming from Salesforce. BillingAddress and ShippingAddress on the contract object, If I remove these fields it works perfectly. The two fields in question are of type address in Salesforce and are read only. It only occurs on jobs that have been migrated from an older version of talend.

New jobs seem to work fine

Cheers

Truez

Re: Upgraded to 7.2 Data integration open studio

Anonymous — Wed, 18 Dec 2019 06:12:51 GMT

@Truezplaya wrote:

Hi MyKFC,

The issue is related to two fields in the Schema coming from Salesforce. BillingAddress and ShippingAddress on the contract object, If I remove these fields it works perfectly. The two fields in question are of type address in Salesforce and are read only. It only occurs on jobs that have been migrated from an older version of talend.

New jobs seem to work fine

The schema appears to be the issue however it's the same schema on my old machine with talend 7.0.1 and I do not have any issues so I am wondering if something in the Tsalesforceinput component schema retrieval is playing up. We've considered it could be some funky data however it's why does it work with my old setup which is confusing me.