FYI, if you have SEDA flow configured in your servicemix.xml in addition to JMSFlow (which is the default configuration), your clustered configuration will prefer to use it over JMSFlow if the target endpoint exists on the same node as the source endpoint.
----- Original Message ---- From: Lars Heinemann <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, May 16, 2008 9:48:34 AM Subject: Re: Load Balancing problems Ganesh, actually I never tried to setup 2 smx instances working together, but I know that the default transport policy of smx is the FirstChoicePolicy. That means it will always take the first endpoint in the list of available endpoint to route the message to. Sounds somehow like your problem, doesn't it? So if the activemq is somehow that intelligent under the hood, then it should pass the messages in equal load to your endpoints. But as I understood you, this is not the case. Another thing. The round robin policy is part of smx. Actually it is only in 3.3 version. Some minutes ago I put it to 3.2. So you would probably have to choose the RandomChoicePolicy for your testing. The problem with this policy is that it will choose the endpoint randomly...so don't expect that much. Lars navigator09 schrieb: > Hi Lars, > > I am using the servicemix version 3.2.1 . I have a doubt here. The > servicemix load balancing feature is provided by apache mq. I have read the > documentation of apache MQ and it says that, load bancing is done by > splitting the total load into equally among servicemix instances. If they > are using round robin algoritham, then for 10messages how will they > distribute the load? > > Regards, > Ganesh > > > lhe77 wrote: > >> Btw. I am not sure if this policy is already in your smx version. >> Otherwise you need to use the RandomChoicePolicy or get the actual trunk >> version of smx. >> >> Lars >> >> >> >> >> Lars Heinemann schrieb: >> >>> Hi, >>> >>> try adding this to your servicemix.xml: >>> >>> ... >>> </sm:container> >>> >>> <bean factory-method="getBroker" factory-bean="jbi"> <property >>> name="defaultServiceChooser"> <bean >>> class="org.apache.servicemix.jbi.resolver.ServiceRoundRobinPolicy" /> >>> </property> >>> </bean> >>> >>> ... >>> >>> >>> In the above case there will be a round robin logic used to choose >>> between services with the same name. >>> There is also a RandomChoicePolicy, but it's not that effective in my >>> opinion. >>> >>> Hope this helps, >>> Lars >>> >>> >>> >>> navigator09 schrieb: >>> >>>> Hi , I am tryning to achieve load balancing in servicemix as >>>> mentioned in the >>>> tutorial http://servicemix.apache.org/clustering.html. >>>> >>>> The bridge between the two services is successfully done, however >>>> when I >>>> send 10 messages to any one instance, all ten messages are handled by >>>> that >>>> instance only. It dosnt load balance. I am posting the active MQ files >>>> below. Let me know how to solve the matter. >>>> >>>> >>>> <?xml version="1.0" encoding="UTF-8"?> >>>> <!-- >>>> >>>> Licensed to the Apache Software Foundation (ASF) under one or more >>>> contributor license agreements. See the NOTICE file distributed >>>> with >>>> this work for additional information regarding copyright ownership. >>>> The ASF licenses this file to You under the Apache License, >>>> Version 2.0 >>>> (the "License"); you may not use this file except in compliance with >>>> the License. You may obtain a copy of the License at >>>> >>>> http://www.apache.org/licenses/LICENSE-2.0 >>>> >>>> Unless required by applicable law or agreed to in writing, software >>>> distributed under the License is distributed on an "AS IS" BASIS, >>>> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or >>>> implied. >>>> See the License for the specific language governing permissions and >>>> limitations under the License. >>>> >>>> --> >>>> <beans xmlns:amq="http://activemq.org/config/1.0";> >>>> <!-- ActiveMQ JMS Broker configuration --> >>>> <amq:broker id="broker" brokerName="pd92" depends-on="jmxServer" >>>> useShutdownHook="false"> >>>> >>>> <!-- Disable creation of the jmx connector which is >>>> created in the jmx.xml configuration file --> >>>> <amq:managementContext> >>>> <bean class="org.apache.activemq.broker.jmx.ManagementContext"> >>>> <property name="createConnector" value="false" /> >>>> </bean> >>>> </amq:managementContext> >>>> >>>> <!-- Use journaled JDBC persistence --> >>>> <amq:persistenceAdapter> >>>> <amq:journaledJDBC journalLogFiles="5" >>>> dataDirectory="D:\apache-servicemix-3.2.1\data\amq"/> >>>> >>>> <!-- To use a different datasource, use th following syntax : --> >>>> <!-- <amq:journaledJDBC journalLogFiles="5" >>>> dataDirectory="../data" >>>> dataSource="#postgres-ds"/> >>>> --> >>>> </amq:persistenceAdapter> >>>> <amq:transportConnectors> >>>> <!-- Activate a TCP connector with multicast discovery. >>>> Note that multicast may be disabled if your computer >>>> is not on a network, which may prevent the broker to start. >>>> In such a case, just remove the discoveryUri attribute. >>>> --> >>>> <amq:transportConnector uri="tcp://localhost:61616"/> >>>> >>>> </amq:transportConnectors> >>>> <amq:networkConnectors> >>>> <!-- by default just auto discover the other brokers --> >>>> <!-- <amq:networkConnector uri="multicast://default"/> --> >>>> <amq:networkConnector uri="static://(tcp://pd190:61616)" >>>> conduitSubscriptions="false"/> >>>> </amq:networkConnectors> >>>> </amq:broker> >>>> <!-- This xbean configuration file supports all the standard >>>> spring xml >>>> configuration options --> >>>> <!-- Postgres DataSource Sample Setup --> >>>> <!-- <bean id="postgres-ds" >>>> class="org.postgresql.ds.PGPoolingDataSource"> >>>> <property name="serverName" value="localhost"/> >>>> <property name="databaseName" value="activemq"/> >>>> <property name="portNumber" value="0"/> >>>> <property name="user" value="activemq"/> >>>> <property name="password" value="activemq"/> >>>> <property name="dataSourceName" value="postgres"/> >>>> <property name="initialConnections" value="1"/> >>>> <property name="maxConnections" value="10"/> >>>> </bean> >>>> --> >>>> <!-- MySql DataSource Sample Setup using the Commons DBCP pooler >>>> (http://jakarta.apache.org/commons/dbcp/) --> >>>> <!-- <bean id="mysql-ds" >>>> class="org.apache.commons.dbcp.BasicDataSource" >>>> destroy-method="close"> >>>> <property name="driverClassName" value="com.mysql.jdbc.Driver"/> >>>> <property name="url" value="jdbc:mysql://localhost/activemq"/> >>>> <property name="username" value="activemq"/> >>>> <property name="password" value="activemq"/> >>>> <property name="poolPreparedStatements" value="true"/> >>>> </bean> >>>> --> >>>> <!-- MySql DataSource Sample Setup using the c3p0 pooler >>>> (http://sf.net/projects/c3p0) --> >>>> <!-- <bean id="mysql-ds" >>>> class="com.mchange.v2.c3p0.ComboPooledDataSource" >>>> destroy-method="close"> >>>> <property name="driverClass" value="com.mysql.jdbc.Driver"> >>>> <property name="jdbcUrl" >>>> value="jdbc:mysql://localhost:3306/activemq"> >>>> <property name="user" value="activemq"> >>>> <property name="password" value="activemq"> >>>> <property name="minPoolSize" value="5"> >>>> <property name="maxPoolSize" value="10"> >>>> <property name="acquireIncrement" value="3"> >>>> </bean> >>>> --> >>>> <!-- Embedded Derby DataSource Sample Setup --> >>>> <!-- <bean id="derby-ds" >>>> class="org.apache.derby.jdbc.EmbeddedDataSource"> >>>> <property name="databaseName" value="derbydb"/> >>>> <property name="createDatabase" value="create"/> >>>> </bean> >>>> --> >>>> </beans> >>>> >>>> >>>> Regards, >>>> Ganesh >>>> >>>> >>>> >> > >
