Bug 972623 - jbpm-human-task-core tests fail on mssql due to: null id in org.jbpm.services.task.impl.model.TaskImpl entry
Summary: jbpm-human-task-core tests fail on mssql due to: null id in org.jbpm.services...
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core   
(Show other bugs)
Version: unspecified
Hardware: Unspecified Unspecified
Target Milestone: ER1
: 6.0.0
Assignee: Mauricio Salatino
QA Contact: Jiri Svitak
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-10 08:48 UTC by Jiri Svitak
Modified: 2015-06-02 01:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-08-06 20:10:54 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
jenkins log (14.45 KB, text/plain)
2013-06-10 08:48 UTC, Jiri Svitak
no flags Details

Description Jiri Svitak 2013-06-10 08:48:05 UTC
Created attachment 759112 [details]
jenkins log

jbpm-human-task-core tests fail on mssql2008R2 and mssql2012 due to:

Caused by: org.hibernate.AssertionFailure: null id in org.jbpm.services.task.impl.model.TaskImpl entry (don't flush the Session after an exception occurs)

See the whole attached stack trace from arbitrarily chosen test in jbpm-human-task-core. You can also go through the following or other jenkins build results:



Comment 1 Mauricio Salatino 2013-06-24 15:06:55 UTC
I don't know how to reproduce the issue. Can you make sure that you have the correct MSSQL drivers for that database version? For this case I would recommend to see if the tests works at least with one version of MS SQL

Comment 2 Jiri Svitak 2013-06-25 07:20:29 UTC
yes, I am sure that I use correct drivers. Other jBPM modules besides human-task work the same drivers fine, see the whole db matrix:

Have you looked at the Jenkins job results? Have you analyzed the stack traces? Please open the the attached links to Jenkins.

If the available logs and resources are insufficient, you can reproduce the problem again - either configure your local test suite to use MSSQL or use Jenkins job:
You can also look how this 'single' job is executed and use its configuration Groovy script to run the job on local computer.

Please, do not ignore these bugs and set them to MODIFIED status only if the issue is resolved. Thanks.

Comment 4 Jiri Svitak 2013-08-08 16:12:44 UTC
Verified in 6.0.x product branch:


Cannot set the mandatory target milestone, because:
1.) there are no libraries of the product, which the verification can be done against
2.) the job is configured to run continuously against 6.0.x product branch

(Using ER1 for this.)

Comment 8 Jiri Svitak 2014-01-03 17:23:45 UTC
commit in 6.0.x branch:

Comment 9 Lukáš Petrovický 2014-02-07 16:15:13 UTC
This BZ has been part of the 6.0.0 stream.

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