You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Anand K Kalyanasundaram (JIRA)" <ji...@apache.org> on 2006/09/12 00:39:23 UTC

[jira] Commented: (SM-487) network clogging when service mix runs

    [ https://issues.apache.org/activemq/browse/SM-487?page=comments#action_36936 ] 
            
Anand K Kalyanasundaram commented on SM-487:
--------------------------------------------

I tried removing all multicast configurations in activemq and everything seems to work fine now. I changed the activemq configuration from

<transportConnectors>
       <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
       <transportConnector uri="vm://localhost" discoveryUri="multicast://default"/>
</transportConnectors>
    
<networkConnectors>
      <networkConnector uri="multicast://default"/>
</networkConnectors>

to 

 <transportConnectors>
       <transportConnector uri="tcp://localhost:61616"/>
       <transportConnector uri="vm://localhost"/>
</transportConnectors>
    
<networkConnectors>
      <networkConnector uri="static://(tcp://....:61616)"/>
</networkConnectors>

I am not sure about the implications of the change I made. Please coment on this change.


> network clogging when service mix runs
> --------------------------------------
>
>                 Key: SM-487
>                 URL: https://issues.apache.org/activemq/browse/SM-487
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.0-M1, 3.0-M2, 3.0.1
>         Environment: Linux 2.6.x (Suse 10 and Gentoo), Java 1.5.0_0x
>            Reporter: Anand K Kalyanasundaram
>            Priority: Critical
>
> Running servicemix 3.0 overloads the network on
> a linux machine. This does not happen with service mix 2.0.2. This happens with service mix 3.0-M1, 3.0-M2 and 3.0-SNAPSHOT and all of them consistently caused a "server" configured linux machine to become unresponsive on the network. On a linux desktop, the machine was responsive, but all outgoing and incomming connections to
> the machine where incurring huge latencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira