Skip to content

[JENKINS-756] Perform initialization outside WebAppMain #13813

Closed

Description

@jenkins-infra-bot

Hudson spends a lot of time in ServletContextListener during initialization.

Many containers like Tomcat serves blank message during this period, which
confuses the user. Hudson should return from the servlet context listener right
away, then use a separate thread to perform initialization. This would allow
Hudson to produce a meaningful "initializing" message during this process.


Originally reported by kohsuke, imported from: Perform initialization outside WebAppMain
  • status: Closed
  • priority: Major
  • component(s): core
  • resolution: Fixed
  • resolved: 2007-09-16T16:47:03+00:00
  • votes: 0
  • watchers: 0
  • imported: 2025-11-24
Raw content of original issue

Hudson spends a lot of time in ServletContextListener during initialization.

Many containers like Tomcat serves blank message during this period, which confuses the user. Hudson should return from the servlet context listener right away, then use a separate thread to perform initialization. This would allow Hudson to produce a meaningful "initializing" message during this process.

  • environment: Platform: All, OS: All

Activity

  1. jenkins-infra-bot commented on Sep 16, 2007

    @jenkins-infra-bot
    Author
    kohsuke:
    • Original comment link
    • Raw content of original comment:

      Fixed in 1.139.

    Fixed in 1.139.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions