The following WARNing message may be observed in the DSA trace log:
What can we do to prevent this from happen again?
"rs_rsp: Credit limit reached"
The credits parameter provides a mechanism to govern how many client requests are outstanding at any given time for each association and to delay new requests.
The credit limit reached warning can be explained as:
"Setting the DSA credits to 5 (for example, via the limits configuration file) instructs the DSA that all user associations (meaning unique client IP address and port pairs) can have a maximum of 5 operations outstanding at any given time before the DSA will impose flow control."
If you are observing "Credit limit reached" warnings, increase the number of credits by a small amount, then stop and start the DSA's.
If you are still seeing the messages, then you may want to analyze the directory logs to see which connection (application or user) is causing the credit limit to occur.
You may need change the value to a bigger number if the problem persists.
Please check the current "credit" value in the dxserver\config\limit\default.dxc configuration file of the eTrust Directory server.
The setting is:
set credits = <the number>;
Credits are per "association" (which is a unique TCP connection), not per IP address. There is no "shared pool".
The maximum number of DSA operations in progress at the same time on a per user basis can be set using the credit limit, for example:
set credits = 5
To determine the maximum number of concurrent operations you can perform, multiply the number of credits by the maximum number of users.
When the credit value is exceeded, the DSA delays the receipt of any new requests from the DUA (client).