No, there is no parameter for regulating packet size for the client to the AppServer.
In order to
decrease the traffic between the Progress client and the Appserver, the Progress 9.1D08 service pack introduced a new client switch (-mc) that allows the message between the client and the AppServer to be compressed.
The message compression startup switch, "
-mc", should be set only for Progress clients talking to compatible AppServers:
In order to throttle the amount of data transmitted from the producer (AppServer agent) to guard against Java heap exhaustion, the maximum queue size can be configured with the queueLimit parameter in the ubroker.properties file.
- When the queueLimit property is restricted, it causes the producer (aka the AppServer server) thread to block once the maximum number of messages has been added to the queue, thereby allowing the consumer (aka client process) to dequeue the messages. As messages are removed from the queue by the consumer thread, the producer thread again able to enqueue messages until the limit is reached and the process repeats as needed.
- Every environment / application is different, the size of table contents is different, the number of consumers is different, the network hardware or topology is different. As these factors all play a part in the flow of data from producer to consumer there is no one-size-fits-all value that can be stated on how this queueLimit value should be set.
- Setting the queuelimit too high may allow the queue to build up and allow the out of memory to occur.
- Performance may be affected when using queueLimit but exact amounts can vary widely.
- It is advised to use the queuelimit parameter with OpenEdge 11.3.3 Service Pack, 11.4.0 or later. For further information refer to Article QueueLimit set to a finite value on AppServer message queue may cause dead lock scenario.
