Gets a value that indicates whether the queue accepts only transactions.
Assembly: System.Messaging (in System.Messaging.dll)
An error occurred when accessing a Message Queuing method.
Transactional messaging refers to the coupling of several related messages into a single transaction. Sending messages as part of a transaction ensures that the messages are delivered in order, delivered only once, and successfully retrieved from their destination queue.
If a queue is transactional, it accepts only messages that are sent as part of a transaction. However, a non-transactional message can be sent or received from a local transaction queue without explicitly using transactional Begin, Commit, and Abort syntax. If a non-transactional message is sent to a transactional queue, this component creates a single-message transaction for it, except in the case of referencing a queue on a remote computer using a direct format name. In this situation, if you do not specify a transaction context when sending a message, one is not created for you and the message will be sent to the dead-letter queue.
If you send a non-transactional message to a transactional queue, you will not be able to roll back the message in the event of an exception.
MessageQueueTransaction is threading apartment aware, so if your apartment state is STA, you cannot use the transaction in multiple threads. Visual Basic sets the state of the main thread to STA, so you must apply the MTAThreadAttribute in the Main subroutine. Otherwise, sending a transactional message using another thread throws a MessageQueueException exception. You apply the MTAThreadAttribute by using the following fragment.
<System.MTAThreadAttribute> public sub Main()
The following table shows whether this property is available in various Workgroup modes.
Local computer and direct format name
Remote computer and direct format name