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

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] tRuleSurvivorship error: Unknown resource type: ResourceType = jBPMN2

Hi,
I'm trying to use a tRuleSurvivorship component, I was able to create rules but when I execute the job, the exception below occurs.
Exception in component tRuleSurvivorship_1
java.lang.RuntimeException: Unknown resource type: ResourceType = 'jBPM BPMN2 Language'
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:553)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25)
at org.talend.survivorship.SurvivorshipManager.initKnowledgeBase(SurvivorshipManager.java:143)
at

Any ideas what's the cause of this?
0683p000009MBBH.png
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

This is solved now.
You have to make sure that there are no other libraries loaded on the job that will cause conflict.

View solution in original post

7 Replies
Anonymous
Not applicable
Author

Hi,
Could you please give us your screenshot of tRuleSurvivorship component setting so that we can address your issue quickly.
Best regards
Sabrina
Anonymous
Not applicable
Author

Hi Sabrina,
I've attached the screenshot of the basic settings and schema for the component tRuleSurivorship, I've also attached the generated rules and flow.
Thanks,
Chris
0683p000009MBBM.png 0683p000009MBBR.png 0683p000009MBBW.png
Anonymous
Not applicable
Author

Schema Screenshot
0683p000009MB2C.png
Anonymous
Not applicable
Author

Sorry for the multiple reply, I had issue uploading an image.
Anonymous
Not applicable
Author

Component Screenshot
0683p000009MBAZ.png
Anonymous
Not applicable
Author

Could not still find a solution on the problem.
I've tried loading other libraries on the job but still the exception exist.
Anonymous
Not applicable
Author

This is solved now.
You have to make sure that there are no other libraries loaded on the job that will cause conflict.