-
Notifications
You must be signed in to change notification settings - Fork 865
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
Tomcat start delay hardcoded to 180s #3898
Comments
I know that this is not a solution, but is it possible to try a JVM with HotSpot instead of OpenJ9? OpenJ9 has a terrible performance when starting in Debug mode. |
Hello, |
Well, you might just check out NB 13 code change that timeout value and compile one for yourself. This is a so rare case, that I do not feel introducing an API for it. Even as small as add a System Property to be able to change that timeout. Though others can have other opinion. You can also file a PR if you would like to push that through. |
…t_parameter [#3898] Parameterize Tomcat startup/shutdown timeouts.
Apache NetBeans version
Apache NetBeans 13
What happened
Hello,
I'm trying to use netbeans to work on a big project, this project takes about 200s to start in debug mode. After 180s netbeans throw a message "Starting of Tomcat failed".
I saw the message in netbeans-master\enterprise\tomcat5\src\org\netbeans\modules\tomcat5\optional\Bundle.properties
I think that it's due to hardcoded timeout in netbeans-master\enterprise\tomcat5\src\org\netbeans\modules\tomcat5\optional\StartTomcat.java L113 :
private static final long TIMEOUT_DELAY = 180000;
Is it possible to change this timeout ? At least increase the time to solve the bug, best option would be to have an option to set it in servers > startup menu (new feature)
How to reproduce
No response
Did this work correctly in an earlier version?
No
Operating System
Linux rhel 7.6
JDK
adopt openjdk 11.0.9 openj9
Apache NetBeans packaging
Apache NetBeans provided installer
Anything else
No response
Are you willing to submit a pull request?
No
Code of Conduct
Yes
The text was updated successfully, but these errors were encountered: