Consultor Eletrônico

Status: Verified

GOAL:

What are some reasons why a WebSpeed agent and/or AppServer server process hangs in STARTING mode with errors 8100 and 8525?

GOAL:

ERROR: cannot start server. (8100)

GOAL:

Exception unbinding broker (not bound) : <ExceptionMsg_string> (8525)

FACT(s) (Environment):

Progress/WebSpeed Versions

FIX:

There are a variety of reasons why an agent/server hangs in a prolonged STARTING state. Below are just a few generic items to review and/or look for when debugging these types of errors.

1. The agents are waiting on a TCP port. On AIX especially, this process can be very slow if there are a lot of ports in use in the ?minport to -maxport range. Verify and start each broker with a specific range of agents/servers -min and -max ports.

2. The agents are trying to connect to a database. If the database is not up and running, you have to wait for the timeout to occur before the agent dies. If the database is not up, start the database first, before starting agents/servers.

3. There is a lot of CPU usage during starting up. Due to the lack of CPU resources, agents/servers times out before it can finish startup.

4. Java memory, increase two JVM parameters for $JVMARGS;

ms - memory allocation pool
mx - heap size

JVMARGS="-Xms<value>m -Xmx<value>m"

Example:
JVMARGS="-Xms16m -Xmx256m"

Each WebSpeed and AppServer broker(s) consume 5M of memory. Unlike WebSpeed agents, each AppServer server, is a java thread and consumes at least 1M of memory each. Add &/or change JVMARGS underneath each
broker instance within the ubroker.properties file. Changing JVMARGS within java_env will change those values for all JAVA processes. It's best to set the values in the ubroker.properties file so you can change each broker independently, without effecting all the other brokers. If you make changes in the ubroker.properties it should override settings in the java_env file.