几乎在每个服务器应用程序中都会出现线程池和工作队列问题。
In nearly every server application, the question of thread pools and work queues comes up.
现在只有一个队列管理器实例正在运行，如果出现问题，将不会再有任何故障转移。
Now there is only one instance of the queue manager running, and there would not be any failover if problems arise.
本文讲解了如何解决在迁移集群队列管理器过程中涉及的一些主要问题。
This article explained how to deal with some of the major issues involved when migrating cluster queue managers.
随后，脚本大约每周一次地通过电子邮件发送一份遵从性报告，使我能够了解网络上的哪些队列管理器存在需要关注的配置问题。
Then, about once a week the script e-mails a compliance report letting me know which queue managers on the network, if any, have configuration issues I need to look at.
为每个队列管理器创建和分配一个死信队列，并使用它来捕获由于网络或目的地问题而未发送的消息，这是一个很好的实践。
It's a good practice to create and assign one for each queue manager and use it to catch messages that are not sent due to network or destination issues.
如果您想完全避免冲突问题，请为您的发起队列选择一个不以system开始的名称。
If you want to avoid this problem altogether, choose a different name for your initiation queue that does not begin with SYSTEM.
如果我们真的要遵循“经验法则”，那么我对您的问题提出两条建议：伸缩系统和调整组件队列。
If we really want to play the "Rule of Thumb", I have two recommendations to address your problem: scaling the system and tuning the queue of components.
制定迁移计划时，需要考虑常见队列管理器迁移问题、集群细节、更广泛的系统架构和更改控制策略。
When creating the migration plan, you need to consider general queue manager migration issues, clustering specifics, wider system architecture, and change control policies.
对所有对象全部使用大写，包括队列管理器，以防止在异构环境中出现可移植性问题。
Use full UPPERCASE for all objects, including the queue manager, to prevent portability issues in heterogeneous environments.
对于该模型的一个关键问题是增加工作线程数会加剧对工作队列的争用(如图3所示)。
A key problem with this model is that increasing the number of worker threads increases the contention on the work queue (this is shown in Figure 3).
无论测试和生产的计划和环境是否一致，总是会在迁移生产集群队列管理器时发现问题。
Whether or not the plans and environments for test and production differ, it is always possible to find problems when migrating the production cluster queue managers.
在大多数用例中，这是理想的行为，并被视为一个调优问题：增加maxdepth值，直到队列能吸收最高峰值负载。
In most cases, this is the desired behavior and is treated as a tuning problem: increase MAXDEPTH until the queue can absorb the highest peak loads.
另一方面，此服务可能拥有连接到队列管理器或访问其发起队列的相关问题。
On the other hand, the service might have problems connecting to the queue manager or accessing its initiation queue.
以前尝试解决此问题时通常都依赖于采用某种形式的数据存储区访问，如关系数据库或队列。
Previous attempts at solving this problem have generally relied on some form of access to a data store, such as a relational database or queue.
尽管这个基本模式比较简单，但可以通过将队列和线程池连接在一起，以便将这个模式用于解决各种各样的问题。
While this basic pattern is relatively simple, it can be used to solve a wide number of problems by chaining queues and thread pools together.
消息队列系统通过允许消息一直存储到接收系统变为可用为止，隐藏了可用性问题。
A message queuing system can also hide availability problems by allowing messages to be stored until the receiving system becomes available.
解决老鼠和大象的问题至少要求不同类型的消息通过不同的通道和传输队列。
Solving the mice and elephants problem requires, at a minimum, that the different types of messages pass through different channels and transmit queues.
本示例省略了队列的实际处理过程，因为它特定于您的需求，并涉及到许多微妙的并发性问题。
This example omits the actual handling of the queue because it's specific to your requirements and involves many concurrency subtleties.
然后，当我在斯德哥尔摩休假时，有机会参与了瑞典的双胞胎人员的登记工作，它是一个大型的队列研究项目，其中的一些研究人员正在着眼于认知的问题。
Then, when I was on a sabbatical in Stockholm, I had the opportunity to get involved with the Swedish Twin Registry, a large cohort study in which some researchers were looking at cognition.
第二个问题是，尽管异步事件处理程序是通过队列进行处理的，但一个队列有多个读取程序。
The second problem is that although asynchronous events are indeed processed through a queue, there are multiple readers of the queue.
回撤流程可能包括从集群移除或挂起队列管理器、向后迁移和在外部问题得到解决之前保持队列管理器离线。
The procedure could involve removing or suspending the queue manager from the cluster, backwards migrating, or keeping the queue manager offline until an external issue is resolved.
为了减轻该问题，您可以创建多个网桥队列、客户端连接、服务器连接通道以及同步队列。
To alleviate this problem, you can create multiple bridge queues, client connections, server connection channels, and sync queues.
显然，攻击客户机可以根据自己的喜好发送任何SACK选项，但不太容易看出的一个问题是，它可以轻易控制被攻击方的重传队列的长度。
An attacking client can obviously send any SACK option it likes, but less obviously, it can also easily control the size of the peer's retransmission queue.
但是在通常情况下，一种更好的解决此问题的方法是使用MQ集群技术，这将为每个应用程序服务器提供自己的队列管理器。
It would normally be better, though, to use MQ clustering techniques to achieve this, giving each application server its own queue manager.
这个SupportPac将检查一个队列管理器的SSL配置设置，也可以选择为客户端进行检查，并报告所发现的任何问题。
This SupportPac will examine the SSL configuration Settings for a queue manager and, optionally, for a client as well, and report on any issues that it finds.
向后迁移是降低现有队列管理器使用的WebSphereMQ版本的过程。如果完成向前迁移后遇到问题，就有可能需要执行向后迁移。
Backward migration is the process of downgrading the version of WebSphere MQ used by an existing queue manager, and you may need to use it if you encounter problems after a forward migration.
问题是这些变更还在Gerrit的评审队列里，我们要先批准这些变更。
The problem is, these changes are still in the review queue for Gerrit. We'll need to go there and approve them.
问题1：CouplingFacility列表结构和队列大小。
pl不工作时最明显的问题标志是队列总是设置为NOTRIGGER。
The most obvious sign of trouble when ChompQ.pl does not work is that the queue will remain set to NOTRIGGER.
这个改变引入一些索引，允许对大的重传队列中的元素进行随机访问，这个改变对于解决TCP协议栈的find - first攻击问题很重要。
A change that introduces some sort of index that allows access to random elements of the large retransmission queue is critical to address the find-first attacks against the TCP stack.
应用推荐