[ 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
