You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/01/10 16:50:03 UTC
[jira] [Resolved] (ARTEMIS-1594) Artemis excessively logs
"AMQ222165: No Dead Letter Address" and "AMQ222166: No Expiry Address"
[ https://issues.apache.org/jira/browse/ARTEMIS-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-1594.
-------------------------------------
Resolution: Fixed
Assignee: Justin Bertram
Fix Version/s: 2.5.0
> Artemis excessively logs "AMQ222165: No Dead Letter Address" and "AMQ222166: No Expiry Address"
> -----------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1594
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1594
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.4.0
> Environment: Artemis 2.5.0-SNAPSHOT
> Reporter: Johan Stenberg
> Assignee: Justin Bertram
> Priority: Minor
> Fix For: 2.5.0
>
> Attachments: ArtemisTest.java
>
>
> # When starting clustered Artemis instances the following Warnings are logged:
> {noformat}
> Jan 09, 2018 12:53:00 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222165: No Dead Letter Address configured for queue $.artemis.internal.sf.cluster.a46132db-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:00 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222166: No Expiry Address configured for queue $.artemis.internal.sf.cluster.a46132db-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:01 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222165: No Dead Letter Address configured for queue $.artemis.internal.sf.cluster.a401d4c7-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:01 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222166: No Expiry Address configured for queue $.artemis.internal.sf.cluster.a401d4c7-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:01 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222165: No Dead Letter Address configured for queue notif.a4c7e3f8-f533-11e7-ae3c-54524514640f.ActiveMQServerImpl_serverUUID=a401d4c7-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:01 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222165: No Dead Letter Address configured for queue notif.a4c7e3f7-f533-11e7-ae3c-54524514640f.ActiveMQServerImpl_serverUUID=a46132db-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:01 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222166: No Expiry Address configured for queue notif.a4c7e3f8-f533-11e7-ae3c-54524514640f.ActiveMQServerImpl_serverUUID=a401d4c7-f533-11e7-ae3c-54524514640f in AddressSettings
> Jan 09, 2018 12:53:01 PM org.apache.activemq.artemis.core.server.impl.QueueImpl checkDeadLetterAddressAndExpiryAddress
> WARN: AMQ222166: No Expiry Address configured for queue notif.a4c7e3f7-f533-11e7-ae3c-54524514640f.ActiveMQServerImpl_serverUUID=a46132db-f533-11e7-ae3c-54524514640f in AddressSettings
> {noformat}
> Since these are warnings about Artemis internal queues and - I guess - no expiry address and no DLQ are configured on purpose, they have no value to anyone as an Administrator can do nothing about them.
> # Each time a modification of the AddressSettingsRepository is performed the check for ExpiryAddresses and DLQs is performed again on ALL existing queues and the AMQ222165/AMQ222166 warnings are logged again for all queues. In our case when a client logs-in we configure new address settings for this client (like a namespace where that client can create queues freely). So each time a new client logs in on an instance Artemis again logs warnings for all existing queues without expiry address/DLQ.
> Therefore I would suggest:
> # for Artemis internal queues these warnings should not be logged at all or at debug level
> # for custom queues the warning should only be logged once on creation and not on each a modification of the AddressSettingsRepository occurs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)