Github user TomasHofman commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
No, if `lockAcquisitionTimeout` is set to -1, it will wait 2 seconds, and
then retry the lock. I don't see what you are referring to.
There are two situations:
*
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
My point is. -1 is forever. If you set it forever it will be failing at 2
seconds.
What happens if you just configure the system at 2 seconds instead of -1?
---
Github user TomasHofman commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
@jbertram @franz1981 we could really use this...
---
Github user TomasHofman commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
Everything looks OK now, so I will wait for merging and porting to 2.6.x,
and then will update downstream PR for 2.6.3.jbossorg-x (will cherry-pick -x
from 2.6.x port).
---
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
The PR build is automated. You just need to update your branch so it knows
to test it again. A couple of git commands aren't really much harder than a
GitHub comment.
---
Github user TomasHofman commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
No automation? Thanks, will do. :)
---
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
@TomasHofman you'll need to update your branch somehow to force the PR
build to run again. I recommend something like `git commit --amend` & `push
-f`.
---
Github user TomasHofman commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
Retest this please.
---
Github user mnovak1 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2287
@TomasHofman Could you update the state of this PR, please?
---
