Kbase P39810: -m3 is not recognized in the -PF file within procontrol but
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/03/2004 |
|
Status: Unverified
SYMPTOM(s):
The -m3 parameter is not recognized in a -pf file called from within ProControl.
Could not connect to server for database <dbname>, errno 0. (1432)
The secondary broker appears to be started but it's not.
Promon does not show its existence nor can you connect via its port.
The command that works in ProControl is -m3 -pf dbname.pf
If started from the command line the -m3 can be used in the -pf file.
The -m3 parameter is the parameter to startup the secondary broker.
The -pf file is composed of parameters to apply to the secondary broker.
The registry lists what is place on the startup line in ProControl.
CAUSE:
In our source code it appears that the problem is with the ProControl code that
verifies whether the -m3 parameter is in the Startup parameters, to decide if
a secondary broker for the database should be started or not.. Since the
parameter is in the .pf file, this check will fail and ProControl won't
even start the process..
It is working as designed.. A code change to look at a pf
files could possibly be done, but the thought is that they will not do any changes to ProControl at this time..specially with such an easy workaround.
FIX:
The startup parameter for the secondary broker (-m3) needs to be outside of any pf file when configured within ProControl.