Hi,
After upgrading to Artemis 2.41.0 (includes ARTEMIS-5428), shutdown
produces random WARNs due to a race between persistence shutdown and
STOMP/notification cleanup. Examples:
STOMP cleanup after IDGenerator stopped:
2025-09-03T07:27:19.525 | WARN | server | AMQ222069: error cleaning up
stomp connection
java.lang.RuntimeException: AMQ229257: IDGenerator has been stopped
at ... BatchingIDGenerator.generateID
at ... ServerSessionImpl.doRollback
at ... StompProtocolManager.cleanup
Notification dispatch after IDGenerator stopped:
2025-08-31T01:31:35.485 | WARN | server | AMQ222230: Failed to send
notification
java.lang.RuntimeException: AMQ229257: IDGenerator has been stopped
at ... BatchingIDGenerator.generateID
at ... ManagementServiceImpl.sendNotification
at ... ServerSessionImpl.sendSessionNotification
These warnings are harmless (occur only during teardown)
Even when WARNs appear, shutdown continues cleanly. Example with WARN:
2025-09-03T07:27:19.484 | DEBUG | ServiceManagerImpl | Stopping
activeMQManager now ...
2025-09-03T07:27:19.486 | DEBUG | ProducerTargetSource | Destroying
instance of bean 'activeMQProducerTarget'
2025-09-03T07:27:19.494 | DEBUG | SessionTargetSource | Destroying instance
of bean 'activeMQSessionTarget'
2025-09-03T07:27:19.525 | WARN | server | AMQ222069: error cleaning up
stomp connection
(stack trace: IDGenerator stopped)
2025-09-03T07:27:19.666 | DEBUG | ServiceManagerImpl | Update state for
activeMQManager to stopped.
2025-09-03T07:27:19.666 | INFO | ServerStatus | activeMQManager is stopped
How should I mitigate this warnings?
Should i stop RemotingService and ManagementService Notification before
stopping ActiveMQ server ?
*RegardsDharmashivam Muthuraman*
