JT400 tests can not be run in parallel #6018 #6019
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #6018
Better locking mechanism is iused.
1 file for locking has to be provided in the integrated file system. Each execution then asks for the lock of that file using JTOpen API.
Instruction of how to create such file are added into the readme.adoc.
Investigation of parallel executions revealed, that there might be a problem in jt400 regarding release of the connections.
Even if the route
is stopped, access to the queue is still blocked (about 20-30 seconds) and throws
CPF2451 Message queue REPLYMSGQ is allocated to another job
.Therefore I'm adding a clear of the queues to the
@BeforeAll
method with await to wait for the lock to go away.(Until a proper fix is implemented)