[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268680#comment-17268680 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit c2c637407ec28ce4b995f1681fa083de67eaea4b in activemq-artemis's branch refs/heads/master from gtully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c2c6374 ] ARTEMIS-2937 - tidy up shutdown, resolve intermittent failure in org.apache.activemq.artemis.tests.integration.amqp.connect.AMQPReplicaTest#testReplicaCatchupOnQueueCreates > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224994#comment-17224994 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 648340a864d95652c0e8fe030705f51114116962 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=648340a ] ARTEMIS-2969 / ARTEMIS-2937 Making sure consumers are cleaned after failures and reconnects > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224867#comment-17224867 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 7a435a944c12dfa6cab1fab3f9f1faed47a2859f in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7a435a9 ] ARTEMIS-2969 / ARTEMIS-2937 should set connecting = false when maxRetry is reached > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224804#comment-17224804 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit fa4064cfd784e93a02a3905b16b8c9302fe105fc in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=fa4064c ] ARTEMIS-2969 / ARTEMIS-2937 RedoConnection should call protonRemotingConnection.destroy Instead of calling destroy, redo was closing the Netty connection directly leaving the job of destroy delayed until TTL > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224708#comment-17224708 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit c0b12b14c88995a1ca2d3e2c2220aeca220d94b7 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c0b12b1 ] ARTEMIS-2969 / ARTEMIS-2937 Controlling connecting state on AMQP Broker Connection - Fixed an issue where I needed to set connection to null after closing it - Added more tests on QpidDispatchPeerTest (tests i would have done manually, and reproduced a few issues along the way) > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223660#comment-17223660 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit f3dde91b911e73cc9733a06fe00a72ec7d2249c0 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f3dde91 ] ARTEMIS-2969 / ARTEMIS-2937 Dealing with instant disconnects on amqp broker connections > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223625#comment-17223625 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit dff2ed36383f1e52304eff2705bf43e01e3c3f10 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=dff2ed3 ] ARTEMIS-2937 Implementing skip create and skip delete on Mirror Source > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223583#comment-17223583 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 7a5f325b721fcbb7169cca1a0d0dc5de9f6d06cc in activemq-artemis's branch refs/heads/master from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7a5f325 ] ARTEMIS-2937: remove a couple of unecessary lines for alt stores, left over by mistake (c error) > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223323#comment-17223323 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 9b0f7605cb4bb768cd098e127644eda5b347cd28 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9b0f760 ] ARTEMIS-2969 / ARTEMIS-2937 Dealing with Connection Timeout properly on AMQP Broker Connections > 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: 35h 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223160#comment-17223160 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 1af8be353f6072efb317a438d7f3defb93ada46c in activemq-artemis's branch refs/heads/master from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1af8be3 ] ARTEMIS-2937: use more realistic key/truststore and client+broker setup in SSL example, remove non-SSL acceptors > 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: 35h 10m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223153#comment-17223153 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit dc7eb5c23db356e9f7bbdc66d68240efafb19f6a in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=dc7eb5c ] ARTEMIS-2937 Broker connection improvements - Adding a paragraph about addressing and distinct queue names - Renaming match on peers, senders and receivers as "address-match" - Changing qpid dispatch test to use a single listener - Fixing reconnect attemps message > 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: 34h 40m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222953#comment-17222953 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 9335cd83ed0b2bdc12d72d24e88eb67cf3ddf7d1 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9335cd8 ] ARTEMIS-2937 Changing BrokerConnection SSL example to also use SSL on the client > 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: 34h 10m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222952#comment-17222952 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 753dac47d8f407f94f672718bb416c6f5385b0de in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=753dac4 ] ARTEMIS-2937 Cleanup on tests > 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: 34h 10m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222894#comment-17222894 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit ef5d257f3fbac41d6958d5bd6ef97ce8799024c1 in activemq-artemis's branch refs/heads/master from Robbie Gemmell [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ef5d257 ] ARTEMIS-2937: improve the docs, particularly around use of 'peer' config to waypoint for Dispatch > 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: 33h 50m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17222389#comment-17222389 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit bf52134dc0bb0ebefbe6228b26ae5326a6b2baec in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=bf52134 ] ARTEMIS-2937 Fixing Tests and some review > 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: 32h > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1742#comment-1742 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 05d5db83a406462da5b88bf140b1985c4596b659 in activemq-artemis's branch refs/heads/master from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=05d5db8 ] Merge pull request #3316 from clebertsuconic/ARTEMIS-2937 ARTEMIS-2937 Broker Connections > 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: 27h 40m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1740#comment-1740 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 8499eac76c2044bfa52a65b9ada15581cd2efb7a in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8499eac ] ARTEMIS-2937 Server Side AMQP Connectivity with options to transfer queues or replicate data > 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: 27.5h > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1743#comment-1743 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 05d5db83a406462da5b88bf140b1985c4596b659 in activemq-artemis's branch refs/heads/master from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=05d5db8 ] Merge pull request #3316 from clebertsuconic/ARTEMIS-2937 ARTEMIS-2937 Broker Connections > 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: 27h 40m > 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 > > 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 > it would also be possible to use 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)
[jira] [Commented] (ARTEMIS-2937) AMQP Server Connectivity
[ https://issues.apache.org/jira/browse/ARTEMIS-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1741#comment-1741 ] ASF subversion and git services commented on ARTEMIS-2937: -- Commit 12280cdaaa313a01ade5b5cd41134a1d3b0abbb6 in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=12280cd ] ARTEMIS-2937 DOCS & Examples on AMQP Broker Connection > 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: 27h 40m > 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 > > 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 > it would also be possible to use 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)
