You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jason Dexter (JIRA)" <ji...@apache.org> on 2009/08/05 10:32:35 UTC
[jira] Created: (AMQ-2344) Multicast works, but cannot be
controlled
Multicast works, but cannot be controlled
-----------------------------------------
Key: AMQ-2344
URL: https://issues.apache.org/activemq/browse/AMQ-2344
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.2.0
Reporter: Jason Dexter
I'm currently testing the network of brokers configuration (ref: http://activemq.apache.org/networks-of-brokers.html)
Actually this works, but concerning the available parameters for discoveryUris, I do not see any effect, when using a xbean configuration like
<transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default?reconnectDelay=4000&maxReconnectAttempts=10&useExponentialBackOff=false&initialReconnectDelay=5000"/>
I do not want to produce much multicast traffic, because it is not necessary in my target networks. Is there a way to let the above configured transport work as required?
Or is this a local brain problem? ;-)
Kind Regards
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Stable version of ActiveMQ
Posted by Sh...@sungard.com.
Hi,
Has anyone used ActiveMQ on Linux in Production?
If yes can you please let me know the version and also the way you installed activemq on machine?
Thanks.
Connection pool size of ActiveMQ
Posted by Sh...@sungard.com.
Hi,
Can anyone tell me what is the default connection pool size of ActiveMQ 5.2?
And how we can configure connection pooling through stomp protocol (Python client)?
[jira] Resolved: (AMQ-2344) Multicast works, but cannot be
controlled
Posted by "Jason Dexter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dexter resolved AMQ-2344.
-------------------------------
Resolution: Working as Designed
Fix Version/s: 5.2.0
as commented...
> Multicast works, but cannot be controlled
> -----------------------------------------
>
> Key: AMQ-2344
> URL: https://issues.apache.org/activemq/browse/AMQ-2344
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.2.0
> Reporter: Jason Dexter
> Fix For: 5.2.0
>
>
> I'm currently testing the network of brokers configuration (ref: http://activemq.apache.org/networks-of-brokers.html)
> Actually this works, but concerning the available parameters for discoveryUris, I do not see any effect, when using a xbean configuration like
> <transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default?reconnectDelay=4000&maxReconnectAttempts=10&useExponentialBackOff=false&initialReconnectDelay=5000"/>
> I do not want to produce much multicast traffic, because it is not necessary in my target networks. Is there a way to let the above configured transport work as required?
> Or is this a local brain problem? ;-)
> Kind Regards
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2344) Multicast works, but cannot be
controlled
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53468#action_53468 ]
Gary Tully commented on AMQ-2344:
---------------------------------
To configure how a client connects, add the parameters to the brokerURI on the client network connector or connection factory. I think the fix for https://issues.apache.org/activemq/browse/AMQ-2283 may be necessary though to allow the parameters to be applied.
The discoveryUri has a limited number of parameters on the broadcast side but these should be respected. things like the keepAlive and timeToLive, full details in http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/discovery/multicast/MulticastDiscoveryAgent.java
> Multicast works, but cannot be controlled
> -----------------------------------------
>
> Key: AMQ-2344
> URL: https://issues.apache.org/activemq/browse/AMQ-2344
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.2.0
> Reporter: Jason Dexter
>
> I'm currently testing the network of brokers configuration (ref: http://activemq.apache.org/networks-of-brokers.html)
> Actually this works, but concerning the available parameters for discoveryUris, I do not see any effect, when using a xbean configuration like
> <transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default?reconnectDelay=4000&maxReconnectAttempts=10&useExponentialBackOff=false&initialReconnectDelay=5000"/>
> I do not want to produce much multicast traffic, because it is not necessary in my target networks. Is there a way to let the above configured transport work as required?
> Or is this a local brain problem? ;-)
> Kind Regards
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2344) Multicast works, but cannot be
controlled
Posted by "Jason Dexter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53579#action_53579 ]
Jason Dexter commented on AMQ-2344:
-----------------------------------
I found my problem and tested the solution keppAliveInterval=<n> after reading the MulticastDiscoveryAgent soruce.
With the following configuration the multicast packages are reduced massively (keepAliveInterval default is DEFAULT_IDLE_TIME = 500)..
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616" discoveryUri="multicast://default?keepAliveInterval=5000"/>
(The default value can be a problem with some smart switches not supporting IGMP snooping).
IMHO this issue can be closed.
> Multicast works, but cannot be controlled
> -----------------------------------------
>
> Key: AMQ-2344
> URL: https://issues.apache.org/activemq/browse/AMQ-2344
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.2.0
> Reporter: Jason Dexter
>
> I'm currently testing the network of brokers configuration (ref: http://activemq.apache.org/networks-of-brokers.html)
> Actually this works, but concerning the available parameters for discoveryUris, I do not see any effect, when using a xbean configuration like
> <transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default?reconnectDelay=4000&maxReconnectAttempts=10&useExponentialBackOff=false&initialReconnectDelay=5000"/>
> I do not want to produce much multicast traffic, because it is not necessary in my target networks. Is there a way to let the above configured transport work as required?
> Or is this a local brain problem? ;-)
> Kind Regards
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.