By default when a request / reponse operation is invoked via an import with a SOAP / JMS binding the runtime creates a temporary queue for the response .

默认情况下，当通过带有SOAP/JMS绑定的导入调用请求/响应操作时，运行时创建一个 临时的响应 队列。

Imports don 't use an MDB to receive responses and can be configured to use a single reply queue or one temporary reply queue per request .

导入并不使用MDB接收响应，可以将其配置为对每个请求使用单个应答队列或者一个 临时应答 队列。

The SOAP / JMS binding then waits for a response message to be put on the temporary reply queue and finally discards the queue once the reply has been read .

SOAP/JMS绑定然后等待将一条响应消息放在 临时回复 队列上，最后在读取回复后丢弃该队列。

Imports do not use an MDB to receive responses and can be configured to use a single reply queue or one temporary reply queue per request via the JMS URL specified for the import binding in the WebSphere Integration Developer tool .

导入不使用MDB来接收响应，可配置为通过在WebSphereIntegrationDeveloper工具中为导入绑定指定的JMSURL，使用单个回复队列或为每个请求使用一个 临时回复 队列。

Temporary queues are not able to hold persistent messages so if you need a permanent reply queue to be used by an import for this or other reasons it is possible to identify the queue to be used via the URL configured on the import binding .

临时队列无法保存持久消息，所以，如果出于这种原因或其他原因需要一个用于导入的永久回复 队列，可以将队列标识为通过在导入绑定上配置的URL来使用。

It aggregates multi-aspect factors to adjust self-adaptively such as average length of request queue temporary length of request queue the relations of every request and the loading etc.

该算法综合了平均请求队列长度、 瞬时请求 队列长度、请求之间的关系以及负载情况等多方面的因素自适应调整。

The temporary backout queue that comes into play if there are transaction failures ( ERRORQ )

如果存在事务故障，则使用 临时回滚 队列（ERRORQ）

With extra care in closing connections that created the temporary queue it is a good solution .

如果在关闭创建 临时 队列的连接时格外小心的话， 临时 动态 队列是一个不错的解决方案。

This option allows a temporary queue to be recreated to store the response for each request that is sent through the import .

这个选项允许重建一个 临时 队列来存储通过导入发送的每个请求的响应。