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.
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

Similar Messages

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!

Any way to communicate a message to all cluster members?

Is there any way I can communicate a message to all cluster members?
          In my case I do some data caching within each cluster member. I'm trying to
          implement a mechanism that will enable me to have every server flush their
          cache. I was hoping that I could send the request to a servlet (on any
          machine) that in-turn would send a 'multicast' message to all app servers
          that would request a cache refresh.
          Any ideas?
          Thanks.
          Marko.


JMS topics are great for multi-server synchronization.
          Marko Milicevic <[email protected]> wrote in message
          news:39dba2e7$[email protected]..
          > Is there any way I can communicate a message to all cluster members?
          > In my case I do some data caching within each cluster member. I'm trying
          to
          > implement a mechanism that will enable me to have every server flush their
          > cache. I was hoping that I could send the request to a servlet (on any
          > machine) that in-turn would send a 'multicast' message to all app servers
          > that would request a cache refresh.
          >
          > Any ideas?
          >
          > Thanks.
          >
          > Marko.
          > .
          >
          >

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

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

JMS Ordered Messaging in a cluster

Just a question pertaining to message ordering for Weblogic 8.1 JMS.
          We want to maintain ordered messages in the case of a Weblogic cluster. We want to use a publish / subscribe model and have the ordered guaranteed for any consumer subscribing to the topic.
          Is this possible? The JMS documentation seems to imply that it is using distributed destinations. Is this the way to configure it?
          Thanx,
          GB

Hi,
          I'm assuming the distributed destination members are running in the same cluster as the MDB, so that when you kill the server that hosts the MDB you are also killing the destination.
          Messages that are in a destination that is shutdown, killed, etc, can not re-appear until the destination is restarted. If you want the messages to re-appear, either (A) restart the server that hosts the destination, or (B) use WebLogic's migration framework feature to migrate the JMS server, JTA service, and persistent store from the failed WebLogic server to a running WebLogic server. The former can be automated via the "whole server migration" feature, and the latter can be fully automated in the next upcoming release via "automatic service migration". The next release is available in beta, and is currently scheduled for GA mid-year (no promises!).
          Tom

Message Bridge to Cluster

Hey guys,
I'm trying to configure a message bridge to a cluster of servers. When configuring the destination portion of the bridge, I entered server 1 connection url and messages went to that one server. I shut the server down to see if the bridge would send messages to any of the other servers and it didn't.
So in the destination bridge connection url I entered all the addresses of the servers in the cluster and got the following error when restarting the JMS server:
<Feb 22, 2010 2:00:09 PM EST> <Warning> <Connector> <BEA-190032> << eis/jms/WLSC
onnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter
on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.R
esourceException: ConnectionFactory: failed to get initial context (InitialConte
xtFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:9015,t3:/
/localhost:9016,t3://localhost:9017, user name = null) ">
Do I need a separate bridge for each server or how would I configure the bridge to randomly pick a server to send message to?
In the cluster there is a distributed queue module targeted to all the machines in the cluster.
Thanks for viewing and any helpful replies

Changed the connection url to the cluster url address fixed problem :)
But its still not working :(
Think the problem now is my cluster jms server. It's currently targeted to my first server in the cluster, which is the one I'm shutting down. In the articles I've read supposely the jms sever will move to another server within the cluster?
Help!
Thanks

RPC calls and multicast messages in oc4j cluster

Hi, our application uses RPC calls, which are distributed over multicast messages (jgroups). We use RPC calls to update internal object cache, which exists on each cluster instance. The OC4J instance, which sends the message, successfully receives these and executes the RPC call. The other OC4J instance does not get the message or cannot execute the RPC call. I don't know whether reception of multicast messages is not possible and/or the RPC call is not possible (safety reasons). The same implementation does work with other app. server like Bea Weblogic 8.1.

Scrap JMS. Use plain java.net or JINI.
You could create a Peer-to-Peer Chain:
Server A -> Server B -> Server C -> Server A
On each Server have a server listening for messages (from the Server to the left in the chain) and a client that sends messages (to the Server to the right in the chain) and an application that links the server and client on each Server.
So,
Server A's "server" listens for messages from the "client" on Server C, and so on.
This is vary efficent. A simple send-receive chain that is clusterd within a small (or large) group of Servers. You could also try Bi-Directional Parallel Communications BDPC. That would basically have Server A send messages to both Servers - one to the left and one to the right, then at the same time, listen for messages from the Server on the left and the Server on the right. This is better suited for large-scale clusters where a Uni-directional communications model would take too long to propogate messages to every member of the group.
But, that's just me.

Informational TX messages in a cluster

I have a 2 server cluster running, servers 140 and 142. On server 140, I
          see these types of informational messages that seem to be reported by 142.
          Mon Jan 22 08:25:17 EST 2001:<I> <TX> Transaction (TxC (22523839, xid =
          979924549690_137, timeout = 30, txState = Marked Rollback, roo
          t = 2233880269814797780S258.39.94.142:[7001,7001,7002,7002,7001,-1]/3923)
          rolled back after 30 sec.
          Question, what causes these types of messages to be reported? Is this
          cluster specific?
          TIA,
          Jim Clark
          www.idea.com


We are having the exact same situation occur in our setup. What makes it
          weird for us is that we basically migrated from a single non-clustered
          instance to a clustered server with 2 instances. Before we enable
          clustering we never got such errors. No other exception is printed out in
          either instance. We are calling a bean method (which accesses other beans
          and and RMI object) when a client logs in and the client gets on without any
          problems. The only thing we are seeing is those exception messages.
          Any ideas what could be causing this?
          Thanks,
          Sergio
          "Cameron Purdy" <[email protected]> wrote in message
          news:[email protected]...
          > It sounds like a transaction is marked for rollback (set rollback only)
          but
          > not rolled back (throw a runtime exception).
          >
          > --
          > Cameron Purdy
          > Tangosol, Inc.
          > http://www.tangosol.com
          > +1.617.623.5782
          > WebLogic Consulting Available
          >
          >
          > "Jim Clark" <[email protected]> wrote in message
          > news:[email protected]...
          > > I have a 2 server cluster running, servers 140 and 142. On server 140,
          I
          > > see these types of informational messages that seem to be reported by
          142.
          > >
          > > Mon Jan 22 08:25:17 EST 2001:<I> <TX> Transaction (TxC (22523839, xid =
          > > 979924549690_137, timeout = 30, txState = Marked Rollback, roo
          > > t =
          2233880269814797780S258.39.94.142:[7001,7001,7002,7002,7001,-1]/3923)
          > > rolled back after 30 sec.
          > >
          > > Question, what causes these types of messages to be reported? Is this
          > > cluster specific?
          > >
          > > TIA,
          > > Jim Clark
          > > www.idea.com
          > >
          > >
          > >
          >
          >

Messaging Bridge and cluster problem

I am trying to setup the Messaging Bridge between MQ and WLS. Originally, we were going to use the Foreign JMS setup but the loss of transactionality was an issue (QManager cannot be assumed to be on the same box as our cluster). So we moved to the Messaging Bridge in the hopes that it will provide greater stability.
          I am following the example provided here https://messaging-bridge.projects.dev2dev.bea.com/ and setting up 2 JMS Destinations. Setting up the MQ Destination was trivial given that I had done it already with the Foreign JMS setup.
          But the destination that points to the internal WLS JMS Queue is a little trickier given that we are using clusters. I am stuck trying to figure out what Connection URL I should be using. According the the example above, I should use t3://localhost:7001 but in a clustered setup, what do I point to?

I finally got my Messaging Bridge (Tibco to a WLS Cluster) to work. See my post 3 messages before yours - to which no-one responded... :-(
          So here goes with my suggestion based on what I have done.
          1. Create a Distributed Destination for the WLS queue and "auto deploy" it your cluster. (Read the manual on how to do that, it is quite straightforward).
          2. In the Local Bridge Destination, put :
          Connection URL - nothing
          Initial Context Factory - weblogic.jndi.WLInitialContextFactory
          Connection Factory JNDI Name - <your JMS conection factory name>
          Destination JNDI Name - <the JNDI name given to the Distributed Destination>.
          I hope that works.
          Andy

Recommendations for a 2-Node Messaging 6.3 Cluster

Hi all, I'm in the process of building a 2-node cluster to run Messaging Server 6.3 and would like your help. My question is in regard to the layout of the messaging software. For example, should I install the messaging binaries on each node of the cluster and store the configuration/data files on shared storage or store the messaging binaries AND the configuration/data files on the shared storage?
Is the any preferred approach to building a messaging cluster?
Thanks in advance,
Stewart

Hi,
mcleans wrote:
Hi all, I'm in the process of building a 2-node cluster to run Messaging Server 6.3 and would like your help. My question is in regard to the layout of the messaging software. For example, should I install the messaging binaries on each node of the cluster and store the configuration/data files on shared storage or store the messaging binaries AND the configuration/data files on the shared storage?Information on installing messaging with cluster here:
http://blogs.sun.com/SC/entry/java_messaging_server_6_3
http://www.sun.com/bigadmin/features/hub_articles/message_srvr_cluster.pdf
Regards,
Shane.

Publising message in weblogic cluster

Hi all,
          Is it possible to publish a message to all servers in weblogic clustering?
          Hope to receive suggestions.
          Plad

You can use a single standard JMS topic, running on one server for the purpose. And subscribe to this topic from all servers (usually via an MDB).
          Similarly, for scaling/HA purposes, you can use WL JMS' distributed topic feature. This is a single logical topic that is that is physically hosted on multiple servers.
          For a list JMS' features, documentation, and recommended books start here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          Tom

Error message when accessing Cluster Manager (Windows Server 2012-based) console from a Windows 8 system

Hi all;
Please look at the following figures:
Any ideas?
Thanks
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Hi,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Node failed to join the cluster because it ould not send and receive failure detection network messages

One of my customers has a Windows Server 2008 R2 cluster for an Exchange 2010 Mailbox Database Availability Group. Lately, they've been having problems with one of their nodes (the one node that is on a different subnet in a different datacenter) where
their Exchange databases aren't replicating. While looking into this issue it seems that the problem is the Network Manager isn't started because the cluster service is failing. Since the issue seems to be with the cluster service, and not Exchange,
I'm asking here.
When the cluster service starts, it appears to start working, but within a few minutes the following is logged in the system event log.
FailoverClustering
1572
Critical
Cluster Virtual Adapter
Node 'nodename' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. ...
It seems that the problem is with the 169.254 address on the cluster virtual adapter. An entry in the cluster.log file says: Aborting connection because NetFT route to node nodename on virtual IP 169.254.1.44:~3343~ has failed to come up.
In my experience, you never have to mess with the cluster virtual adapter. I'm not sure what happened here, but I doubt it has been modified. I need the cluster to communicate with its other nodes on our routed 10. network. I've never experienced
this before and found little in my searches on the subject. Any idea how I can fix this?
Thanks,
Joe
Joseph M. Durnal MCM: Exchange 2010 MCITP: Enterprise Messaging Administrator, Exchange 2010 MCITP: Enterprise Messaging Administrator, MCITP: Enterprise Administrator

Hi,
I suspected an issue with communication on UDP port 3343. Please confirm the set rules for port 3343 on all the nodes in firewall and enabled all connections for all the profiles
in firewall on all the nodes are opened, or confirm the connectivity of all the node.
Use ipconfig /flushdns to update all the node DNS register, then confirm the DNS in your DNS server entry is correct.
The similar issue article:
Exchange 2010 DAG - NetworkManager has not yet been initialized
https://blogs.technet.com/b/dblanch/archive/2012/03/05/exchange-2010-dag-networkmanager-has-not-yet-been-initialized.aspx?Redirected=true
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Messages in Broker cluster

Similar Messages

Maybe you are looking for