[jboss-as7-dev] TCPPING in AS7
Richard Achmatowicz
rachmato at redhat.com
Wed Mar 14 20:01:21 EDT 2012
He may have been referring to the fact that in AS 7.1.1 if you don't
include a <transport/> element in your cache container, you don't get a
transport. And in that case, caches in two instances of that cache
container would not communicate.
On 03/14/2012 07:12 PM, Kabir Khan wrote:
> A guy at last night's JUG was complaining about this. He mentioned there is a new setting to make the cache replicated, which now needs explicitly turning on. The config from 7.0.x does not turn this on in 7.1, the new setting needs turning on. I guess (but have no idea) that it is one of these values from the infinispan 1.2 xsd:
>
> <xs:complexType name="cache-container">
> <xs:complexContent>
> <xs:extension base="tns:base-cache-container">
> <xs:sequence>
> <xs:element name="transport" type="tns:transport" minOccurs="0">
> <xs:annotation>
> <xs:documentation>Overrides the transport characteristics for this cache container.</xs:documentation>
> </xs:annotation>
> </xs:element>
> <xs:choice maxOccurs="unbounded">
> <xs:element name="local-cache" type="tns:local-cache">
> <xs:annotation>
> <xs:documentation>Defines a LOCAL mode cache.</xs:documentation>
> </xs:annotation>
> </xs:element>
> <xs:element name="replicated-cache" type="tns:replicated-cache">
> <xs:annotation>
> <xs:documentation>Defines a REPL_* mode cache.</xs:documentation>
> </xs:annotation>
> </xs:element>
> <xs:element name="invalidation-cache" type="tns:invalidation-cache">
> <xs:annotation>
> <xs:documentation>Defines an INVALIDATION_* mode cache.</xs:documentation>
> </xs:annotation>
> </xs:element>
> <xs:element name="distributed-cache" type="tns:distributed-cache">
> <xs:annotation>
> <xs:documentation>Defines a DIST_* mode cache.</xs:documentation>
> </xs:annotation>
> </xs:element>
> </xs:choice>
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> On 14 Mar 2012, at 21:44, William DeCoste wrote:
>
>> Hi Brian,
>>
>> Has anything changed in the config of AS7.1 from 7.0.x? I am not seeing
>> any jgroups traffic or discovery. This configuration worked fine in
>> 7.0.x. When JGroups is loaded it just creates 2 1-node clusters. They
>> don't seem to see each other or even be trying.
>>
>> Thanks -Bill
>>
>> <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="tcp">
>> <stack name="tcp">
>> <transport type="TCP" socket-binding="jgroups-tcp"/>
>> <protocol type="TCPPING">
>> <property name="timeout">
>> 3000
>> </property>
>> <property name="initial_hosts">
>> 127.0.250.1[7600],127.0.251.1[7600]
>> </property>
>> <property name="port_range">
>> 1
>> </property>
>> <property name="num_initial_members">
>> 2
>> </property>
>> </protocol>
>> <protocol type="MERGE2"/>
>> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
>> <protocol type="FD"/>
>> <protocol type="VERIFY_SUSPECT"/>
>> <protocol type="BARRIER"/>
>> <protocol type="pbcast.NAKACK"/>
>> <protocol type="UNICAST2"/>
>> <protocol type="pbcast.STABLE"/>
>> <protocol type="pbcast.GMS"/>
>> <protocol type="UFC"/>
>> <protocol type="MFC"/>
>> <protocol type="FRAG2"/>
>> </stack>
>> </subsystem>
>>
>> --
>> Bill DeCoste
>> Principal Software Engineer, Red Hat
>> 978-204-0920
>> wdecoste at redhat.com
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
More information about the jboss-as7-dev
mailing list