Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1057195

Summary:

CR1 updated to mortgage-demo (example app) jboss-mortgage-client.jar fails

Product:

[Retired] JBoss BPMS Platform 6

Reporter:

Eric D. Schabell <eschabel>

Component:

Business Central

Assignee:

Kris Verlaenen <kverlaen>

Status:

CLOSED NOTABUG

QA Contact:

Marek Baluch <mbaluch>

Severity:

medium

Docs Contact:

Priority:

high

Version:

6.0.0

CC:

eschabel, kverlaen, lpetrovi, mrietvel

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Mac OS

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-01-23 19:45:17 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:

Description	Flags
server log with errors	none

Description Eric D. Schabell 2014-01-23 15:46:22 UTC

Created attachment 854453 [details]
server log with errors

Description of problem:
Setup bpms-mortgage-demo project based on CR1 (https://github.com/eschabell/bpms-mortgage-demo), run server, login, build & deploy project, run jar in support directory (java -jar jboss-mortgage-client.jar erics bpmsuite), log shows several instances being inserted before it fails with erorrs, attached server.log.

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

How reproducible:
see above

Steps to Reproduce:
1. see above
2.
3.

Actual results:
client jar fails to insert more than a few instances of process before failure.

Expected results:
client jar should insert 16 process instances and exit without errors.

Additional info:
Using latest version of example app installed in server for this demo.

Comment 2 Lukáš Petrovický 2014-01-23 15:52:09 UTC

Did you have the security policy enabled? If so, could you disable it and try again?

Comment 3 Eric D. Schabell 2014-01-23 15:56:47 UTC

Setup my demo, it is all turned off by default.

Comment 4 Marco Rietveld 2014-01-23 19:45:17 UTC

Maciej and I figured out that the problem is being caused by the following lines in the support/1000_jbpm_demo_h2.sql import script (https://github.com/eschabell/bpms-mortgage-demo/blob/v0.5/support/1000_jbpm_demo_h2.sql): 

insert into bamtasksummary(pk,taskid,taskname,createddate,startdate,userid,processinstanceid,enddate,duration,status)  values (2, 1000, 'Task 1', PARSEDATETIME('16/12/2012 20:34', 'd/MM/yyyy HH:mm', 'en', 'GMT'), PARSEDATETIME('09/01/2013 00:25', 'd/MM/yyyy HH:mm', 'en', 'GMT'), 'Frank T.', 100, null, null, 'Claim');

These lines should also specify a "version" value. Because no version column value is specified, the column contains a null value which hibernate does not expect. 

The fix for this is to modify those lines so that they insert a valid value ("1" for example) for the "version" field. 

To be clear, this fix would be for the SQL script -- this bug is NOT caused by anything on the BPMS side. For that reason, I'm closing this as NOTABUG.

Comment 5 Marco Rietveld 2014-01-23 19:47:20 UTC

I'll be submitting pull requests to eric's demo and to the original github repo to fix the problem.