Admin: WebApp
From Resin 3.0
The WebApp /resin-admin page is used to check the status of your deployed web applications
- Check the deployed version
- Check that all servers in the cluster are running the same .war
- Deploy a new application version
- Check for web-app errors
- Check the session status
WebApps summary
The summary view shows all the web-apps in your server and a brief summary of the activity.
- Web-App
- The context-path identifier of the web-app
- State
- The deployment state for the web-app: ACTIVE, FAIL, STARTING
- Active
- The number of currently active requests in the web-app.
- Sessions
- The number of currently active sessions in the web-app.
- Uptime
- How long since the last restart for the webapp.
- 500
- Number of 500 error (servlet exceptions) and the time since the last error.
- Deploy
- The version or date of the current deployed version if deployed with a war archive or through Resin's deploy
In the above example, /hello2 was deployed from the command-line. Since all the servers in the cluster have the same version, there's a green checkmark by the deployment.
The Uptime is colored red with "0h01" for all the servers since the screenshot was taken just after restarting Resin.
Deployment
The web-app page checks the deployed applications across the cluster and displays any differences, even when the application is deployed as a .war. Resin calculates a hash of the .war contents on each server. If any server has a different hash, it will be displayed as a red 'x'.
In this screenshot, the 4th server ("d") is currently stopped, so Resin cannot contact it to compare the hashes and marks that server's content in red.
Because this web-app was deployed using .war files and without versions, Resin reports the .war date instead of the version. Notice in the screenshot that the dates do differ for two of the servers even though they are both green. In that case, the .war contents are identical.
