You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Archibald <ar...@gmx.net> on 2018/01/16 14:05:37 UTC
[ARTEMIS] ActiveMQScheduledLeaseLock warning is written
periodically in broker log since 2.4.0
Hi, I read ongoing warnings in the broker's log since 2.4.0 using a
persistent message store backed by oracle:
07:32:28,205 WARN
[org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
live lock renew period lasted 4002 ms instead of 4000 ms
07:32:32,206 WARN
[org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
live lock renew period lasted 4001 ms instead of 4000 ms
07:32:44,208 WARN
[org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
live lock renew period lasted 4002 ms instead of 4000 ms
07:32:48,211 WARN
[org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
live lock renew period lasted 4001 ms instead of 4000 ms
...
What is it about?
Br, Archibald
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: [ARTEMIS] ActiveMQScheduledLeaseLock warning is written
periodically in broker log since 2.4.0
Posted by nigro_franz <ni...@gmail.com>.
Hi!
when is used a JDBC Journal the JDBC Node Manager will use an optimistic
Lock with timeout (similar to the ActiveMQ's
http://activemq.apache.org/maven/apidocs/org/apache/activemq/store/jdbc/LeaseDatabaseLocker.html)
to maintain the ownership of the Journal.
This lock periodically renew the lease on the Journal and warn if the renew
operation will take more than what is expected (4000 ms I suppose) to be
triggered/happen.
The reasons could be very different including DBMS latencies/heavy GC
pauses/too many threads vs CPU cores.
More infos are here:
https://activemq.apache.org/artemis/docs/latest/persistence.html on
dbc-lock-renew-period field.
Cheers,
Franz
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: [ARTEMIS] ActiveMQScheduledLeaseLock warning is written
periodically in broker log since 2.4.0
Posted by Archibald <ar...@gmx.net>.
Awesome, thank you!
Br, Archibald
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: [ARTEMIS] ActiveMQScheduledLeaseLock warning is written
periodically in broker log since 2.4.0
Posted by Clebert Suconic <cl...@gmail.com>.
I fixed this yesterday in my PR for database. It’s not Merged yet.
On Tue, Jan 16, 2018 at 9:05 AM Archibald <ar...@gmx.net> wrote:
> Hi, I read ongoing warnings in the broker's log since 2.4.0 using a
> persistent message store backed by oracle:
>
> 07:32:28,205 WARN
>
> [org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
> live lock renew period lasted 4002 ms instead of 4000 ms
> 07:32:32,206 WARN
>
> [org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
> live lock renew period lasted 4001 ms instead of 4000 ms
> 07:32:44,208 WARN
>
> [org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
> live lock renew period lasted 4002 ms instead of 4000 ms
> 07:32:48,211 WARN
>
> [org.apache.activemq.artemis.core.server.impl.jdbc.ActiveMQScheduledLeaseLock]
> live lock renew period lasted 4001 ms instead of 4000 ms
> ...
>
> What is it about?
>
> Br, Archibald
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
--
Clebert Suconic