springMvc integrated cluster

springMvc integrated cluster

 

springMvc integrated cluster, the address of the cluster should be written, and the form of writing is different

 

 

MQ cluster connection (spring integrated mq cluster)

Then you need to modify the address method when spring is integrated under the cluster

http://nettm.blog.51cto.com/4841905/1160108/

 

 <!-- Configure the JMS connection factory --> 

    <bean id="myConnectionFactory" 

        class="org.springframework.jms.connection.CachingConnectionFactory"> 

        <!-- Session cache number--> 

        <property name="sessionCacheSize" value="10" /> 

        <property name="targetConnectionFactory"> 

            <bean class="org.apache.activemq.ActiveMQConnectionFactory"> 

                <!-- MQ address--> 

                <property name="brokerURL" 

                    value="failover:(tcp://127.0.0.1:61616,tcp://127.0.0.1:61617)?randomize=false" /> 

                <!-- Whether to send asynchronously --> 

                <property name="useAsyncSend" value="false" /> 

            </bean> 

        </property> 

    </bean> 

 

http://www.cnblogs.com/shihaiming/p/6018916.html

<bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">  

    <property name=“brokerURL” value=“failover:(tcp://192.168.0.101:61616,tcp://192.168.0.101:61617, tcp://192.168.0.101:61618)" />  

     <property name="useAsyncSend" value="true" />  

     <property name="alwaysSessionAsync" value="true" />  

     <property name="useDedicatedTaskRunner" value="false" />  

</bean>  

then change

clientid, different systems use different channels

 

 

 

zk cluster connection (different dubbo services need different ports)

<!-- Consumer application name, used to calculate dependencies, not matching conditions, not the same as the provider -->

<dubbo:application name="esteelds-consumer" />

 

<!-- Use the zookeeper registry to expose the service address -->

<!-- Registration Center Address-->

<dubbo:registry protocol="zookeeper" address="172.18.1.101:2181,172.18.1.102:2181,172.18.1.103:2181" />

 

<!-- User service interface -->

<!-- Moved to the dubbo-consumer-list directory -->

 

<!-- provider application information for calculating dependencies -->

<dubbo:application name="esteelds-provider" />

 

<dubbo:registry protocol="zookeeper" address="172.18.1.101:2181,172.18.1.102:2181,172.18.1.103:2181" />

 

<!-- Expose services on port 20880 using the dubbo protocol -->

<dubbo:protocol name="dubbo" port="25555" />//Different dubbo services require different ports

 

<!-- User service interface -->

<!-- All moved to the dubbo-provider-list directory -->

 

springMvc integrated redis cluster

 

http://www.cnblogs.com/shiyalong/p/5916749.html

 

 

Properties file redis.properties

address1=127.0.0.1:7002

address2=127.0.0.1:7001

address3=127.0.0.1:7000

address4=127.0.0.1:7003

address5=127.0.0.1:7004

address6=127.0.0.1:7005

 

redis-context.xml

 

<!-- Connection pool configuration-->

    <bean name="genericObjectPoolConfig" class="org.apache.commons.pool2.impl.GenericObjectPoolConfig">

        <property name="maxWaitMillis" value="-1" />

        <property name="maxTotal" value="1000" />

        <property name="minIdle" value="8" />

        <property name="maxIdle" value="100" />

    </bean>

 

    <bean id="jedisClusterFactory" class="com.hanwei.its.itoss.dao.redis.JedisClusterFactory">

        <property name="addressConfig">

            <value>classpath:conf/redis.properties</value>

            <value>/conf/redis.properties</value>

        </property>

        <property name="addressKeyPrefix" value="address" /> <!-- The prefix of the key in the properties file --> 

        <property name="timeout" value="300000" />

        <property name="maxRedirections" value="6" />

        <property name="genericObjectPoolConfig" ref="genericObjectPoolConfig" />

    </bean>

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326397284&siteId=291194637