Bug 1315242 - DB2 9.7 Can't get metadata on specified data set: jbpmProcessInstances
Summary: DB2 9.7 Can't get metadata on specified data set: jbpmProcessInstances
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: CR2
: 6.2.2
Assignee: David Gutierrez
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks: 1309326
TreeView+ depends on / blocked
 
Reported: 2016-03-07 10:49 UTC by Tibor Zimanyi
Modified: 2020-03-27 20:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:10:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Server.log (195.86 KB, text/plain)
2016-03-07 10:49 UTC, Tibor Zimanyi
no flags Details

Description Tibor Zimanyi 2016-03-07 10:49:28 UTC
Created attachment 1133709 [details]
Server.log

Description of problem:

Using process instance perspective with DB2 9.7 database fails on SqlSyntaxErrorException. This is the same bug as already reported here [1], but this is the first time it occured on 6.2 product. 

[1] https://issues.jboss.org/browse/DASHBUILDE-96

We should decide if we want to backport fix from later versions or if we only document this for 6.2 and leave the fix for later. 

Attaching server.log

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

Comment 2 Maciej Swiderski 2016-03-07 10:57:00 UTC
Neus, could you please take a look at this as you're most likely are more up to date with this part.

Comment 3 Neus Miras 2016-03-07 11:24:32 UTC
In the 6.3 version:
The queries over the console have been updated to work fine over all supported databases. 

The dashbuilder have included the fix for this issue in the 0.4.x
https://github.com/dashbuilder/dashbuilder/commit/fb496fec66d871b3d0763344bcb646ee11ddce95 

And the jbpm-console-ng queries have been updated in this PR waiting to be merge
https://github.com/droolsjbpm/jbpm-console-ng/pull/353 at 6.4.x

In the previous version (6.2)
Now, we have to decide if the fix, have to be ported to 6.2. In that sense, David can answer better the question of if dashbuilder can take this fix for previous version of dashbuilder.

In jira it's reported at:
https://issues.jboss.org/browse/JBPM-4943

Comment 4 Neus Miras 2016-03-07 11:29:10 UTC
David can you take a look on the possibility to take the LIMIT issue fix to previous version?

Comment 5 David Gutierrez 2016-03-07 12:01:08 UTC
Yes, I think the issue can be backported, Although I'd need look to into it thoroughly, to asses the impact. 

@Tibor can you confirm a backport is needed?

Comment 6 Tibor Zimanyi 2016-03-07 12:10:45 UTC
After discussion with David - we agreed to backport this so we get rid of all DB2 issues related to this case and I agree with this.

Comment 8 David Gutierrez 2016-03-11 18:33:18 UTC
The fix https://issues.jboss.org/browse/DASHBUILDE-96 has been backported to the 6.2 product branch (i.e: dashbuilder 0.3.x):

https://github.com/dashbuilder/dashbuilder/commit/c92bfbdd3a7bdd9fdda9f3b7067ca282789483e6

Comment 9 Jan Hrcek 2016-03-23 06:18:07 UTC
Working fine now. Verified with BPM Suite 6.2.2 CR2


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