The queue manager will do what it's designed to do - send/receive messages etc. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
the restart behavior of a queue manager that belongs to a cluster is *exactly* the same as the restart behavior of a queue manager that is not in a cluster.
The behavior of cluster channels when one end disappears is *exactly* the same as the behavior of non-cluster channels when one end disappears.
the restart behavior of a queue manager that belongs to a cluster is *exactly* the same as the restart behavior of a queue manager that is not in a cluster.
The behavior of cluster channels when one end disappears is *exactly* the same as the behavior of non-cluster channels when one end disappears.
If we restart the cluster qmgr any impact will occurs at MQ level or app level
the restart behavior of a queue manager that belongs to a cluster is *exactly* the same as the restart behavior of a queue manager that is not in a cluster.
The behavior of cluster channels when one end disappears is *exactly* the same as the behavior of non-cluster channels when one end disappears.
If we restart the cluster qmgr any impact will occurs at MQ level or app level
What is the impact if you restart a queue manager that is not part of a cluster?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum