[
https://issues.apache.org/jira/browse/ARTEMIS-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-5047:
------------------------------------
Description:
After upgrading from version 2.23.1 to 2.33.0 the system has started to fail
due to a lock loss. This issue was not present in the previous version and has
only surfaced after the upgrade.
I have seen a similar issue.
{noformat}
(AuditLogger_impl.java:2843) - AMQ601767: STOMP connection c3e5b678 for user
[email protected]:64628 created FINEST|6324/0|Service
com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|22 Aug 2024 01:03:51,813 WARN
[Thread-0 (ActiveMQ-scheduled-threads)] (FileLockNodeManager.java:557) - Lost
the lock according to the monitor, notifying listeners FINEST|6324/0|Service
com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|22 Aug 2024 01:03:51,813 ERROR
[Thread-0 (ActiveMQ-scheduled-threads)] (ActiveMQServerLogger_impl.java:805) -
AMQ222010: Critical IO Error, shutting down the server. file=Lost NodeManager
lock, message=NULL FINEST|6324/0|Service
com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|java.io.IOException: lost
lock{noformat}
was:
After upgrading from version 2.23.1 to 2.33.0, the system has started to fail
due to a lock loss. This issue was not present in the previous version and has
only surfaced after the upgrade.
I have seen a similar issue.
{code:java}
(AuditLogger_impl.java:2843) - AMQ601767: STOMP connection c3e5b678 for user
[email protected]:64628 created FINEST|6324/0|Service
com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|22 Aug 2024 01:03:51,813 WARN
[Thread-0 (ActiveMQ-scheduled-threads)] (FileLockNodeManager.java:557) - Lost
the lock according to the monitor, notifying listeners FINEST|6324/0|Service
com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|22 Aug 2024 01:03:51,813 ERROR
[Thread-0 (ActiveMQ-scheduled-threads)] (ActiveMQServerLogger_impl.java:805) -
AMQ222010: Critical IO Error, shutting down the server. file=Lost NodeManager
lock, message=NULL FINEST|6324/0|Service
com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|java.io.IOException: lost lock
{code}
> Lost the lock according to the monitor, notifying listeners
> -----------------------------------------------------------
>
> Key: ARTEMIS-5047
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5047
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.33.0, 2.37.0
> Environment: * *Storage Type:* SMB share hosted on AWS FSxN
> * *Current Version:* NetApp Release 9.14.1P5
> * *Affected Version:* 2.33.0 / 2.37.0
> * *Previous Version:* 2.23.1 (issue not observed)
> Reporter: Juan
> Priority: Major
>
> After upgrading from version 2.23.1 to 2.33.0 the system has started to fail
> due to a lock loss. This issue was not present in the previous version and
> has only surfaced after the upgrade.
> I have seen a similar issue.
> {noformat}
> (AuditLogger_impl.java:2843) - AMQ601767: STOMP connection c3e5b678 for user
> [email protected]:64628 created FINEST|6324/0|Service
> com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|22 Aug 2024 01:03:51,813
> WARN [Thread-0 (ActiveMQ-scheduled-threads)] (FileLockNodeManager.java:557) -
> Lost the lock according to the monitor, notifying listeners
> FINEST|6324/0|Service com.docshifter.mq.DocShifterMQ|24-08-22 01:03:51|22 Aug
> 2024 01:03:51,813 ERROR [Thread-0 (ActiveMQ-scheduled-threads)]
> (ActiveMQServerLogger_impl.java:805) - AMQ222010: Critical IO Error, shutting
> down the server. file=Lost NodeManager lock, message=NULL
> FINEST|6324/0|Service com.docshifter.mq.DocShifterMQ|24-08-22
> 01:03:51|java.io.IOException: lost lock{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
