Broker/Cluster Message Replication

I am trying to determine if messages sent to a Broker within a Cluster are replicated to different Brokers and as such the different Brokers' persistence message stores?
I what a HA solution that has no single point of failure within a site (and ultimately across sites, but let's focus on a single site to start with). I need the replication to ensure that if Broker-A goes down the message is still available and can be consumed via Broker-B; and not relying on Broker-A being restarted.
There is a statement within the Technical Overview document that might suggest that what I am looking for is not possible. It says...
"Note that broker clusters provide service availability but not data availability. If one broker in a cluster fails, clients connected to that broker can reconnect to another broker in the cluster but may lose some data while they are reconnected to the alternate broker."
If I am not asking to much already any cases studies, blue prints etc. would be nice. But simple answers to this question will also get my deep thanks.
Regards
Paul

Thank you for the response. I think you have confirmed my fears, but I will ask some more questions, just to make sure I am 100% clear...
Can 2 brokers share the exact same JDBC message store? From what you are saying we could do that but Broker-B would have to be passive. But to be clear could both Brokers be active and using the same store at the same time?
I am baffled as to how guaranteed message order can be provided if a Broker and its store is unavailable. Is it that new messages are processed out of order? ie, new messages are processed ignoring the failed broker's messages? Are there known issues with guaranteed message order when a Broker fails?
Thank you again for the response.
Regards
Paul.
Message was edited by:
paularmstrong

Similar Messages

Broker/Cluster Message Persistence and Replication

I am evaluating the Sun JMS MQ implementation and I am trying to determine if messages sent to a Broker within a Cluster are replicated to different Brokers and as such the different Brokers' persistence message stores?
I what a HA solution that has no single point of failure within a site (and ultimately across sites, but let's focus on a single site to start with). I need the replication to ensure that if Broker-A goes down the message is still available and can be consumed via Broker-B; and not relying on Broker-A being restarted.
There is a statement within the Technical Overview document that might suggest that what I am looking for is not possible. It says...
"Note that broker clusters provide service availability but not data availability. If one broker in a cluster fails, clients connected to that broker can reconnect to another broker in the cluster but may lose some data while they are reconnected to the alternate broker."
If I am not asking to much already any cases studies, blue prints etc. would be nice. But simple answers to this question will also get my deep thanks.
Regards
Paul

"Note that broker clusters provide service
availability but not data availability. If one broker
in a cluster fails, clients connected to that broker
can reconnect to another broker in the cluster but
may lose some data while they are reconnected to the
alternate broker."Yes, that's clustering. Messages are stored-and-forwarded. If the broker where the message is stored goes down, it is not available until the broker restarts.
What you are looking for is high availability where messages from the active instance are synchronously replicated to a standby instance. In the failover case the JMS clients tranparently reconnect and operation continues.
I don't know if Sun IMQ provides that but I do know that SwiftMQ does that very well:
http://www.swiftmq.com/products/harouter/introduction/index.html
Full docs start here:
http://www.swiftmq.com/products/harouter/index.html
-- Andreas

Cluster session replication

Hi,
CFMX 7.01 MULTISERVER:
I am facing a problem, session are not replicating on two CF
instances on same server. Below is Jrun log file error detail
30/05 17:18:10 error Setup of session replication failed.
[1]java.rmi.RemoteException: The web application
'cfusion.ear#cfusion.war' could not be found to accept sessions for
replication.
at
jrun.servlet.session.SessionReplicationService.replicate(SessionReplicationService.java:8 0)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown
Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native
Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown
Source)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
CFMX 7.01 MULTISERVER:
My set-up, installed as multiserver. create new instance from
CF Admin. Cluster them from Jrun Admin. I followed almost all
instructions from live doc, and also help from other blogs.
So far i could not findout why session can not replicate on
same machine.
Is any body have idea about above error.
Thanks for your help in-advance

In my config.xml, I have:
<cluster>
<name>MyCluster</name>
<cluster-address/>
<default-load-algorithm>round-robin</default-load-algorithm>
<cluster-messaging-mode>unicast</cluster-messaging-mode>
<frontend-host>192.168.6.6</frontend-host>
<frontend-http-port>80</frontend-http-port>
<frontend-https-port>443</frontend-https-port>
</cluster>
I already posted my weblogic.xml

ECC Cluster Enqueue Replication Server

Hi Experts,
I installed SAP ECC EHP5 in a Windows Cluster Environment. I followed all the steps in the installation guide. When I execute the following command to check the status of the Enqueue Replication Server:
enqt.exe pf=<profile> 2
The following message appears:
Nr Man UserName Name-- M -
Arg-- -UsVB-----
-Object- TCOD B
Entries in Backup-File...: 0
Instead of the following message:
Replication is enabled in server, repl. server is connectedReplication is active...
Do I miss any adittional configuration??
The trace file had this information:
trc file: "dev_eq_trc_7804", trc level: 1, release: "720"
Wed Oct 19 14:02:02 2011
Enqueue Info: enque/use_pfclock2 = FALSE
Enqueue Info: enque/use_pfclock2 = FALSE
Enqueue Info: enque/disable_replication = 0
Enqueue Info: replication enabled
Enqueue Info: enque/replication_dll not set
LstRestore: no old replication configured
I manually set enque/disable_replication parameter to 2 because previously was set in the instance profile in 0.
Any ideas?
Thanks a lot.
Kind Regards

Hi Estaban,
The command is "ensmon" not "enqt". Check the example, below;
ensmon pf=<ERS profile> 2
Best regards,
Orkun Gedik

Integration Broker Application Messages Issue

Hi Gurus,
We are having an issue with the Integration Broker Application Messages.
Here's the issue, when we run Dynrole it process Application Messages. All messages go to Done status, but checking the instance, the Footer comes first, where the header should comes first. This issue happens from time to time, we only run 8 application messages at a time (header and footer included). BTW, failover is enabled on our server.
We are trying to find a solution on this, please help us.
Thanks,
Red

Hi,
Did it resolved? If yes, please share here if possible.
Cheers,
Elvis.

Broker-to-broker cluster connections

Can the broker-to-broker cluster connections be configured to use an HTTP proxy like a client?
I have a question about broker clustering configurations.
Page 59 of the Admin guide mentions using a cluster to deal with
firewall restrictions. Can the broker-to-broker cluster connections
be configured to use an HTTP proxy like a client? Or if you have
two brokers in a cluster separated by a firewall(s), must you open the
firewall to allow them to communicate directly, no proxies allowed?

Currently iMQ (2.0) does not support HTTP between brokers. Therefore you
need to open firewall to allow broker to broker communication if they
are separated by firewall.

How the broker cluster determine which broker to be connected

Currently,there are four server instances in glassfish a cluster.By default classfish used MQ broker cluster to provide JMS services.The question is when a client use the JMS connection factory to create a connection,what's the policy the brokers cluster used to determine which broker to be connected to?
In MQ's document, it's said that the connection was create use the imqAddressListBehavior and imqAddressList properties.
As a fact,I found that the connection distribution is 350/200/50/200(broker3,broker4,broker1,broker2);
the imqAddressList =broker3,broker4,broker1,broker2
the imqAddressListBehavior= priority
Can anyone tell me what's the policy the brokers cluster to routing the connection?

Hi,
The brokers is started up by glassfish nodeagent process,when i started a nodeagent.All of the brokers are behind the firewall.
can anyone share some document about this subject?
thanks a lots!

[svn:bz-trunk] 21327: Updated the sample destination config to show the new "none" value for cluster-message-routing

Revision: 21327
Revision: 21327
Author:   [email protected]
Date:     2011-06-02 08:51:22 -0700 (Thu, 02 Jun 2011)
Log Message:
Updated the sample destination config to show the new "none" value for cluster-message-routing
Modified Paths:
    blazeds/trunk/resources/config/messaging-config.xml

Thanks Carlo for your reply.
I have read again the link and you are correct that in using the preferred command together with localhost under POTS dial-peer, I can now select which correct path to choose for my outbound calls. I'm just not very strong with dial-peer and translation rules at the moment.
I will try this solution during the weekend and let you know. But it would have been better if there was a sample configuration for this option.

Messages in Broker cluster

Hi,
My question is, if a broker in cluster setup fails, do the other brokers know about the messages sitting on this failed broker?
If so can one of the other brokers send them out to relevant consumers?
I would very much appreciate your reply.
Kind Regards

Hi,
My question is, if a broker in cluster setup fails,
do the other brokers know about the messages sitting
on this failed broker?
If so can one of the other brokers send them out to
relevant consumers?
I would very much appreciate your reply.
In the current release, a cluster allows scaling of connections
and availability of service but does not support high availablity
of message data. This means that connections can fail over
to a new broker and continue to send or receive messages,
but the messages stored on a down broker (aka the broker
that the producer was connected to) will remain unavailable
until either:
* the broker restarts
* a new broker is started which points to the same store
If you need the message data to be highly available, we
do support that functionality through SunCluster on solaris.
(sun cluster handles storing the data on a highly available
file store and automatically starting a new broker to take over
for a down broker)
We are also currently working on adding HA functionality to
MQ so that we can provide this functionality in a future
release

DAG 2010 Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network replication

Hello,
DAG Exchange 2010 SP3 RU6 with MAPI network and Replication network. All works correctly.
But, when the DAG member restarts , the cluster goes offline and i can't bring it online.
The message error:
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access.
Cluster Network 1 is the replication network and it is normal that allow client access is unchecked
I already tried to check, apply then uncheck apply. it does anything.
Could you please help me to figure out the issue ?
Best regards

Hi,
Check below link.
http://forums.msexchange.org/Cluster_network_name_is_not_online/m_1800552315/tm.htm
I was able to resolve the issue without taking down any resources.
First, I noticed that the Failover Cluster Manager "Cluster Name" had the IP address of the replication network only..
After going back through the guide @
http://technet.microsoft.com/en-us/library/dd638104.aspx I changed the properties on the NICs for file sharing, etc..I then adjusted windows firewall rules to block traffic from my MAPI network destined for the replication network.
I then removed the IP from the replication network on the DAG leaving only the 1 MAPI network IP.
After an hour or so, I ran Get-DatabaseAvailabilityGroupNetwork and seen that the MAPIAccess property was finally set to true on my MAPI network. I went back to Failover Cluster Manager and my Cluster Core Resource Cluster Name dropped the IP address that was
associated (IP from the replication network) I added a new IP from my Mapi network range, updated the DAG IP in Exchange and the DNS record for the DAG and my cluster resource came online.

Weblogic 7.0 sp1 cluster - session replication problem

Hi,
          I have installed Weblogic 7.0 sp2 on Win NT. To test clustering
          feature, I have installed one admin server and added two managed
          servers. All are running on same box. I could deploy web application
          to the cluster. Connection pools and every other resource is working
          well with the cluster. However I couldn't get session replication to
          work. I have modified web app descriptor, and set 'persistent store
          type' to "replicated".
          I accessed application from one managed server, in the middle of
          session I modified the port number in the URL to point to other
          managed server. It looks like second managed server has no idea of
          that session, my app fails because of this.
          Could you please help me out in this, Do I need to do any thing in
          addition to the above. I couldn't find much in the BEA manual..
          Thanks
          Rao


          For Web application like servlets/JSP, it is better to put one web server as proxy
          plugin before your two managed servers and access your application through web
          proxy. (You need set session as in-memory replicated either in weblogic.xml or
          by console editor). Otherwise, you need record the session cookie from the first
          serevr and send the cookie to the second server (not sure if it works). To access
          EJB/JMS, use cluster URL like t3://server1:port1,server2:port2.
          [email protected] (Rao) wrote:
          >Hi,
          >
          >I have installed Weblogic 7.0 sp2 on Win NT. To test clustering
          >feature, I have installed one admin server and added two managed
          >servers. All are running on same box. I could deploy web application
          >to the cluster. Connection pools and every other resource is working
          >well with the cluster. However I couldn't get session replication to
          >work. I have modified web app descriptor, and set 'persistent store
          >type' to "replicated".
          >
          >I accessed application from one managed server, in the middle of
          >session I modified the port number in the URL to point to other
          >managed server. It looks like second managed server has no idea of
          >that session, my app fails because of this.
          >
          >
          >Could you please help me out in this, Do I need to do any thing in
          >addition to the above. I couldn't find much in the BEA manual..
          >
          >
          >Thanks
          >Rao

Failover cluster without replication

Hello,
This might be a basic question to many, but I couldn't find a straight answer so ..
is it possible to create a failover cluster with shared storage and without any replication/copies of the databases?
i.e.:
Create two exchange nodes with two shared luns, make each an owner of a lun and have its database stored in it.
If node1 failed, it's lun and database gets mounted on node2, making node2 the host of both databases until node1 is back online.
if the answer is no, was it possible in 2010?
Thanks.

Hello,
This might be a basic question to many, but I couldn't find a straight answer so ..
is it possible to create a failover cluster with shared storage and without any replication/copies of the databases?
i.e.:
Create two exchange nodes with two shared luns, make each an owner of a lun and have its database stored in it.
If node1 failed, it's lun and database gets mounted on node2, making node2 the host of both databases until node1 is back online.
if the answer is no, was it possible in 2010?
Thanks.
Nothing in Exchange does that. Anything that did would be a 3rd party solution and not supported by Microsoft.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

IDVD: 'ME BROK'N' Message in series 5 and 6 Theme Previews

When Deciding on what theme to use after just installing iLife '08, the themes under 5.0 and 6.0 have a preview message saying 'Me Brok'n' in purple writing with a lime background, it looks very childish writing however all the other themes work fine. Although it makes it difficult to choose, and well it shouldn't be there anyway.
If some one can help it would be mostly appreciated, and if you need to have a screenshoot I have one available.
Thanks

Delete the iDVD preference file, com.apple.iDVD.plist, that resides in your User/Library/Preferences folder. See if that will help.
You might have to do a custom install of the iLife 08 and select the older themes to reinstall. Then try again.

DFSr supported cluster configurations - replication between shared storage

I have a very specific configuration for DFSr that appears to be suffering severe performance issues when hosted on a cluster, as part of a DFS replication group.
My configuration:
3 Physical machines (blades) within a physical quadrant.
3 Physical machines (blades) hosted within a separate physical quadrant
Both quadrants are extremely well connected, local, 10GBit/s fibre.
There is local storage in each quadrant, no storage replication takes place.
The 3 machines in the first quadrant are MS clustered with shared storage LUNs on a 3PAR filer.
The 3 machines in the second quadrant are also clustered with shared storage, but on a separate 3PAR device.
8 shared LUNs are presented to the cluster in the first quadrant, and an identical storage layout is connected in the second quadrant. Each LUN has an associated HAFS application associated with it which can fail-over onto any machine in the local cluster.
DFS replication groups have been set up for each LUN and data is replicated from an "Active" cluster node entry point, to a "Passive" cluster node that provides no entry point to the data via DFSn and a Read-Only copy on it's shared cluster
storage.
For the sake of argument, assume that all HAFS application instances in the first quadrant are "Active" in a read/write configuration, and all "Passive" instances of the HAFS applications in the other quadrants are Read-Only.
This guide: http://blogs.technet.com/b/filecab/archive/2009/06/29/deploying-dfs-replication-on-a-windows-failover-cluster-part-i.aspx defines
how to add a clustered service to a replication group. It clearly shows using "Shared storage" for the cluster, which is common sense otherwise there effectively is no application fail-over possible and removes the entire point of using a resilient
cluster.
This article: http://technet.microsoft.com/en-us/library/cc773238(v=ws.10).aspx#BKMK_061 defines the following:
DFS Replication in Windows Server 2012 and Windows Server 2008 R2 includes the ability to add a failover cluster
as a member of a replication group. The DFS Replication service on versions of Windows prior to Windows Server 2008 R2
is not designed to coordinate with a failover cluster, and the service will not fail over to another node.
It then goes on to state, quite incredibly: DFS Replication does not support replicating files on Cluster Shared Volumes.
Stating quite simply that DFSr does not support Cluster Shared Volumes makes absolutely no sense at all after stating clusters
are supported in replication groups and a technet guide is provided to setup and configure this configuration. What possible use is a clustered HAFS solution that has no shared storage between the clustered nodes - none at all.
My question: I need some clarification, is the text meant to read "between" Clustered
Shared Volumes?
The storage configuration must to be shared in order to form a clustered service in the first place. What
we am seeing from experience is a serious degradation of
performance when attempting to replicate / write data between two clusters running a HAFS configuration, in a DFS replication group.
If for instance, as a test, local / logical storage is mounted to a physical machine the performance of a DFS replication group between the unshared, logical storage on the physical nodes is approaching 15k small files per minute on initial write and even high
for file amendments. When replicating between two nodes in a cluster, with shared clustered storage the solution manages a weak 2,500 files per minute on initial write and only 260 files per minute when attempting to update data / amend files.
By testing various configurations we have effectively ruled out the SAN, the storage, drivers, firmware, DFSr configuration, replication group configuration - the only factor left that makes any difference is replicating from shared clustered storage, to another
shared clustered storage LUN.
So in summary:
Logical Volume ---> Logical Volume = Fast
Logical Volume ---> Clustered Shared Volume = ??
Clusted Shared Volume ---> Clustered Shared Volume = Pitifully slow
Can anyone explain why this might be?
The guidance in the article is in clear conflict with all other evidence provided around DFSr and clustering, however it seems to lean towards why we may be seeing a real issue with replication performance.
Many thanks for your time and any help/replies that may be received.
Paul

Hello Shaon Shan,
I am also having the same scenario at one of my customer place.
We have two FileServers running on Hyper-V 2012 R2 as guest VM using Cluster Shared Volume. Even the data partition drive also a part of CSV.
It's really confusing whether the DFS replication on CSV are supported or not, then what would be consequence if using.
In my knowledge we have some customers they are using Hyper-V 2008 R2 and DFS is configured and running fine on CSV since more than 4 years without any issue.
Appreciate if you can please elaborate and explain in details about the limitations on using CSV.
Thanks in advance,
Abul

OC4J 10.1.3 preview 4 cluster database replication is not working...

Hi,
We are trying to run OC4J 10.1.3 preview 4 standalone server in a cluster mode enabling database replication to persist session details during restarts.
We have created the following:
- JDBC Connection pool
- JDBC data source
- An entry in the application.xml for <cluster><protocol><.... </cluster>
But it does seem to be working.
And there is no change in stdout or stderr console log as well.
It will be really helpful if you send your comments or answers if anybody have have implemented this succefully before!!
Regards,
DGKM

gday DGKM --
I can confirm that this works with the DP4 build.
The easiest way to make sure you get the right entries are to configure this via the "clustering" wizard in Application Server Control at the end of the deployment process.
So I'd recommend deploying the application again using ASC and using the cluster task, setting the protocol to be Database and specifying the datasource to use.
cheers
-steve-

Broker/Cluster Message Replication

Similar Messages

Maybe you are looking for