| Category: | Bug report |
Priority: | High |
Status: | Resolved |
| Project: | Severity: | Major |
Resolution: | Fixed |
|
| Component: | Reproducibility: | Always |
Assigned to: |
Hi, We use jaspersoft studio 6.6.0 on windows 10 with oracle 12c database (ojdbc8.jar).
Frequently when trying to edit a report query it fails consistently (depending on query) with popup windows "Problem Occurred" with following message:
"An internal error occurred during: "XtextReconcilerJob"."
"java.lang.IllegalArgumentException: SelectQuery.op does not exist"
This only seems to happen with queries with combination of with clause and union as far as I can tell.
This can be reproduced with following simple example query on empty report (detail section no fields):
with data1 as (select 1 as value from dual),
data2 as (select 2 as value from dual)
select value from data1
union all
select value from data2
For the rest the report seems to run fine with preview working and generated report (.jasper) working.
I have tested with version jaspersoft studio 6.6.0 on laptop, jaspersoft studio 6.16.0 on same laptop and reproduced issue on different machines with jaspersoft studio 6.6.0
| Attachment | Size |
|---|---|
 xtext_error_jaspersoft_studio_6.6.0.bmp | 275.19 KB |
6 Comments:
It happens identically with postgresql (org.postgresql.Driver)
Hi using your query sample as starting point, I was able to reproduce the bug.
I investigated a bit on the generic issue(s) related to this XtextReconcilerJob thing.
Apparently there are already some opened bugs about similar problems:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=471849
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=413290
- https://github.com/eclipse/xtext-core/issues/773
- https://www.eclipse.org/forums/index.php?SQ=0&t=search&srch=XtextReconci...
In my first test I fixed our grammar in the WITH clause (the ParserRule WithQuery) adding the proper part not covering multiple items comma separated.
Even if from initial tests the error appeared fixed, when I started writing strange chars like \ or [ I was still raising the exception.
Apparently the problem as described in one of the references I found, is caused also by the usage of a ParserRule without assignment.
So I switched from DBID to DbObjectName one.
Right now, after re-generating the grammar it appears to be working.
That said, I'm not sure it's a final solution, also because it appears there is this inner Xtext issue (or more than one?!).
For sure instead of an exception, I would rather want to see some error marker in the editor telling me that something is wrong with my query (and grammar).
Just in case let me know if you can find additional scenarios that triggers this XtextReconcilerJob exception.
Also if there are any noticeable side-effects caused by this fix.
Thanks in advance!
Best regards,
Massimo.
P.S: the fix will be part of then next upcoming version
how to hide the popup windows "Problem Occurred"?