Bug 818936
| Summary: | Human Task with potential owner who is not known to the HT service is not written to database | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Radovan Synek <rsynek> | ||||||||
| Component: | jBPM 5 | Assignee: | Marco Rietveld <mrietvel> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Radovan Synek <rsynek> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | BRMS 5.3.0.GA | CC: | brms-jira, jlocker, mrietvel, paradhya, smcgowan | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | https://issues.jboss.org/browse/JBPM-3652 | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-05-22 14:36:26 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 582111 [details]
server log
Which version of HSQLDB is being used? The internets seem to indicate that there's a well known bug in HSQLDB batching: http://forum.springsource.org/archive/index.php/t-28645.html http://stackoverflow.com/questions/7526729/genericjdbcexception-in-hsql http://sourceforge.net/tracker/?func=detail&atid=378131&aid=1407528&group_id=23316 I can't tell whether or not this was ever fixed in HSQLDB (the above mentioned bug was rejected aka set to "invalid"). It would be great if you could replicate this bug on another database, maybe H2? Created attachment 582670 [details]
H2 server log
(In reply to comment #2) > Which version of HSQLDB is being used? > > The internets seem to indicate that there's a well known bug in HSQLDB > batching: > > http://forum.springsource.org/archive/index.php/t-28645.html > http://stackoverflow.com/questions/7526729/genericjdbcexception-in-hsql > http://sourceforge.net/tracker/?func=detail&atid=378131&aid=1407528&group_id=23316 > > I can't tell whether or not this was ever fixed in HSQLDB (the above mentioned > bug was rejected aka set to "invalid"). > > It would be great if you could replicate this bug on another database, maybe > H2? It seems these issues are about generic exception without the detail information about the cause when batch execution is enabled. But I have tried once more with H2 database and the problem still occurs. Here is the new log file https://bugzilla.redhat.com/attachment.cgi?id=582670 This looks like added functionality, and given the deadlines/timeframe and other prio's/bugs, I'm not sure there's time to implement the solution proposed. Will defer it to next release. See the discussion in BZ 800514 for more information about this issue. *** This bug has been marked as a duplicate of bug 800514 *** |
Created attachment 582110 [details] process definition Description of problem: Simple process definition: start->human task->end with potential owner, that is not known to the HT service is run in the JBPM Console. When the process instance starts, exception occurs in the server.log (see an attachment). There is a root cause: java.sql.SQLException: Integrity constraint violation - no parent FK27A9A59E619A0 table: TASK in statement [update Task set allowedToDelegate=?, taskInitiator_id=?, priority=?, activationTime=?, actualOwner_id=?, createdBy_id=?, createdOn=?, documentAccessType=?, documentContentId=?, documentType=?, expirationTime=?, faultAccessType=?, faultContentId=?, faultName=?, faultType=?, outputAccessType=?, outputContentId=?, outputType=?, parentId=?, previousStatus=?, processId=?, processInstanceId=?, processSessionId=?, skipable=?, status=?, workItemId=?, OPTLOCK=? where id=? and OPTLOCK=?] From my point of view: 1. The task cannot be seen by unknownUser - that's right, it should not be. 2. There is the process instance waiting for the task completion. The only way is to terminate this process instance -> the user can lost his data. 3. There should be an option to assign the task to other user which is known to the HT service (for example by some Task Server admin). But this is not possible - the task is not stored in database and therefore, it can't be seen by any user. 4. If there is more than one potential owner specified in the process definition and only one is unknown to the HT service, still even the known owners are unable to access the task. Version-Release number of selected component (if applicable): BRMS 5.3.0.ER6 Steps to Reproduce: 1. run the attached BPMN2 process (assuming the "unknownUser" is not defined in the running task service) in JBPM Console 2. see server log for the exception Expected results: No org.hibernate.exception.GenericJDBCException or java.sql.SQLException. The task should be stored in database, but not visible to unknown user.