Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(QE) [7.44.x] [JBPM-9447] No session found for context in case SLA on user task is violated #1788

Merged
merged 1 commit into from Nov 10, 2020

Conversation

elguardian
Copy link
Member

added timer name to configure SLA in order to generate a proper job handle id.
Otherwise it will registered twice: once the node is reached and once the node is unmarshalled

Jira https://issues.redhat.com/browse/RHPAM-3233
cherry pick from
885d1be

…violated

added timer name to configure SLA in order to generate a proper job handle id.
Otherwise it will registered twice: once the node is reached and once the node is unmarshalled
@elguardian
Copy link
Member Author

Jenkins retest this please.

@sonarcloud
Copy link

sonarcloud bot commented Nov 2, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

warning The version of Java (1.8.0_202) you have used to run this analysis is deprecated and we will stop accepting it accepting it soon.Please update to at least Java 11.
Read more here

@elguardian elguardian merged commit f248ab5 into kiegroup:7.44.x Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant