Summary: Turning off JMS Application Server Facilities, which are not supported by GigaSpaces JMS.
Overview
GigaSpaces JMS does not currently support the "JMS Application Server Facilities" section 8 in the JMS 1.02 specifications, please "turn it off" when using WSAD 5.1.3 Generic JMS Provider (GS JMS).
To turn it off, define the custom property NON.ASF.RECEIVE.TIMEOUT with the value in milliseconds for the Timeouts of each receive/onMessage call.
See the following link for more details:
http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/umb_prolscp.html
NON.ASF.RECEIVE.TIMEOUT
This is the timeout in milliseconds for synchronous message receives performed by message-driven bean listener sessions in the non-ASF mode of operation.
Set this property to a non-zero value if you want to enable the non-ASF mode of operation for all message-driven bean listeners on the application server.
The message listener service has two modes of operation, Application Server Facilities (ASF) and non-Application Server Facilities (non-ASF).
- The ASF mode provides concurrency and transactional support for applications. For publish/subscribe message-driven beans, the ASF mode offers better throughput and concurrency, because in the non-ASF mode the listener is single-threaded.
- The non-ASF mode is mainly for use with generic JMS providers that do not support JMS ASF, which is an optional extension to the JMS specification. The non-ASF mode is also transactional but, because the path length is shorter than the ASF mode, it usually provides improved performance.
Use Non-ASF if:
- Your generic JMS provider does not provide JMS ASF support.
- You are using message-driven beans with WebSphere topic connections with the DIRECT port, because the embedded publish/subscribe broker utilizing that port does not support XA transactions or JMS ASF.
- Message order is a strict requirement.
| Data type |
Integer |
| Units |
Milliseconds |
| Default |
ASF mode (custom property not created) |
| Range |
0 or greater milliseconds
0
Non-ASF mode is disabled.
1 or more
The timeout in milliseconds for non-ASF message-driven bean listener synchronous session receives. |
| Recommended |
If a transaction timeout occurs, the message must recycle causing extra work. If you want to use the non-ASF mode, set this property to lower than the transaction timeout, but leave at least the maximum duration of your message-driven bean's onMessage() method as a spare. For example, if your message-driven bean's onMessage() method typically takes a maximum of 10 seconds, and the transaction timeout is set to 120 seconds, you might set the NON.ASF.RECEIVE.TIMEOUT property to no more than 110000 (110000 milliseconds, that is 110 seconds). |
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/umb_prols.html
Message Listener Service
The message listener service is an extension to the JMS functions of the JMS provider. It offers a listener manager that controls and monitors one or more JMS listeners. Each monitor becomes a JMS destination on behalf of a deployed message-driven bean.
This panel displays links to the Additional Properties pages for Listener Ports, Thread Pool, and Custom Properties for the message listener service.
To view this administrative console page, click Servers-> application_server-> Message Listener Service.
Custom Properties
These are the custom properties of the message listener service. The JMS server has two modes of operation: Application Server Facilities (ASF) and non-Application Server Facilities (Non-ASF). ASF supplies concurrency and transactional support for applications. Non-ASF, in contrast, bypasses that support so that it can streamline the path length.
Use Non-ASF if:
- Message order is a strict requirement.
- Concurrent PTP messages are desired.
- The property non.asf.receive.timeout exists and has a value greater than 0.
Do not use Non-ASF if concurrent publications and subscriptions messages are desired because ASF offers better throughput.
| Data type |
Integer |
| Units |
Milliseconds |
| Default |
ASF mode (custom property not created) |
| Range |
|
| Recommended |
The value is the number of milliseconds it takes for a message to be delivered. If a timeout occurs, it must recycle, causing extra work. Set this property to lower than the transaction timeout, but close to it with several (10 or more) seconds to spare. Make the spare seconds more if under extreme loads in which threads are waiting long periods of time to get their CPU cycles. |
Previous release
Add GigaSpaces wiki search to your browser search engines! 