| |
** If the agent is incorrectly showing a state of offline, and the running man icon is not available, you can still initiate a connection by following the steps listed [http://wiki.urbancode.com/AnthillPro/Perform_Agent_Connection_Test here]. |
|
** If the agent is incorrectly showing a state of offline, and the running man icon is not available, you can still initiate a connection by following the steps listed [http://wiki.urbancode.com/AnthillPro/Perform_Agent_Connection_Test here]. |
| |
** If multiple agents are failing, you can try the restart broker option from the AHP UI. |
|
** If multiple agents are failing, you can try the restart broker option from the AHP UI. |
| |
|
+ |
* '''An emergency ticket should always be filed for ''production'' server outages.'''
|
| |
|
+ |
* '''ah3server.out''' from server
|
| |
|
+ |
* '''ah3server.err''' from server
|
| |
|
+ |
* Screenshot of the '''Current Activity --> Resources''' tab
|
| |
|
+ |
* (Potentially) Thread dump of the AHP server java process
|
| |
|
+ |
* '''ah3server.out''' from server
|
| |
|
+ |
* '''ah3server.err''' from server
|
| |
|
+ |
* Screenshot of the UI of where the failure occurred
|
| |
|
+ |
* IF UI error (''jasper exception, catalina exception, etc.'') click on '''more info''' and provide the contents in the ticket
|
| |
|
+ |
* Screenshot of the '''System --> Licenses''' main page and '''Committers''' tab
|
| |
|
+ |
== Stuck Requests/Build Lives ==
|
| |
|
+ |
* Go to the '''System --> Server Settings --> Diagnostics''' page, run the ''Active Request Contexts'' diagnostic, and provide the results in the Supportal ticket (optionally run the ''nudge contexts'' command)
|
| |
|
+ |
* Attempt to abort workflows/requests in the UI and revoke any locks
|
| |
|
+ |
* If abort or lock revoking does not resolve the issue, please provide a thread dump of the AnthillPro server's java process
|
| |
|
+ |
* Consult [this SQL] if this is still occurring
|
