This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When the j2eeserver layer calls a plugin's StartServer.startTarget() method or triggers a deploy operation, the code waits to see if the actions completes. The timeout is currently hard-coded and large (~20 minutes). I propose that InstanceProperties be extended with two new constants, STARTUP_TIMEOUT and DEPLOYMENT_TIMEOUT. If a plugin defines an instance property with these names, their value is interpreted as the number of seconds to use as the timeout. If the property isn't defined, the old default would continue to be used. This allows the plugin to change the timeout on a per-instance basis. This may be useful in situations where deployment is being done over a congested link.
Would it be useful to introduce also the SHUTDOWN_TIMEOUT constant?
That sounds reasonable and easy.
Created attachment 39599 [details] api change info
Vince, could you please add that SHUTDOWN_TIMEOUT constant there, or should I modify your diff?
opps.. sure. I will get that attached today.
Created attachment 39836 [details] revised patch
Thanks I have just noticed that the @since tag is missing in the method javadocs, otherwise the patch looks good.
Created attachment 39854 [details] one more time...
The fix was integrated into trunk. Checking in apichanges.xml; /cvs/j2eeserver/apichanges.xml,v <-- apichanges.xml new revision: 1.24; previous revision: 1.23 done Checking in nbproject/project.properties; /cvs/j2eeserver/nbproject/project.properties,v <-- project.properties new revision: 1.15; previous revision: 1.14 done Checking in src/org/netbeans/modules/j2ee/deployment/plugins/api/InstanceProperties.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/plugins/api/InstanceProperties.java,v <-- InstanceProperties.java new revision: 1.20; previous revision: 1.19 done
since this is integrated... isn't it closed now? Do I need to do something else on this?