[jira] [Updated] (ARTEMIS-4902) Downstream federation example not compliant with xsd
[
https://issues.apache.org/jira/browse/ARTEMIS-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4902:
Description:
The configuration example relating downstream federation (see
https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
isn't compliant with the artemis-configuration.xsd, so tryng that config the
broker doesn't start with an error:
Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
found starting with element 'policy'. No child element is expected at this
point.
This is a part of the example configuration:
eu-east-1-connector
netty-connector
but policy element must be before upstream-connector, as of the XSD.
was:
The configuration example relating downstream federation (see
https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
isn't compliant with the artemis-configuration.xsd, so tryng that config the
broker doesn't start with an error:
Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
found starting with element 'policy'. No child element is expected at this
point.
This is a part of the example configuration:
{{
eu-east-1-connector
netty-connector
}}
but policy element must be before upstream-connector, as of the XSD.
> Downstream federation example not compliant with xsd
>
>
> Key: ARTEMIS-4902
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4902
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Documentation
>Reporter: Piero Cena
>Priority: Major
>
> The configuration example relating downstream federation (see
> https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
> isn't compliant with the artemis-configuration.xsd, so tryng that config the
> broker doesn't start with an error:
> Invalid configuration
> org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
> found starting with element 'policy'. No child element is expected at this
> point.
> This is a part of the example configuration:
>
> eu-east-1-connector
>
> netty-connector
>
>
>
> but policy element must be before upstream-connector, as of the XSD.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Updated] (ARTEMIS-4902) Downstream federation example not compliant with xsd
[
https://issues.apache.org/jira/browse/ARTEMIS-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4902:
Description:
The configuration example relating downstream federation (see
https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
isn't compliant with the artemis-configuration.xsd, so tryng that config the
broker doesn't start with an error:
Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
found starting with element 'policy'. No child element is expected at this
point.
This is a part of the example configuration:
{{
eu-east-1-connector
netty-connector
}}
but policy element must be before upstream-connector, as of the XSD.
was:
The configuration example relating downstream federation (see
https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
isn't compliant with the artemis-configuration.xsd, so tryng that config the
broker doesn't start with an error:
Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
found starting with element 'policy'. No child element is expected at this
point.
This is a part of the example configuration:
{{ }}
{{ }}{{eu-east-1-connector
}}{{ }}
{{netty-connector }}
{{ }}
{{}}
but policy element must be before upstream-connector, as of the XSD.
> Downstream federation example not compliant with xsd
>
>
> Key: ARTEMIS-4902
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4902
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Documentation
>Reporter: Piero Cena
>Priority: Major
>
> The configuration example relating downstream federation (see
> https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
> isn't compliant with the artemis-configuration.xsd, so tryng that config the
> broker doesn't start with an error:
> Invalid configuration
> org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
> found starting with element 'policy'. No child element is expected at this
> point.
> This is a part of the example configuration:
> {{
> eu-east-1-connector
>
> netty-connector
>
> }}
>
> but policy element must be before upstream-connector, as of the XSD.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Created] (ARTEMIS-4902) Downstream federation example not compliant with xsd
Piero Cena created ARTEMIS-4902:
---
Summary: Downstream federation example not compliant with xsd
Key: ARTEMIS-4902
URL: https://issues.apache.org/jira/browse/ARTEMIS-4902
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Documentation
Reporter: Piero Cena
The configuration example relating downstream federation (see
https://activemq.apache.org/components/artemis/documentation/latest/federation-address.html#configuring-downstream-federation)
isn't compliant with the artemis-configuration.xsd, so tryng that config the
broker doesn't start with an error:
Invalid configuration
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was
found starting with element 'policy'. No child element is expected at this
point.
This is a part of the example configuration:
{{ }}
{{ }}{{eu-east-1-connector
}}{{ }}
{{netty-connector }}
{{ }}
{{}}
but policy element must be before upstream-connector, as of the XSD.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
[jira] [Comment Edited] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848214#comment-17848214
]
Piero Cena edited comment on ARTEMIS-4777 at 5/21/24 2:05 PM:
--
I simply used two clients (nodejs clients written with
[rhea|https://github.com/amqp/rhea/]), one receiver connected to the Artemis
broker and subscribed to "test" node, one sender connected to the Classic
broker and sending messages to "test" destination. I've tried both with "test"
as a topic and "test" as a queue. No messages were received from the first
client.
As specified in my Stack Overflow question, we need to bridge with our Artemis
broker instance some others AMQP brokers, not only ActiveMQ Classic.
The proposed solution on SO (Camel with AMQP component) has been explored in
the past but we experienced poor performance and problems with high message
volumes.
was (Author: JIRAUSER305511):
I simply used two clients (nodejs clients written with
[rhea.js|[http://example.com|https://github.com/amqp/rhea/]]), one receiver
connected to the Artemis broker and subscribed to "test" node, one sender
connected to the Classic broker and sending messages to "test" destination.
I've tried both with "test" as a topic and "test" as a queue. No messages were
received from the first client.
As specified in my Stack Overflow question, we need to bridge with our Artemis
broker instance some others AMQP brokers, not only ActiveMQ Classic.
The proposed solution on SO (Camel with AMQP component) has been explored in
the past but we experienced poor performance and problems with high message
volumes.
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.33.0
> Environment: Server installed on CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
> {code:xml}
>
> retry-interval="1000" reconnect-attempts="2" user="xxx{*}" password="xxx{*}">
>
>
> {code}
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
> {code:xml}
>
>
> {code}
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly (between 2
> Artemis).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848214#comment-17848214
]
Piero Cena commented on ARTEMIS-4777:
-
I simply used two clients (nodejs clients written with
[rhea.js|[http://example.com|https://github.com/amqp/rhea/]]), one receiver
connected to the Artemis broker and subscribed to "test" node, one sender
connected to the Classic broker and sending messages to "test" destination.
I've tried both with "test" as a topic and "test" as a queue. No messages were
received from the first client.
As specified in my Stack Overflow question, we need to bridge with our Artemis
broker instance some others AMQP brokers, not only ActiveMQ Classic.
The proposed solution on SO (Camel with AMQP component) has been explored in
the past but we experienced poor performance and problems with high message
volumes.
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.33.0
> Environment: Server installed on CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
> {code:xml}
>
> retry-interval="1000" reconnect-attempts="2" user="xxx{*}" password="xxx{*}">
>
>
> {code}
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
> {code:xml}
>
>
> {code}
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly (between 2
> Artemis).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4777:
Description:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers, one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly (between 2 Artemis).
was:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers, one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly (between 2 artemis).
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: Server installed on CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="xxx{*}"
> password="xxx{*}">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly (between 2
> Artemis).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4777:
Environment: Server installed on CentOS Linux release 7.9.2009 (was:
CentOS Linux release 7.9.2009)
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: Server installed on CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="{*}{{*}}{*}"
> password="{*}">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly (between 2
> artemis).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4777:
Description:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers, one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly (between 2 artemis).
was:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers, one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="{*}{{*}}{*}"
> password="{*}">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly (between 2
> artemis).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848203#comment-17848203
]
Piero Cena commented on ARTEMIS-4777:
-
see my question on stackoverflow:
[https://stackoverflow.com/questions/78477736/activemq-artemis-broker-connection-to-activemq-classic|http://example.com]
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="{*}{{*}}{*}"
> password="{*}">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4777:
Description:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers, one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
was:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="{*}{{*}}{*}"
> password="{*}">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers, one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4777:
Description:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
was:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{{}{}}}{{{}{}}}{{{}{}}}{{{}{}}}{{{}{}}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="*{*}{{*}}"
> password="{{*}}{*}*">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
[
https://issues.apache.org/jira/browse/ARTEMIS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piero Cena updated ARTEMIS-4777:
Description:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
was:
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{}}
{{}}
{{}}
{{}}
{{}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
> Broker connections (AMQP) with receiver operation not working
> -
>
> Key: ARTEMIS-4777
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.33.0
> Environment: CentOS Linux release 7.9.2009
>Reporter: Piero Cena
>Priority: Major
>
> Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
> in order to receive messages from one destination (preferably a topic
> destination). Here is the configuration on Artemis instance:
>
> {{}}
> {{ retry-interval="1000" reconnect-attempts="2" user="{*}{*}{*}"
> password="{*}">}}
> {{}}
> {{}}
> {{}}
>
> The address "test" is predefined as multicast on Artemis and exists on the
> other side:
>
> {{}}
> {{}}
> {{}}
>
> On startup Artemis will connect correctly to Classic but no message is
> received on the Artemis side when published to the Classic destination "test".
> The same test has done with two Artemis brokers one configured as above, but
> the results are the same.
> Only "sender" or "mirror" operations seem to work properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4777) Broker connections (AMQP) with receiver operation not working
Piero Cena created ARTEMIS-4777:
---
Summary: Broker connections (AMQP) with receiver operation not
working
Key: ARTEMIS-4777
URL: https://issues.apache.org/jira/browse/ARTEMIS-4777
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.33.0
Environment: CentOS Linux release 7.9.2009
Reporter: Piero Cena
Trying to connect an Artemis instance to an instance of ActiveMQ Classic 5.15
in order to receive messages from one destination (preferably a topic
destination). Here is the configuration on Artemis instance:
{{{}{}}}{{{}{}}}{{{}{}}}{{{}{}}}{{{}{}}}
The address "test" is predefined as multicast on Artemis and exists on the
other side:
{{}}
{{}}
{{}}
On startup Artemis will connect correctly to Classic but no message is received
on the Artemis side when published to the Classic destination "test".
The same test has done with two Artemis brokers one configured as above, but
the results are the same.
Only "sender" or "mirror" operations seem to work properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
