Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
TRF
Champion II
Champion II

REST service deployed into a 7.3.1 ESB container crashes when using tWriteJSONField component

Hello,

As for this post https://community.talend.com/s/feed/0D53p00007vCjUOCA0 I am unable to run a REST service when deployed into a 7.3.1 ESB container (Windows and Linux) as soon as it includes a tWriteJSONField component (see following error stack).

The same service built with the same Studio 7.3.1 and deployed into a 6.4.1 or a 7.1.1 container works fine.

I've tried to install and start bundle commons-lang/2.6 without any success (bundle:install wrap:mvn:commons-lang/commons-lang/2.6 + bundle:start).

As this problem seems to be not new, is there a well known fix or should we have to stay on 7.1.1 or older versions?

Thanks for your answer(s).

java.lang.NoClassDefFoundError: org/apache/commons/lang/exception/NestableRuntimeException

    at java.lang.ClassLoader.defineClass1(Native Method)

    at java.lang.ClassLoader.defineClass(Unknown Source)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:276)

    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:655)

    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:578)

    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:538)

    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:525)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)

    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:368)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:446)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)

    at java.lang.ClassLoader.loadClass(Unknown Source)

    at gpf.s0w01_contact_0_1.S0W01_Contact.tWriteJSONField_3_InProcess(S0W01_Contact.java:3372)

    at gpf.s0w01_contact_0_1.S0W01_Contact$1ThreadXMLField_tWriteJSONField_3_Out.run(S0W01_Contact.java:1801)

Caused by: java.lang.ClassNotFoundException: org.apache.commons.lang.exception.NestableRuntimeException cannot be found by gpf.S0W01_Contact_0.1.0

    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)

    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)

    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)

    at java.lang.ClassLoader.loadClass(Unknown Source)

    ... 16 more

Labels (2)
3 Replies
Anonymous
Not applicable

Hi @Fred Trebuchet​, sorry about the late response. Have you been able to send this issue to support? If not, can you give me as much detail as you have and I will see if I can get some answers

TRF
Champion II
Champion II
Author

Hi @Richard Hall​ ,

 

Thanks for your answer.

I didn't send anything to the support as this issue was detected with Community version.

All details are in my post. As you can see, the problem occurs only when running on a 7.3.1 ESB container, not 7.1.1 nor 6.41 even if the service was built with TOS version 7.3.1.

 

Regards

Anonymous
Not applicable

I see. I can't give you an answer to this, but I can point you in the direction I would take to find the fault. It looks like a runtime Jar is missing. A quick way to find the fault is to search for a Jar containing the missing class (org.apache.commons.lang.exception.NestableRuntimeException) and drop it in the deploy folder of your runtime. This may not entirely fix this, but it will almost certainly at least change the error. Then it is a case of doing the same thing until it works.