Lucee startup takes 15 minutes to become available

Description

We see some issues with Lucee in a corporate network.
For local development on Laptops or on our company site, where there is no restriction to block communication from Luceeserver-VMs to the public internet, the startup phase is very quick and at least 1 minute after restart Lucee can be accessed by Browser.

On our customer side, the Lucee restart needs up to 15 minutes to become available. Catalina.out seems to be quick, restart of Tomcat is fast and already processed. But it takes up to 15 minutes before the first requests are served by Lucee application.

Could it be case, that in the launch phase, Lucee try to contact the Extensions URL providers to look for possible updates? What happens if this connection was timed out? What is the timeout limit for this action?

You can test: Start a lucee from PC laptop connected with Internet and in parallel open the Lucee server admin. It will takes only seconds until the page was loaded.
Disconnect Internet connection (by Flight mode or unplug cable) and do the same steps, it takes minutes, until the Lucee Server admin was loaded.

Is there a switch to disable the Extension provider?
I cannot delete the extension provider as we manually update all extensions when we decide with the customer. How it can be deleted?

Environment

None

Attachments

8
  • 13 May 2019, 01:01 pm
  • 12 Mar 2019, 03:00 pm
  • 12 Mar 2019, 02:56 pm
  • 12 Mar 2019, 02:56 pm
  • 12 Mar 2019, 02:32 pm
  • 26 Feb 2019, 12:02 pm
  • 26 Feb 2019, 11:54 am
  • 15 Jan 2019, 02:17 pm

Activity

Show:

Zac Spitzer 28 April 2022 at 02:25

fixed in LDEV-3355

J Farrar 14 November 2019 at 17:27

How can we vote this up?

John Liljegren 31 October 2019 at 01:23

We’ve been noticing this for quite some time as well, and this has cropped its head twice in the last few weeks when were deploying our product to clients. It is a major headache and could be fixed so easily with a simple flag. Please address in the next patch!

Brad Wood 30 October 2019 at 19:40

This issue comes up on a very regular basis with CommandBox users. I had people asking about it today on the mailings list and yesterday on CFML Slack-- some of the users completely unable to even use CommandBox on their PC due to the downloading behavior. This really needs addressed. Just add a flag we can set to disable auto-downloads. This is a complete no-go on locked down computers. And if Lucee thinks it needs to download something and can't, then we need an exception thrown that explains why because in all of my cases Lucee shouldn't even be downloading anything in the first place. This ticket is fairly new, but this issue has been brought up for years now with no change. cc/

Alexander Diedler 8 August 2019 at 15:05

I already describe the test case. Install lucee, upgrade by lco. Disconnect network and start lucee, it will take around 15min.

Unresolved

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 15 January 2019 at 13:28
Updated 28 April 2022 at 02:27

Flag notifications