Kbase P113327: 4GL-JMS: setFlowToDisk and getFlowToDisk methods not documented
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/02/2006 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.1x
SonicMQ
SYMPTOM(s):
4GL-JMS setFlowToDisk is not documented
4GL-JMS getFlowToDisk is not documented
OpenEdge Development: Messaging and ESB documentation does not document the 4GL-JMS API methods setFlowToDisk, and getFlowToDisk.
CAUSE:
This is a known issue being investigated by Development
FIX:
Flow To Disk Publishing is a new feature introduced SonicMQ 6.0. Flow to Disk allows the Broker to handle flow control by storing messages sent to a slow subscriber in the persistent storage mechanism. This feature can be turned on and off by the broker setting but can also be overridden by a Client session.
The feature is supported by OE10.1A Adapter for SonicMQ with the following 4GL-JMS API's:setFlowToDisk(): Overrides the Brokers default setting for Flow To Disk
getFlowToDisk(): Return the value of the Client Sessions Flow To Disk. This will always return 0 unless the session explicitly overrides the Brokers setting with a call to setflowToDisk
The following list the valid values and descriptions for the flowToDisk feature:0 (Broker setting) - The default setting, specifies that the broker setting of FLOW_TO_DISK will be used for the subscriber.
1 (ON) - Sets FLOW_TO_DISK on for the subscriber despite the broker setting.
2 (OFF) - Sets FLOW_TO_DISK off for the subscriber despite the broker setting.
By Default, the Adapter for SonicMQ sets the Flow to Disk to 0 for the client sessions. This means that the client will follow the Brokers setting unless a session explicitly overrides the Brokers setting with setflowToDisk().
Only a subscriber can meaningfully set the Flow To Disk setting. If a session exclusively produces messages, calling the setFlowToDisk( ) method will have no effect.