topic Re: tHttpClient work correctly when executed from Studio, but does nothing when executed from the TAC in Talend Studio

tHttpClient work correctly when executed from Studio, but does nothing when executed from the TAC

GHDustin — Wed, 14 May 2025 13:18:59 GMT

We're converting tRestClient components to tHttpClient components to move with the recommendation of using tHttpClient. I made the conversion and ran several tests locally through studio and it worked as expected. However, when I deploy to the TAC. The GET request seems to do nothing. Below is a snip of the execution log from the TAC with Debug logging. Any help would be appreciated.

[DEBUG] 15:38:25 customermaster.mdm_contact_create_crm_0_16.MDM_Contact_Create_CRM- tHTTPClient_1 - Start to work.
[DEBUG] 15:38:25 customermaster.mdm_contact_create_crm_0_16.MDM_Contact_Create_CRM- tHTTPClient_1 - Parameters:configuration.dataset.datastore.base = context.CRM_Endpoint_URL+context.CRM_Entity_Contact | configuration.dataset.datastore.authentication.type = NoAuth | configuration.dataset.methodType = GET | configuration.dataset.resource = context.Guid | configuration.dataset.hasPathParams = false | configuration.dataset.hasQueryParams = false | configuration.dataset.hasHeaders = true | configuration.dataset.headers = [{configuration.dataset.headers[].key=context.APISubscriptionHeader, configuration.dataset.headers[].query=BOTH, configuration.dataset.headers[].value=context.APISubscriptionKey}, {configuration.dataset.headers[].key=context.X_CRM_Instance_Header, configuration.dataset.headers[].query=BOTH, configuration.dataset.headers[].value=context.X_CRM_Instance_Key}] | configuration.dataset.hasBody = false | configuration.dataset.format = RAW_TEXT | configuration.dataset.returnedContent = STATUS_HEADERS_BODY | configuration.dataset.outputKeyValuePairs = false | configuration.downloadFile = false | configuration.dataset.datastore.connectionTimeout = 30000 | configuration.dataset.datastore.receiveTimeout = 120000 | configuration.dataset.datastore.bypassCertificateValidation = false | configuration.dataset.datastore.useProxy = false | configuration.dataset.datastore.hasRetry = false | configuration.dataset.acceptRedirections = false | configuration.dataset.hasPagination = false | configuration.dataset.useCookies = false | configuration.dataset.saveCookies = false | configuration.uploadFiles = false | configuration.dieOnError = false |
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.service.path.PathHandlerImpl- [PathHandlerImpl] non existent path: ..\lib.
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.service.path.PathHandlerImpl- [PathHandlerImpl] non existent path: .m2\repository.
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.service.MavenRepositoryDefaultResolver- [fromEnvironmentVariables] M2_HOME=null
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.service.MavenRepositoryDefaultResolver- [fromEnvironmentVariables] Could not get m2 from environment.
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.service.MavenRepositoryDefaultResolver- [fallback] default to user's default repository.
[DEBUG] 15:38:25 org.talend.sdk.component.container.ContainerManager- Using root repository: C:\Windows\system32\config\systemprofile\.m2\repository
[DEBUG] 15:38:25 org.talend.sdk.component.container.ContainerManager- No TALEND-INF/plugins.properties found, will use file resolution
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.ComponentManager- ComponentManager version: 1.67.0
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.ComponentManager- Creating the contextual ComponentManager instance (classloader=jdk.internal.loader.ClassLoaders$AppClassLoader@45ff54e6, jvm=9680@TalendAdmin-Dev)
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.ComponentManager- Components: []
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.ComponentManager- Created the contextual ComponentManager instance (classloader=jdk.internal.loader.ClassLoaders$AppClassLoader@45ff54e6, jvm=9680@TalendAdmin-Dev)
[DEBUG] 15:38:25 org.talend.sdk.component.container.ContainerManager- Creating module D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar (from D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar, location=D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar)
[TRACE] 15:38:25 customermaster.azurequeue_process_message_crm_0_5.AzureQueue_Process_Message_CRM- tWaitForFile_1 - Nothing appened. Waiting for 1 seconds and continue to loop.
[DEBUG] 15:38:25 org.talend.sdk.component.container.ContainerManager- Created container dssl-dictionary
[DEBUG] 15:38:25 org.talend.sdk.component.runtime.manager.ComponentManager- Adding plugin: D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar, as dssl-dictionary
[DEBUG] 15:38:25 org.talend.sdk.component.container.ContainerManager- Creating module D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3700380046_1520568135\http-studio-1.66.0.jar (from D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3700380046_1520568135\http-studio-1.66.0.jar, location=D:\TalendPlatform\jobserver\agent\TalendJobServersFiles\cache\lib\3700380046_1520568135\http-studio-1.66.0.jar)
[statistics] disconnected
[statistics] disconnected
[statistics] disconnected
[DEBUG] 15:38:25 customermaster.mdm_contact_create_crm_0_16.MDM_Contact_Create_CRM- tDBClose_2 - Start to work.

Re: tHttpClient work correctly when executed from Studio, but does nothing when executed from the TAC

Denis_Segard — Sat, 17 May 2025 05:49:56 GMT

Build the job as a standalone job https://help.qlik.com/talend/en-US/studio-user-guide/8.0-R2024-08/building-job-as-standalone-job
and run it on the Studio Machine , then on the Jobserver machine
(the goal is to check if the problem is related to the ZIP file result of the Build or to the machine where the job is running ...)

Re: tHttpClient work correctly when executed from Studio, but does nothing when executed from the TAC

GHDustin — Wed, 21 May 2025 19:29:29 GMT

I did this. I executed the .bat from windows CMD. Both my development machine and the execution server process with the tHttpClient component correctly.

Re: tHttpClient work correctly when executed from Studio, but does nothing when executed from the TAC

Denis_Segard — Thu, 22 May 2025 05:40:08 GMT

Hello,
Did you try to run the job from the TAC with the Log4j Level set to Trace and check the log ?
Kind regards
Denis

Re: tHttpClient work correctly when executed from Studio, but does nothing when executed from the TAC

GHDustin — Thu, 22 May 2025 14:07:26 GMT

This log section here is from the TAC with TRACE set for Log4J.

[DEBUG] 09:00:15 customermaster.mdm_contact_create_crm_0_16.MDM_Contact_Create_CRM- tHTTPClient_2 - Start to work.
[DEBUG] 09:00:15 customermaster.mdm_contact_create_crm_0_16.MDM_Contact_Create_CRM- tHTTPClient_2 - Parameters:configuration.dataset.datastore.base = context.CRM_Endpoint_URL+context.CRM_Entity_Contact | configuration.dataset.datastore.authentication.type = NoAuth | configuration.dataset.methodType = GET | configuration.dataset.resource = context.Guid | configuration.dataset.hasPathParams = false | configuration.dataset.hasQueryParams = false | configuration.dataset.hasHeaders = true | configuration.dataset.headers = [{configuration.dataset.headers[].key=context.APISubscriptionHeader, configuration.dataset.headers[].query=BOTH, configuration.dataset.headers[].value=context.APISubscriptionKey}, {configuration.dataset.headers[].key=context.X_CRM_Instance_Header, configuration.dataset.headers[].query=BOTH, configuration.dataset.headers[].value=context.X_CRM_Instance_Key}] | configuration.dataset.hasBody = false | configuration.dataset.format = RAW_TEXT | configuration.dataset.returnedContent = STATUS_HEADERS_BODY | configuration.dataset.outputKeyValuePairs = false | configuration.downloadFile = false | configuration.dataset.datastore.connectionTimeout = 30000 | configuration.dataset.datastore.receiveTimeout = 120000 | configuration.dataset.datastore.bypassCertificateValidation = false | configuration.dataset.datastore.useProxy = false | configuration.dataset.datastore.hasRetry = false | configuration.dataset.acceptRedirections = false | configuration.dataset.hasPagination = false | configuration.dataset.useCookies = false | configuration.dataset.saveCookies = false | configuration.uploadFiles = false | configuration.dieOnError = false |
[DEBUG] 09:00:15 org.talend.sdk.component.runtime.manager.service.path.PathHandlerImpl- [PathHandlerImpl] non existent path: ..\lib.
[DEBUG] 09:00:15 org.talend.sdk.component.runtime.manager.service.path.PathHandlerImpl- [PathHandlerImpl] non existent path: .m2\repository.
[DEBUG] 09:00:15 org.talend.sdk.component.runtime.manager.service.MavenRepositoryDefaultResolver- [fromEnvironmentVariables] M2_HOME=null
[DEBUG] 09:00:15 org.talend.sdk.component.runtime.manager.service.MavenRepositoryDefaultResolver- [fromEnvironmentVariables] Could not get m2 from environment.
[DEBUG] 09:00:15 org.talend.sdk.component.runtime.manager.service.MavenRepositoryDefaultResolver- [fallback] default to user's default repository.
[DEBUG] 09:00:16 org.talend.sdk.component.container.ContainerManager- Using root repository: C:\Windows\system32\config\systemprofile\.m2\repository
[DEBUG] 09:00:16 org.talend.sdk.component.container.ContainerManager- No TALEND-INF/plugins.properties found, will use file resolution
[DEBUG] 09:00:16 org.talend.sdk.component.runtime.manager.ComponentManager- ComponentManager version: 1.67.0
[DEBUG] 09:00:16 org.talend.sdk.component.runtime.manager.ComponentManager- Creating the contextual ComponentManager instance (classloader=jdk.internal.loader.ClassLoaders$AppClassLoader@45ff54e6, jvm=15564@Talendadmin-TST)
[DEBUG] 09:00:16 org.talend.sdk.component.runtime.manager.ComponentManager- Components: []
[DEBUG] 09:00:16 org.talend.sdk.component.runtime.manager.ComponentManager- Created the contextual ComponentManager instance (classloader=jdk.internal.loader.ClassLoaders$AppClassLoader@45ff54e6, jvm=15564@Talendadmin-TST)
[DEBUG] 09:00:16 org.talend.sdk.component.container.ContainerManager- Creating module D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar (from D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar, location=D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar)
[DEBUG] 09:00:16 org.talend.sdk.component.container.ContainerManager- Created container dssl-dictionary
[DEBUG] 09:00:16 org.talend.sdk.component.runtime.manager.ComponentManager- Adding plugin: D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3177541072_2158889179\dssl-dictionary-1.66.0.jar, as dssl-dictionary
[DEBUG] 09:00:16 org.talend.sdk.component.container.ContainerManager- Creating module D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3700380046_1520568135\http-studio-1.66.0.jar (from D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3700380046_1520568135\http-studio-1.66.0.jar, location=D:\TalendPlatform\jobserver\jobserver\agent\TalendJobServersFiles\cache\lib\3700380046_1520568135\http-studio-1.66.0.jar)
[statistics] disconnected