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.
Summary: | org.netbeans.modules.j2ee.deployment.impl.ServerException: Deployment timeout has exceeded. | ||
---|---|---|---|
Product: | serverplugins | Reporter: | tyrantblizz |
Component: | Infrastructure | Assignee: | Petr Hejl <phejl> |
Status: | STARTED --- | ||
Severity: | normal | CC: | abien, alied, bht, ehsaniara, fortruth, jbsabmello, jskrivanek, krushnakant, leonhad, marco76, mkhramov, myururdurmaz, ozziej, panason2008, pjiricka, sebsmail, sj-nb, szmitek, tnleeuw, TomasKraus, trekxander, tyrantblizz, vkhashin, yyq2008, zdenek.rod, zmirc |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 195471 |
Attachments: |
stacktrace
stacktrace stacktrace stacktrace Netbeans threads dump stacktrace stacktrace stacktrace |
Description
tyrantblizz
2012-11-21 02:59:17 UTC
Created attachment 128176 [details]
stacktrace
Created attachment 128292 [details]
stacktrace
This bug already has 20 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=195471 This may happen if deploy is quite long. The default timeout is 20s. There is a possibility for server plugin to make it configurable. Reporters any details? Is the project quite large? Any other details about your projects? Ok I have evaluated bit more. This is not a real defect in our codebase. It happens when deployed application is too big or machine or server too slow so the deployment takes too long. The message is not very helpful as it is actually stacktrace being reported here. The default timeout is 20s, but plugin implementor may change (and so the user if plugin allows that). So the proper solution would be 1) Display decent message explaining what's going on and how to avoid that (serverplugin configuration). 2) Implement configurable timeout in all maintained plugins. For example Tomcat plugin already allows that and its default is 120s. I do not think this is P2 as duplicates has been collected during 2 years. I also think it would be better to fix post 7.3. There is already a request for configurable timeout for GF here: #166642 Created attachment 130681 [details]
stacktrace
deploying JSP project
Created attachment 131727 [details]
stacktrace
Very often reproducible on last build: NetBeans IDE Dev (Build 201302212300) Java: 1.7.0_15; Java HotSpot(TM) 64-Bit Server VM 23.7-b01 GlassFish server started and project is deployed as I see in server log: >> INFO: WebApplication69 was successfully deployed in 529 milliseconds. But in Application run output tab I see only >> Initializing... Created attachment 131794 [details]
Netbeans threads dump
Netbeans threads dump
Created attachment 132636 [details] stacktrace Deploy project. Server started but project not deployed in 20 minutes. last message seen in log: >> Initializing.... Problem with 201302212300 build is not related to this bug. There is already another bug# 226298 opened to resolve this issue. Created attachment 132679 [details]
stacktrace
writing facelet code
Created attachment 133972 [details]
stacktrace
craeate ws< deploy to 3.1.2.2, create ws client, add some method wiith @webMethod(excelude = true).
create one more ws, addd some methods with exclude. autodeploy is atrted but stop at some point and finally this exception.
In my case I have very small/simple application with ws and ws client and have INFO: WS00018: Webservice Endpoint deployed NewWebService listening at address at http://stalenovo:8080/WebApplication30/NewWebService INFO: WEB0671: Loading application [WebApplication30] at [/WebApplication30] INFO: WebApplication30 was successfully deployed in 2 064 milliseconds. in output but progress is never completed, it's likely a valid issue instead of timeout. Sergey, please, can you let us know what version did you use? Was it dev build from trunk, or 7.3.1 build. dev/trunk OK, thanks. Then it's bug# 226298 which was fixed by Peter B. today. |