If your messaging system runs in non-Application Server Facilities (non-ASF) mode, you must configure the Total transaction lifetime timeout transaction service property and the NON.ASF.RECEIVE.TIMEOUT message listener service custom property correctly, to avoid unwanted transaction timeouts.
To carry out the steps in this task, your messaging system must be running in non-ASF mode. To change from ASF mode to non-ASF mode, add the NON.ASF.RECEIVE.TIMEOUT custom property to the message listener service as described in Configuring the message listener service.
If your messaging system is running in non-ASF mode, to avoid unwanted transaction timeouts, you must allow a sufficient amount of time for processing to be completed before the total transaction lifetime timeout is reached. Therefore, you must make sure that the value that you specify for the NON.ASF.RECEIVE.TIMEOUT message listener service custom property is smaller than the value that you specify for the Total transaction lifetime timeout transaction service property, and also that the difference between the values of the two properties is greater than the amount of time that the onMessage() method of the message-driven bean (MDB) takes to process the message.
In this information ...Related concepts
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |