Bug 1293587 - Error jitting a compareTo constraint
Error jitting a compareTo constraint
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: BRE (Show other bugs)
Unspecified Unspecified
high Severity unspecified
: DR1
: 6.3.0
Assigned To: Mario Fusco
Marek Winkler
Depends On:
Blocks: 1294424
  Show dependency treegraph
Reported: 2015-12-22 04:48 EST by Anton Giertli
Modified: 2016-03-18 10:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1294424 (view as bug list)
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
[0] reproducer (5.24 KB, application/zip)
2015-12-22 04:48 EST, Anton Giertli
no flags Details

  None (edit)
Description Anton Giertli 2015-12-22 04:48:48 EST
Created attachment 1108600 [details]
[0] reproducer

Description of problem:

Since this issue was reported by a customer, I have created bugzilla which covers this JIRA

When the implementation of the Comparable interface is not directly declared by a Class, but the Class implements another interface that transitively extends Comparable the jitting of a constraint doing a compareTo on that class fails with the following exception:

Version-Release number of selected component (if applicable):

BRMS 6.2.0
How reproducible:

Steps to Reproduce:
1. Run the reproducer

Actual results:

Reproducer fails with methodnotfound error
Expected results:
Reproducer does not fail

Additional info:
Comment 1 Anton Giertli 2015-12-22 04:50:05 EST
This is not the same issue as reported in here

the reproducer attached in here, fails when using 6.2.0

There is one workaround available - disable jitting.
System.setProperty("drools.jittingThreshold", "-1");

This workaround is only applicable on 6.2.0 and not for previous versions.
Comment 5 Marek Winkler 2016-03-18 10:26:39 EDT
Verified in BRMS 6.3.0.ER1.

Note You need to log in before you can comment on or make changes to this bug.