JiriOndrusek opened a new pull request, #6019: URL: https://github.com/apache/camel-quarkus/pull/6019
fixes https://github.com/apache/camel-quarkus/issues/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 ``` from("jt400://username:password@localhost/qsys.lib/qusrsys.lib/myq.msgq?sendingReply=true") .choice() .when(header(Jt400Constants.MESSAGE_TYPE).isEqualTo(AS400Message.INQUIRY)) .process((exchange) -> { String reply = // insert reply logic here exchange.getIn().setBody(reply); }) .to("jt400://username:password@localhost/qsys.lib/qusrsys.lib/myq.msgq"); ``` is stopped, access to the route 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) <!-- Uncomment and fill this section if your PR is not trivial [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #. [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request. [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
