Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce Listeners to aid in tracking timings within ServletContext and WebApp #5032

Closed
joakime opened this issue Jul 8, 2020 · 2 comments
Assignees
Labels
Enhancement Sponsored This issue affects a user with a commercial support agreement Stale For auto-closed stale issues and pull requests

Comments

@joakime
Copy link
Contributor

joakime commented Jul 8, 2020

Jetty version
9.4.30

Description
While the HttpChannel.Listener is very powerful, it doesn't have visibility into Servlet/WebApp specific concepts to aide in tracking performance behavior within specific Servlet/WebApp components.

Introduce a Listener (or two) that will :

  • expose startup timing. (overall WebApp timing, and ServletContext specific init timing)
  • expose individual component init timing (for Servlet / Filter / Listener inits)
  • expose WebApp configuration timing (for Configuration steps that can often take a long time to process. eg: annotation/bytecode scanning, jndi/datasource setup, etc)
  • expose tracking of Enter/Exit for Filter.doChain() and Servlet.service() call events.
@joakime joakime added Enhancement Sponsored This issue affects a user with a commercial support agreement labels Jul 8, 2020
@joakime joakime self-assigned this Jul 8, 2020
@joakime joakime changed the title Introduce Listeners to aide in tracking timings within ServletContext and WebApp Introduce Listeners to aid in tracking timings within ServletContext and WebApp Jul 8, 2020
joakime added a commit that referenced this issue Jul 8, 2020
joakime added a commit that referenced this issue Jul 8, 2020
@joakime joakime linked a pull request Jul 8, 2020 that will close this issue
joakime added a commit that referenced this issue Aug 21, 2020
joakime added a commit that referenced this issue Sep 14, 2020
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime added a commit that referenced this issue Sep 14, 2020
joakime added a commit that referenced this issue Sep 15, 2020
joakime added a commit that referenced this issue Sep 15, 2020
joakime added a commit that referenced this issue Sep 15, 2020
joakime added a commit that referenced this issue Sep 16, 2020
+ Fixing Filter destroy call order

Signed-off-by: Joakim Erdfelt <[email protected]>
joakime added a commit that referenced this issue Sep 16, 2020
joakime added a commit that referenced this issue Sep 16, 2020
joakime added a commit that referenced this issue Sep 17, 2020
joakime added a commit that referenced this issue Sep 17, 2020
joakime added a commit that referenced this issue Sep 17, 2020
…ible-web-apps

Issue #5032 - Minimal Extensible Web App changes
@stale
Copy link

stale bot commented Jul 21, 2021

This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale For auto-closed stale issues and pull requests label Jul 21, 2021
@github-actions
Copy link

This issue has been closed due to it having no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Sponsored This issue affects a user with a commercial support agreement Stale For auto-closed stale issues and pull requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant