Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Obsolete
Priority: Minor
Fix Version/s: None
Affects Version/s: 7.4.0.GA
Component/s: Kie-Server
Labels:
None
Environment:

OCP running in AWS with HA authoring environment deployed via template

Steps to Reproduce:

Hide

1. Deploy authoring environment using HA template
2. Deploy mortgage process example
3. Create process, see it it get instance ID '1'
4. Stop OCP
5. Start OCP
6. Kick off a new process instance for mortgage example, see it gets '1' again as the ID.

Show
1. Deploy authoring environment using HA template 2. Deploy mortgage process example 3. Create process, see it it get instance ID '1' 4. Stop OCP 5. Start OCP 6. Kick off a new process instance for mortgage example, see it gets '1' again as the ID.

SFDC Cases Counter:
SFDC Cases Links:

Description

I run an OCP environment in AWS that I use for demos and to save money I stop the environment when I'm not using it and then start it again when needed.

I'm finding that when I do this and submit new processes after the restart the process instance IDs get reused as they start from 1 again like they are not persisted. Since I am using the HA authoring template which does deploy a database my expectation is that this process instance counter should survive restarts.

Reusing the instance ID causes all sorts of issues in BC as it displays information from the original process with that instance ID rather then the current one.

I am testing this with the mortgage process sample.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

Screenshot from 2019-07-30 09-03-40.png
59 kB
2019/07/30 9:11 AM

Activity

People

Assignee:: Filippe Spolti

Reporter:: Gerald Nunn

Tester:: Karel Suta

QA Contact:: Karel Suta

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2019/07/30 9:11 AM

Updated:: 2021/10/24 5:59 AM

Resolved:: 2021/09/30 6:04 PM