Require to set timeout on JMS Send Queue and Receive Queue so that messgae will be lost and no thread will be available to read it

We identified there is a setting at Queue settings in console for WAS where time-to-live is present , can we use it to set timeout at Queue level at JMS level so that response message from downstream system will not be read or written to receive queue . All we need is to timeout from the interaction with downstream system as soon as the timeout value has reached at queue level .Once this happens when the response message from downstream comes in both the queues must have timed out and not hread must be waiting to read the response .Can you please help us to achieve this ?

Related:

Event ID 2256 — Message Queuing Operation

Event ID 2256 — Message Queuing Operation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing operation provides message authentication, message encryption, dead-letter queues, security settings, and other basic features. If Message Queuing has problems with any of these features, proper Message Queuing operation may suffer.

Event Details

Product: Windows Operating System
ID: 2256
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_WARN_DEADLETTER_QUEUE_NOT_TRANSACTIONAL
Message: The message could not be moved to deadletter queue %1. The deadletter queue needs to be transactional. The message will be moved to the system transactional dead letter queue.

This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2256 registry value to desired time in seconds.

Resolve
Make the per-app dead-letter queue transactional or the messages being sent to it nontransactional

The dead-letter queue that is specified in the event is nontransactional, but there are transactional messages trying to go there.

To allow messages to go to the dead-letter queue, recreate the dead-letter queue as a transactional queue, or if you have control over the messages that are being sent to the queue, ensure that the messages are nontransactional.

To recreate the dead-letter queue as a transactional queue, create a new transactional queue with all the same properties as the original dead-letter queue, but make the new queue transactional.

For more information about creating queues, see Create Queues (http://go.microsoft.com/fwlink/?LinkId=104735).

Verify

Verify that the MSMQ Service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the MSMQ Service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Locate the Message Queuing service, and confirm that the value in the Status column is Started.

Related Management Information

Message Queuing Operation

Message Queuing

Related:

This device is already in use as a communication device.

Details
Product: Windows Operating System
Event ID: 2343
Source: System
Version: 5.0
Symbolic Name: NERR_CommDevInUse
Message: This device is already in use as a communication device.
   
Explanation

This message should occur only on a workstation. Any action to correct the problem should be performed on that computer. This device is used with a communication-device queue. You cannot use a device with both communication-device queues and printer queues.

   
User Action

To use this device with a printer queue, you must disconnect all communication-device queues from it.

Related: