topic Re: Get a warning tRest component, Studio R2024-07 in Talend Studio

Get a warning tRest component, Studio R2024-07

Jacco_De_Zwart — Tue, 30 Jul 2024 08:09:43 GMT

Hi all,

I have a job that incldes a tRest component which calls a web-service.

All is configured well, but when running the job I get the following warning :

jul. 30, 2024 10:07:31 A.M. org.glassfish.jersey.client.innate.inject.NonInjectionManager <init>
WARNING: Falling back to injection-less client.

The call to the webservice succeeds, data is retreivable, but where comes this warning from ? I reinstalled Talend Studio, upgaded to R2024-07, installed the additional libraries when I open the job for the first time.

What can be wrong ??

Re: Get a warning tRest component, Studio R2024-07

azT — Wed, 31 Jul 2024 00:52:22 GMT

Getting same error. Lot of my jobs are failing with this error - Lesson learned. Never update Talend

Re: Get a warning tRest component, Studio R2024-07

jlolling — Wed, 31 Jul 2024 10:56:41 GMT

You can ignore this message. This message tells us the client cannot use byte code injection but Talend do not use this method. It is actually an error of the component itself because of a missing jar.

If you can, ignore this!

Re: Get a warning tRest component, Studio R2024-07

jlolling — Wed, 31 Jul 2024 10:59:28 GMT

Thats for sure not the right lesson learned. If you do not update frequently you will run into some other trouble. Yes this component is a bad configured because a dependency is not taken which would prevent this error message. This error message does not affect our jobs or services because the client complaints it cannot use byte code injection but Talend does not use this feature at all.

Re: Get a warning tRest component, Studio R2024-07

Jacco_De_Zwart — Wed, 31 Jul 2024 11:14:38 GMT

Thanks Jan,

I will ignore the message since everything works fine. As for the 'missing' jar, is it an option to add the jar in someway ?

Re: Get a warning tRest component, Studio R2024-07

jlolling — Wed, 31 Jul 2024 11:19:10 GMT

Yes, download this jar: https://repo1.maven.org/maven2/org/glassfish/jersey/inject/jersey-hk2/3.1.7/jersey-hk2-3.1.7.jar

and added it per tLibraryLoad to your job. This should solve the error message.

Re: Get a warning tRest component, Studio R2024-07

JDUbanco — Tue, 27 Aug 2024 16:04:27 GMT

Hello there, I encountered the same error and tried to add the jar by tLibraryLoad.

The configuration :

I get an error :

Exception in thread "main" java.lang.NoClassDefFoundError: org/glassfish/hk2/api/ServiceLocatorFactory
 at org.glassfish.jersey.inject.hk2.AbstractHk2InjectionManager.<clinit>(AbstractHk2InjectionManager.java:51)
 at org.glassfish.jersey.inject.hk2.Hk2InjectionManagerFactory$Hk2InjectionManagerStrategy$1.createInjectionManager(Hk2InjectionManagerFactory.java:55)
 at org.glassfish.jersey.inject.hk2.Hk2InjectionManagerFactory.create(Hk2InjectionManagerFactory.java:73)
 at org.glassfish.jersey.internal.inject.InjectionManagerFactory.create(InjectionManagerFactory.java:32)
 at org.glassfish.jersey.internal.inject.Injections.createInjectionManager(Injections.java:56)
 at org.glassfish.jersey.client.ClientConfig$State.findInjectionManager(ClientConfig.java:477)
 at org.glassfish.jersey.client.ClientConfig$State.initRuntime(ClientConfig.java:414)
 at org.glassfish.jersey.internal.util.collection.Values$LazyValueImpl.get(Values.java:317)
 at org.glassfish.jersey.client.ClientConfig.getRuntime(ClientConfig.java:829)
 at org.glassfish.jersey.client.ClientRequest.getClientRuntime(ClientRequest.java:183)
 at org.glassfish.jersey.client.JerseyWebTarget.onBuilder(JerseyWebTarget.java:371)
 at org.glassfish.jersey.client.JerseyWebTarget.request(JerseyWebTarget.java:199)
 at org.glassfish.jersey.client.JerseyWebTarget.request(JerseyWebTarget.java:38)
Caused by: java.lang.ClassNotFoundException: org.glassfish.hk2.api.ServiceLocatorFactory
 at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
 at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
 at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)

Re: Get a warning tRest component, Studio R2024-07

Tim_Ouimet — Tue, 27 Aug 2024 18:00:32 GMT

Had the same issue - the component tRest seems to work just fine. With loading the tLibrary for jersey-hk... it fails catastrophically.

Re: Get a warning tRest component, Studio R2024-07

Xiaodi_Shi — Wed, 28 Aug 2024 02:47:24 GMT

Hello,

tREST is a DI component not an ESB component, which is based on jersey libraries.
tRESTClient is an ESB component, is based on CXF framework, and support more ESB features e.g SAM/SL/Authentication, moreover, the Job with tRESTClient is able to be built as OSGi bundle which can be deployed into Talend Runtime.

It is better to use tRESTClient if you want to deploy and manage it using Runtime (SSL config for service/client can be defined inside org.apache.cxf.http.conduits-common.cfg)

Best regards

Sabrina

Re: Get a warning tRest component, Studio R2024-07

Jacco_De_Zwart — Fri, 30 Aug 2024 05:59:58 GMT

Hey,

I also tried to inport the libary, but then it asks which class I want to import. Got no idea, so I stopped. Since the compontent works fine, besides the error, I left it like it is.

But in order to get an error-free flow, I start using other components like tHTTP, tHTTPClient

It does nearly the same thing.

Jacco

Re: Get a warning tRest component, Studio R2024-07

Jacco_De_Zwart — Fri, 30 Aug 2024 06:04:37 GMT

Sabrina,

Thanks for you clear answer, as always.

But when a component is not specifically for ESB, then why is it selectable when creating a flow ? I think is should be not that difficult that components that are not appropriate for ESB but mainly for DI, get filterd out or marked in a way that developers can see if they made the right choise.

Besides that, jlolling said it was a missing jar. Why is that jar not in the Talend/Studio libray then, problem solved and you don't have to worry about picking a component that is for ESB and not for DI.

Jacco

Re: Get a warning tRest component, Studio R2024-07

JDUbanco — Fri, 30 Aug 2024 06:59:31 GMT

Thanks a lot, it worked fine with trestclient component, no more warnings !

Re: Get a warning tRest component, Studio R2024-07

Xiaodi_Shi — Fri, 30 Aug 2024 08:24:49 GMT

Hello,

Thanks for your reply.

Here is a note in this component reference about:

https://help.talend.com/en-US/components/8.0/rest/trest

To build Jobs that need to be deployed into the Talend Runtime, it is recommended to use the tRESTClient component which is best suited for the Talend Runtime.

For your second issue about this missing jar issue in tRest component, I will check it with our R&D team and come back to you as soon as we can.

Best regards

Sabrina

Re: Get a warning tRest component, Studio R2024-07

User16806936386127367355 — Tue, 15 Oct 2024 13:27:04 GMT

Are your jobs failing or just showing the warning?

Re: Get a warning tRest component, Studio R2024-07

Jacco_De_Zwart — Tue, 15 Oct 2024 13:55:17 GMT

The job is not failing, but shows an warning.

Re: Get a warning tRest component, Studio R2024-07

seanbruton — Tue, 15 Oct 2024 23:34:47 GMT

Kudos nice solution!!

Re: Get a warning tRest component, Studio R2024-07

AFTOUH — Wed, 18 Dec 2024 12:01:32 GMT

Hello,

Support replie: Add the two jars :
jersey-injectless-client-3.1.8.jar and jakarta.activation-api-1.2.2.jar, it will go directly to the injectless client instead of trying first the inject client.

Regards

Re: Get a warning tRest component, Studio R2024-07

dgreenx — Mon, 23 Dec 2024 15:49:51 GMT

Talend support,

Please provide instructions how to properly install this module in Talend Studio so the error will be resolved.

Please do not give answers like "don't use the tRest component, but instead use the tRestClient component".

Please solve this issue for people having this problem. I am included. I am having this issue. And when I make many tRest calls the job runs out of memory, probably because the log data being saved is growing so large.

Thanks,