Kbase P120409: Database started through Progress Explorer defaults number of remote servers to 4
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/4/2007 |
|
Status: Verified
SYMPTOM(s):
Database started through Progress Explorer defaults number of remote servers to 4
number of servers (-Mpb) is not defined in Progress Explorer defaultServerGroup
number of servers (-Mpb) is set to 4 on database startup
Maximum servers (-Mn) slots are allocated at startup
promon shows that Maximum servers (-Mn) slots are not all used
dbman -start -db name does not allow use all remote servers
database started from cmd line (proserve) uses all remote server slots allocated at startup
CAUSE:
When a database is started with the AdminService, and the -Mpb parameter is left undefined: the -Mpb parameter is always set to the default value (4) based on the default value of -Mn known to the AdminService and not the value of -Mn (for example, 10) set in the custom.pf used on OtherArguments. This results in all the -Mn server process slots being defined (10), but not being able to be used as -Mpb (4) limits 4 remote servers per login broker.
When -Mpb is NOT defined:
- in the cmd line, remote servers (ie -Mpb) are allocated on demand as needed up to value of -Mn
- in the Progress Explorer, ie left at value zero. -Mpb is set to 4.
This is an anomily between the two methods, which has existed for quite some time. It has been logged with our development to review.
FIX:
Explicitly define -Mn and -Mpb to ensure that your configuration for remote connections is set as you have designed it
In Progress Explorer:
-Mpb is explicitly set in the:
<right click> defaultServerGroup <Properties> > number of servers
where, -Mn is set in the:
<right click> defaultConfiguration <Properties> > General [TAB] > Maximum servers