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

Automatic deployment waits for pollingInterval time before it scans the autodeploy directory for the first time #25078

Closed
OndroMih opened this issue Aug 7, 2024 · 0 comments · Fixed by #25079

Comments

@OndroMih
Copy link
Contributor

OndroMih commented Aug 7, 2024

Environment Details

  • GlassFish Version (and build number): 7.0.16 (and older)

Problem Description

When an application is dropped into the autodeploy directory while GlassFish is not started, GlassFish waits for the polling interval time before it deploys the application.

Impact of Issue

This prolongs the time from GlassFish launch to application deployment on startup. it takes longer until the application is deployed at startup and serves requests. This also prolongs the startup time of an application in Docker. By default, the pollingInterval is 2 seconds, so app startup takes 2 seconds longer than needed. Polling interval could be reduced to 1 second

Type: improvement
Component: AutoDeploy

OndroMih added a commit to OndroMih/glassfish that referenced this issue Aug 7, 2024
Before, delay time was the same as the poll interval time. 
Now there's no delay. Autodeployment is started immediately
and then in polling intervals.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant