[
https://issues.apache.org/jira/browse/ARTEMIS-2937?focusedWorklogId=503682&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-503682
]
ASF GitHub Bot logged work on ARTEMIS-2937:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Oct/20 11:41
Start Date: 22/Oct/20 11:41
Worklog Time Spent: 10m
Work Description: gemmellr commented on a change in pull request #3294:
URL: https://github.com/apache/activemq-artemis/pull/3294#discussion_r510092582
##########
File path:
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/logger/ActiveMQAMQPProtocolLogger.java
##########
@@ -48,4 +48,16 @@
@LogMessage(level = Logger.Level.WARN)
@Message(id = 111000, value = "Scheduled task can't be removed from
scheduledPool.", format = Message.Format.MESSAGE_FORMAT)
void cantRemovingScheduledTask();
+
+ @LogMessage(level = Logger.Level.WARN)
+ @Message(id = 111001, value =
"\n*******************************************************************************************************************************"
+
Review comment:
Ok. I was also meaningf or the info one below. Logging all that after
each interval seems like its going to be a bit spammy.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 503682)
Time Spent: 16h 20m (was: 16h 10m)
> AMQP Server Connectivity
> ------------------------
>
> Key: ARTEMIS-2937
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2937
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: AMQP
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 16h 20m
> Remaining Estimate: 0h
>
> This feature adds server side connectivity.
>
> It is possible to link two brokers directly using AMQP with this feature, and
> have a Queue transferring messages to another broker directly.
>
> For this we would have options called <sender and <receiver
>
>
> it would also be possible to use qpid-dispatch as an intermediary between
> clients and the brokers (or eventually between brokers), on that case the
> option will be <peer
>
> it would also be possible to use <mirror with a few option to replicate data
> between two brokers, bringing the possibility of using it for Disaster &
> Recovery and Failover.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
