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/07/14 17:18:23 UTC
[jira] Created: (SM-487) network clogging when service mix runs
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
Environment: Linux 2.6.x (Suse 10 and Gentoo), Java 1.5.0_0x
Reporter: Anand K Kalyanasundaram
Priority: Critical
Fix For: 2.0.2
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
[jira] Updated: (SM-487) network clogging when service mix runs
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-487?page=all ]
Guillaume Nodet updated SM-487:
-------------------------------
Fix Version/s: (was: 2.0.2)
> 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
> 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
[jira] Commented: (SM-487) network clogging when service mix runs
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-487?page=comments#action_36659 ]
Guillaume Nodet commented on SM-487:
------------------------------------
Could you be a bit more precise please ?
Which components do you use ? Do you use clustering ?
Does it happen under load ?
> 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
> 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
[jira] Closed: (SM-487) network clogging when service mix runs
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-487?page=all ]
Guillaume Nodet closed SM-487.
------------------------------
Resolution: Won't Fix
Assignee: Guillaume Nodet
Changing / removing the discovery mechanism will
have no effect if you don't use clustering.
If you need clustering, you could use a different discovery mechanism
but this has no impact on servicemix itself.
> 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
> Assigned To: Guillaume Nodet
> 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
[jira] Commented: (SM-487) network clogging when service mix runs
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-487?page=comments#action_36663 ]
Guillaume Nodet commented on SM-487:
------------------------------------
Could you try to remove some features one by one and see if anything change ?
Like removing the jms broker, removing jmx, ...
> 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
> 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
[jira] Commented: (SM-487) network clogging when service mix runs
Posted by "Anand K Kalyanasundaram (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-487?page=comments#action_36662 ]
Anand K Kalyanasundaram commented on SM-487:
--------------------------------------------
I recently realized that it happens only on a Suse 9.0 Enterprise Server dual processor machine. It happens as soon as you start servicemix even without any components being deployed. I am not able to repeat the linux desktop behaviour. It seems to run fine on Redhat 9.0 too.
> 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
> 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
[jira] Commented: (SM-487) network clogging when service mix runs
Posted by "Anand K Kalyanasundaram (JIRA)" <ji...@apache.org>.
[ 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