是一种面向数据流的活动队列管理算法。
An active queue management algorithm for flows called MBUE is proposed.
然后，客户端自动重新连接到活动队列管理器。
The client was then automatically reconnected to the active queue manager.
下面，必须删除所有活动队列管理器服务器上的队列管理器。
Next, you must delete the queue manager on all active queue manager servers.
首先，您需要验证正在运行活动队列管理器的服务器，方法是运行dspm q- x命令。
First, you need to verify the server on which the active queue manage is running; this can be achieved using the DSPMQ -x command.
WebSphereMQExplorer现在将连接到活动队列管理器实例，如图6所示。
WebSphere MQ Explorer will now connect the active queue manager instance, as illustrated in Figure 6.
当某个活动队列管理器失败或变得不可用时，JMS应用程序会自动重新连接到备用网关队列管理器。
Automatic reconnect for JMS applications to a standby gateway queue manager when an active queue manager fails or becomes unavailable.
现在，队列管理器已经启动，可以创建和启动队列管理器侦听器，以便应用程序连接到活动队列管理器IBMESBQM，如清单13所示。
Now that the queue manager has been started, you can create and start the queue manager listener for applications to connect the active queue manager IBMESBQM, as shown in Listing 13.
下面，您需要提供活动和备用队列管理器的连接细节，指示WebSphereMQExplorer在故障转移时自动重新连接活动队列管理器。
Next, you will need to provide connection details for the active and standby queue managers, and instruct WebSphere MQ Explorer to auto-reconnect to the active queue manager in case of a failover.
第二种方法是同时停止队列管理器的活动和备用实例。
The second is to stop both the active and the standby instances of the queue manager.
之后您可以在不同机器上定义并启动此队列管理器的多个实例，包括一个活动实例和一个备用实例。
You can then define and start multiple instances of this queue manager on different machines, with one active instance and one standby instance.
只有以下两个队列管理器实例可以同时运行：活动实例和备用实例。
Only two queue manager instances can run at the same time: an active instance and a standby.
这里描述的系统包含一个活动代理或队列管理器实例和一个备用实例。
The systems described here have included one broker or queue manager instance that is active and one standby.
首先获得队列管理器数据的独占访问权的实例将成为活动实例。
The first instance to acquire exclusive access to the queue manager data becomes the active instance.
在运行命令来停止mi队列管理器的活动实例之前，重要的是要先识别正在运行活动实例的服务器。
Before you issue the command to stop the active instance of the MI queue manager, it is important to identify the server on which the active instance is running.
如果使用持久化事件或活动，一定要记得调优mq队列管理器来优化日志。
If you're using persistent events or actions, it's important to tune the MQ queue manager to optimise logging.
它可以锁定队列管理器数据，确保队列管理器中只有一个活动实例。
It holds a lock on the queue manager data to ensure that there is only one active instance of the queue manager.
启动Server1 中队列管理器的活动实例
队列管理器：活动实例。
如果在队列管理器的活动实例上执行endmqmIBMESBQM命令—您将注意到，没有-s选项—将同时停止活动和备用实例。
If you issue the command endmqm IBMESBQM on the active instance of the queue manager — without, as you will note, the -s option — you will stop both the active and the standby instances.
如果在队列管理器的活动实例上执行endmqmIBMESBQM命令—您将注意到，没有-s选项—将同时停止活动和备用实例。
If you issue the command endmqm IBMESBQM on the active instance of the queue manager — without, as you will note, the -s option — you will stop both the active and the standby instances.
应用推荐