10 windows client networking, 1 windows appserver, 1 centos db server with db1, and db2.

the situation is this. (proof of concept)

Implemented a sort of message queue. Client station1 puts on db1.queuetable a record, and client2, and client3,and so... up to 10 client networking.

one station has a schelduled task to call a batch to connect to appserver, every 3 minutes and download queuetable records to a handler connected to db2. I don't want every user to connect to this db2.

The problem came from a locked record on this handler, so it waited, but client station spaned another batch, and another, and another, as to workgrup database rejects further connections.

While I fix dispatcher's blocking contidition, I don't want to spawn so much appserver agents, as this load brings db server to its knees. And as it is a "message queue" I don't care if appserver uses only 2 agents for this task and queue is put long wait, as labor ends 4 pm, and from that time to 5, it will send to appserver all records without interfering with users...

So i wonder, wich parameter on appserver instance, would allow me to restrict how much resources it consumes... (agents or servers?)...

Thans

state-free instance...

In OpenEdge Application Server: Administration (11.7) page 62:

Managing AppServer agents

In general, you can manage running AppServer agents based on the Server Pool Parameter settings as follows:

• You can trim any number of running AppServer agents below your Minimum Server Instances parameter

value to zero.

• You cannot add any more AppServer agents than your Maximum Server Instances parameter setting.

However, once you have found the maximum number of AppServer agents that you can run productively

for the AppServer, you might even want to set that value lower if the setting negatively impacts other tasks

on the system.

Default seems to be:

maxSrvrInstance=10