2.
Take one or more of following actions:
•
Form a controller team and distributing ownership of the switches in the network across
the team members such that each controller in the team controls one third of the switches
in the network.
•
Increase the system resources, such as the number of file descriptors, on the system
on which the controller is installed.
•
Install the controller on a larger system, such as one that conforms to the hardware
recommendations appropriate to the size of the network deployment.
Application management errors
Application not starting and in disabled state
Symptom
An application cannot start and is automatically moved to the
DISABLED
state.
Cause
The Application Management framework detected a failure to start an application in the OSGi
runtime environment.
Action
1.
Correct the OSGi runtime conditions.
2.
Enable the application via the GUI or a REST call.
Application in transitive state
Symptom
An application is in a
transitive
state.
Cause
An unexpected error condition occurred when manipulating an application (such as file I/O
exception or missing files).
Action
1.
Examine the log files for exceptions, determine the source of error and correct.
2.
Uninstall the application. An application can only be uninstalled when it is trapped in a
transitive
state.
3.
Upload the application.
4.
Install the application.
Application management exceptions
Getting IllegalStateException: HTTP code 500
Symptom
Getting
IllegalStateException
, HTTP code: 500.
Cause
Pushing a meter or group mod to a connected switch from a controller that is not an owner will
not return the proper error message if the switch returns an error.
Application management errors
159