Win2k server progress 9.1d08, 25 databases, 25 4gl brokers and 25 sql brokers.
4gl: -m3 -Mpb 5 -N tcp -S [service name] -L 100000
sql: -Mn 9 -Mpb 4 -N tcp -S [service name] -L 100000
Now I get a new error after the 4am scheduled task restarts the broker, and a single users tries to connect:
04:00:38 BROKER 1: Started for ap5serv using tcp, pid 3460. (5644)
10:26:16 SRV 2: Started on port 3033 using tcp, pid 3932. (5646)
10:26:17 SRV 2: Login usernum 29, userid xxxxxxx, on xxxxxxxx. (742)
11:29:36 BROKER 1: Broker could not spawn a server. (1157)
11:50:12 BROKER 1: Broker could not spawn a server. (1157)
11:54:12 BROKER 1: Broker could not spawn a server. (1157)
11:58:12 BROKER 1: Broker could not spawn a server. (1157)
Progress support says:
"In the shared memory networking model of PROGRESS, the broker was trying to spawn a server and the spawned process died before it had a chance to notify the broker that it was alive. This can happen for any number of reasons -- the host machine could be out of available processes, or available ports or network connection points, or the shared memory versions between broker and server don't match, or there are not enough semaphores for the new server etc."
Anybody else ever have this error, and if so, what did you do to prevent it? I'm not sure what the "out of processes" bit means, I can start all kinds of processes locally on the server, and there are tons of available ports. Not sure how to check the availability of semaphores though.
4gl: -m3 -Mpb 5 -N tcp -S [service name] -L 100000
sql: -Mn 9 -Mpb 4 -N tcp -S [service name] -L 100000
Now I get a new error after the 4am scheduled task restarts the broker, and a single users tries to connect:
04:00:38 BROKER 1: Started for ap5serv using tcp, pid 3460. (5644)
10:26:16 SRV 2: Started on port 3033 using tcp, pid 3932. (5646)
10:26:17 SRV 2: Login usernum 29, userid xxxxxxx, on xxxxxxxx. (742)
11:29:36 BROKER 1: Broker could not spawn a server. (1157)
11:50:12 BROKER 1: Broker could not spawn a server. (1157)
11:54:12 BROKER 1: Broker could not spawn a server. (1157)
11:58:12 BROKER 1: Broker could not spawn a server. (1157)
Progress support says:
"In the shared memory networking model of PROGRESS, the broker was trying to spawn a server and the spawned process died before it had a chance to notify the broker that it was alive. This can happen for any number of reasons -- the host machine could be out of available processes, or available ports or network connection points, or the shared memory versions between broker and server don't match, or there are not enough semaphores for the new server etc."
Anybody else ever have this error, and if so, what did you do to prevent it? I'm not sure what the "out of processes" bit means, I can start all kinds of processes locally on the server, and there are tons of available ports. Not sure how to check the availability of semaphores though.