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.

Bug 190603 - Cannot set "deploy timeout" nor "start timeout" to Glassfish 3 servers
Summary: Cannot set "deploy timeout" nor "start timeout" to Glassfish 3 servers
Status: RESOLVED DUPLICATE of bug 166642
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: PC Mac OS X
: P3 normal with 1 vote (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 06:29 UTC by ijay
Modified: 2011-05-06 18:42 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Setting for GF v2 (174.92 KB, image/png)
2010-09-27 06:31 UTC, ijay 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ijay 2010-09-27 06:29:34 UTC 
In Tools->Servers setting panel, I cannot set "deploy timeout" nor "start timeout" to Glassfish v3 servers like v2 servers. When I tried to deploy a project to GF 3 for a long time, NB told me "Failed to start Glassfish" and stop glassfish output to console.  But in fact, GF started and I can access the port.
Comment 1 ijay 2010-09-27 06:31:17 UTC 
Created attachment 102155 [details]
Setting for GF v2
Comment 2 Vince Kraemer 2010-09-28 20:52:34 UTC 
Adding a field to set the timeout is unlikely to resolve the issue that you are running into.

I am converting this issue to an enhancement request and have opened issue 190651 to track the defect aspect.
Comment 3 adrianriley 2011-04-28 12:45:57 UTC 
It seems that the problem is far worse in Netbeans 7.0. Now, when Netbeans thinks that the server has failed to start, the server process seems to be killed. Hence Glassfish cannot be started within Netbeans at all if the startup time exceeds the timeout arbitrarily set in Netbeans.
Comment 4 Vince Kraemer 2011-05-06 18:42:48 UTC 

*** This bug has been marked as a duplicate of bug 166642 ***