Kbase P167600: Explorer will not allow Maximum Servers GT 512
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/06/2010 |
|
Status: Unverified
SYMPTOM(s):
OpenEdge Explorer will not allow an entry for Maximum Servers GT 512 to be saved
Invalid value for "max servers' property. Range is 1 .. 512. Default is 4
Progress Explorer will not allow entry for Maximum Servers GT 512.
dbconfig conmgr.properties error PRPMsg010
The following errors occurred whilst loading a property file: In group configuration.dbloan.defaultconfiguration": Invalid property value: "513" for property: MaxServers". (PRPMsg010)
Manually adding maxservers to the conmgr.properties works until the AdminServer is shutdown
No databases seen when AdminServer is restarted and maxservers in conmgr.properties is above 512
FACT(s) (Environment):
Windows
Progress 9.x
OpenEdge 10.x
CAUSE:
Known issue with both the Progress Explorer and OpenEdge Explorer products. There is no hardlimit on Maximum Servers, the value is only limited by available system resources.
FIX:
The following Workaround applies to whichever of the two UI (Progress Explorer or OpenEdge Explorer) are in use for managing the databases.
Workaround #1: Add the maximum servers database startup parameter (-Mn) to a pf file, then reference that .pf file in the Progress Explorer "Other Server Arguments"
Database starts despite the dbconfig error and takes the maximum servers (-Mn) value above 512
dbname
|_ Configurations
|__defaultConfiguration > PROPERTIES or EDIT > GENERAL: Maximum Servers <any_value LE 512) ; Other Server Arguments: -pf bigmn.pf
Then define -Mn > 512 in the pf file referenced in 'Other arguments'.
# bigmn.pf
-Mn 1024
The value in the .pf file will take precidense over the value set in the conmgr.properties. This can be verfied in the startup section of the related database lg file.