Bug 1327610 - Kie server: Concurrent call fails when creating container
Summary: Kie server: Concurrent call fails when creating container
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Kie-Server
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR1
: 6.3.0
Assignee: Karel Suta
QA Contact: Karel Suta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 13:19 UTC by Karel Suta
Modified: 2020-03-27 20:01 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
stacktrace (2.85 KB, text/plain)
2016-04-15 13:19 UTC, Karel Suta
no flags Details

Description Karel Suta 2016-04-15 13:19:56 UTC
Created attachment 1147640 [details]
stacktrace

Description of problem:
If Kie server gets a request concerning container while this container is being created then Kie server throws exception shown in attachment.

It is caused by creating conversation ID header, which contains also release id of container, for any request concerning such container. If container is being created at that moment then release id isn't set yet, causing this issue.

Solution could be to return empty conversation ID(if wasn't set in request) until container is fully initialized - is in started state.

For more info see [1].


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

How reproducible:
See test in [2]

Steps to Reproduce:
1.
2.
3.

Actual results:
Kie server throws exception when concurrent call is done.

Expected results:
Kie server should correctly return response.

Additional info:


[1] https://issues.jboss.org/browse/DROOLS-1128
[2] https://github.com/droolsjbpm/droolsjbpm-integration/pull/432

Comment 2 Maciej Swiderski 2016-04-15 15:29:10 UTC
this has been already fixed (by Karel - thanks a lot) and merged into master:
https://github.com/droolsjbpm/droolsjbpm-integration/commit/20a9aac9a45abbc1e83cb0c42907bd29f5b8e6e7

actually this is rather specific use case (though still might happen) that operations are invoked concurrently when container is being started. Usually this operation is fast but first attempts might take more time - when downloading maven dependencies etc.

Comment 4 Karel Suta 2016-04-28 09:02:06 UTC
Verified in 6.3.0CR1


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