[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
Hi, Just for your info, using remoting 2.5.1 cannot solve the message stuck issue. You probably need to wait for 2.5.2 release. and then better wait for a new JBM release for AS 5. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4242233#4242233 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242233 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
If you want a client in JBM 1.x to failover automatically from one node to another you need to set supportsFailover to true in the descriptor where the connection factory is deployed. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4242041#4242041 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242041 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
Ideally, I should be using ClusteredConnectionFactory, but i haven't gotten that to work. Messages get stuck on Cluster B when using ClusteredConnectionFactory.It seems like there are issues with ClusteredConnectionFactory. I'll try creating a custom ConnectionFactory with only SupportsFailover set to true to see if it helps. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4242043#4242043 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242043 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
It depends what you want to do. When you originally said failover I assume you really meant reconnection, in which case you don't need a clustered connection factory. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4242055#4242055 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242055 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
I tried setting SupportsFailOver to true on the Connection. Then, I tried testing failover by taking down node B0, and fail over worked, messages went to B1. After i period of time i brought up B0 and took down B1. Messages never got delievered to B0 and piled up in the message/deliver count queue. I brought up B1, and still nothing happened until i took down B0, then fail over occured and B1 processed the backlog of messages. Next i took down B1 and once again i end up in the messages stuck situation. It seems to me that FailOver works the first time I take down node B0, but after that FailOver doesn't work properly. Is there anything else i can try? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4242073#4242073 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4242073 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
Hi, Can you please post your bridge service configure here? Thanks Howard View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4241503#4241503 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241503 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
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=SourceDestinationLookupcom.company.wop.ots.event.queue/attribute
|
| !-- The JNDI lookup for the target destination --
| attribute
name=TargetDestinationLookupcom.company.wop.ots.event.queue/attribute
| attribute name=QualityOfServiceMode0/attribute
|
| !-- The maximum number of messages to consume from the source
| before sending to the target --
| attribute name=MaxBatchSize5/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=MaxBatchTime5000/attribute
|!-- The number of ms to wait between connection retrues in the
event connections
| to source or target fail --
| attribute name=FailureRetryInterval5000/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=AddMessageIDInHeaderfalse/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=ProviderNameDefaultJMSProvider/attribute
| attribute name=ProviderAdapterClass
| org.jboss.jms.jndi.JNDIProviderAdapter
| /attribute
| !-- The combined connection factory --
| attribute name=FactoryRefXAConnectionFactory/attribute
| !-- The queue connection factory --
| attribute name=QueueFactoryRefXAConnectionFactory/attribute
| !-- The topic factory --
| attribute name=TopicFactoryRefXAConnectionFactory/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=ProviderNameOTSJMSProvider/attribute
| attribute name=ProviderAdapterClass
| org.jboss.jms.jndi.JNDIProviderAdapter
| /attribute
| !-- The combined connection factory --
| attribute name=FactoryRefConnectionFactory/attribute
| !-- The queue connection factory --
| attribute name=QueueFactoryRefConnectionFactory/attribute
| !-- The topic factory --
| attribute name=TopicFactoryRefConnectionFactory/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
|
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
We're using postgres to persist messages. In the file postgresql-persistence-service.xml, I configured the PostOffice to | attribute name=Clusteredtrue/attribute | attribute name=FailoverOnNodeLeavetrue/attribute | Is this correct? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4241577#4241577 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241577 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
anonymous wrote : | jboss 5.1, JBM 1.4.4 src, I modified JMSRemoteConnection to compile against Remoting 2.5.1, so we could have the Bridge fixes, etc. | I believe some of the changes Howard made on trunk will also require some changes on Remoting 2.5.X, but I don't think the required changes have been made yet. Howard: do you have more details about this? artp: as you are runninig from source: did you run the complete testsuite? You may have bugs at your code that we haven't tested yet. (the pending changes on remoting may be an issue for you). View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4241597#4241597 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241597 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clusted FailOver doesn't seem to work correctly with Bri
anonymous wrote : I believe some of the changes Howard made on trunk typo... Old habit.. I meant.. Branch_1_4. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4241598#4241598 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241598 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
