A transactional message is sent to a non-transactional queue.
事务性消息被发送到非事务性队列中。
You cannot associate a transactional queue with a multicast address.
您无法使交易伫列与多点传送位址产生关联。
If the existing queue is not transactional, it is deleted and then recreated as a transactional queue.
如果现存的伫列不是可异动的，则会将它删除，并重新建立为异动的伫列。
Removes the current message from a transactional queue and returns the message to the calling application.
从队列中移除当前消息并将该消息返回给调用应用程序。
When an EJB component wants to access a database, a message queue server, or some other transactional resource, it acquires a connection to the resource manager (usually by using JNDI).
当一个EJB组件想访问数据库、消息队列服务器或者其它一些事务性资源时，它需要到资源管理器的连接(通常是使用JNDI)。
The RMs store the application state and are most often databases, but could also be message queue servers (in a J2EE application, these would be JMS providers) or other transactional resources.
资源管理器存储应用程序状态，常常是数据库，但也可能是消息队列服务器（在J2EE 应用程序中，它们将是JMS提供者）或其他事务性资源。
Distributed transactional support, so queue operations can participate in distributed transactions with other resource managers, such as SQL databases.
分布式事务支持，这样队列操作可以同其它资源管理器(如SQL数据库)一起参加分布式事务。
Moreover, the J2EE specification only recognizes three types of transactional resources -- JDBC databases, JMS message queue servers, and "other transactional services accessed through JCA."
而且，J2EE规范只认可三种类型的事务性资源 ―JDBC数据库、JMS消息队列服务器和“其它通过JCA访问的事务性服务”。
In the case of delivery failure for transactional messages, the message is sent to the transactional dead-letter queue on the source computer in all negative and in-doubt cases.
一旦事务性消息传递失败，则在所有否定的和不确定的情况下，消息将被发送到源计算机上的事务性死信队列。
In the case of delivery failure for transactional messages, the message is sent to the transactional dead-letter queue on the source computer in all negative and in-doubt cases.
一旦事务性消息传递失败，则在所有否定的和不确定的情况下，消息将被发送到源计算机上的事务性死信队列。
应用推荐