I forgot to mention that we have the bridge running as a HASingleton on cluster
A. The JMSProvider, has two nodes(ie Cluster B nodes B0,B1) configured in the
url provider.
| <mbean code="org.jboss.jms.server.bridge.BridgeService"
| name="jboss.messaging:service=Bridge,name=OTSPackageBridge"
| xmbean-dd="xmdesc/Bridge-xmbean.xml">
|
| <!-- The JMS provider loader that is used to lookup the source
destination -->
| <depends optional-attribute-name="SourceProviderLoader">
|
jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider</depends>
|
| <!-- The JMS provider loader that is used to lookup the target
destination -->
| <depends optional-attribute-name="TargetProviderLoader">
|
jboss.messaging:service=JMSProviderLoader,name=OTS-HAJNDIJMSProvider</depends>
|
| <!-- The JNDI lookup for the source destination -->
| <attribute
name="SourceDestinationLookup">com.company.wop.ots.event.queue</attribute>
|
| <!-- The JNDI lookup for the target destination -->
| <attribute
name="TargetDestinationLookup">com.company.wop.ots.event.queue</attribute>
| <attribute name="QualityOfServiceMode">0</attribute>
|
| <!-- The maximum number of messages to consume from the source
| before sending to the target -->
| <attribute name="MaxBatchSize">5</attribute>
|
| <!-- The maximum time to wait (in ms) before sending a batch to the
target
| even if MaxBatchSize is not exceeded.
| -1 means wait forever -->
| <attribute name="MaxBatchTime">5000</attribute>
| <!-- The number of ms to wait between connection retrues in the
event connections
| to source or target fail -->
| <attribute name="FailureRetryInterval">5000</attribute>
|
| <!-- The maximum number of connection retries to make in case of
failure,
| before giving up -1 means try forever-->
| <attribute name="MaxRetries">-1</attribute>
|
| <!-- If true then the message id of the message before bridging will
be added
| as a header to the message so it is available to the receiver.
Can then be
| sent as correlation id to correlate in a distributed
request-response -->
| <attribute name="AddMessageIDInHeader">false</attribute>
|
| </mbean>
|
Here is a snippet of our hajndi-jms-ds.xml
| <!-- The JMS provider loader -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
|
name="jboss.messaging:service=JMSProviderLoader,name=HAJNDIJMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <!-- Access JMS via HAJNDI -->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=${jboss.bind.address:localhost}:1100
| jnp.disableDiscovery=false
| jnp.partitionName=${jboss.partition.name:DefaultPartition}
| jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
| jnp.discoveryPort=1102
| jnp.discoveryTTL=16
| jnp.discoveryTimeout=5000
| jnp.maxRetries=1
| </attribute>
| </mbean>
|
Note:We changed the connection provider to ConnectioFactory, since
ClusteredConnectionFactory didn't work
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
|
name="jboss.messaging:service=JMSProviderLoader,name=OTS-HAJNDIJMSProvider">
| <attribute name="ProviderName">OTSJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">ConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">ConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">ConnectionFactory</attribute>
| <!-- Access JMS via HAJNDI -->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
|
java.naming.provider.url=dev-ots01.test.company.com:1100,dev-ots02.test.company.com:1100
| jnp.disableDiscovery=false
| jnp.partitionName=OTS-dev
| jnp.discoveryGroup=228.1.2.21
| jnp.discoveryPort=1102
| jnp.discoveryTTL=16
| jnp.discoveryTimeout=5000
| jnp.maxRetries=1
| </attribute>
| </mbean>
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241563#4241563
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241563
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
