Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 222501 - org.netbeans.modules.j2ee.deployment.impl.ServerException: Deployment timeout has exceeded.
org.netbeans.modules.j2ee.deployment.impl.ServerException: Deployment timeout...
Product: serverplugins
Classification: Unclassified
Component: Infrastructure
All All
: P3 (vote)
: 7.4
Assigned To: Petr Hejl
Depends on:
  Show dependency treegraph
Reported: 2012-11-21 02:59 UTC by tyrantblizz
Modified: 2014-10-01 02:23 UTC (History)
26 users (show)

See Also:
Issue Type: DEFECT

stacktrace (1.05 KB, text/plain)
2012-11-21 02:59 UTC, tyrantblizz
stacktrace (1.03 KB, text/plain)
2012-11-23 08:17 UTC, fortruth
stacktrace (1.05 KB, text/plain)
2013-01-26 10:19 UTC, szmitek
stacktrace (1.05 KB, text/plain)
2013-02-22 11:50 UTC, Maksim Khramov
Netbeans threads dump (26.47 KB, application/octet-stream)
2013-02-24 08:26 UTC, Maksim Khramov
stacktrace (1.05 KB, text/plain)
2013-03-15 09:03 UTC, Maksim Khramov
stacktrace (1.05 KB, text/plain)
2013-03-16 11:12 UTC, marco76
stacktrace (1.05 KB, text/plain)
2013-04-30 11:22 UTC, Sergey Petrov

Note You need to log in before you can comment on or make changes to this bug.
Description tyrantblizz 2012-11-21 02:59:17 UTC
This bug was originally marked as duplicate of bug 202830, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.3 Beta 2 (Build 201211062253)
VM: Java HotSpot(TM) Client VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24
OS: Windows XP

User Comments:
GUEST: I opened NetBeans 7.2 and was waiting for openning every project

alied: Using Deploy on Save in a Maven project

GUEST: ????????

GUEST: nothing. saved work, waited for deployment...

GUEST: application was connecting to database

alied: deploying a Web Projecet to Tomcat via autodeploy

GUEST: Debugging my Spring application

org.netbeans.modules.j2ee.deployment.impl.ServerException: Deployment timeout has exceeded.
   at org.netbeans.modules.j2ee.deployment.impl.TargetServer.trackDeployProgressObject(
   at org.netbeans.modules.j2ee.deployment.impl.TargetServer.reloadArtifacts(
   at org.netbeans.modules.j2ee.deployment.impl.TargetServer.notifyArtifactsUpdated(
   at org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager$DeployTask.notifyServer(
   at org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager$
   at java.util.concurrent.Executors$
Comment 1 tyrantblizz 2012-11-21 02:59:21 UTC
Created attachment 128176 [details]
Comment 2 fortruth 2012-11-23 08:17:04 UTC
Created attachment 128292 [details]
Comment 3 Exceptions Reporter 2012-11-23 08:17:15 UTC
This bug already has 20 duplicates 
Comment 4 Petr Hejl 2012-11-23 21:35:19 UTC
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?
Comment 5 Petr Hejl 2012-11-26 15:53:50 UTC
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.
Comment 6 Petr Hejl 2012-11-26 15:55:46 UTC
There is already a request for configurable timeout for GF here: #166642
Comment 7 szmitek 2013-01-26 10:19:44 UTC
Created attachment 130681 [details]

deploying JSP project
Comment 8 Maksim Khramov 2013-02-22 11:50:04 UTC
Created attachment 131727 [details]
Comment 9 Maksim Khramov 2013-02-24 08:24:06 UTC
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...
Comment 10 Maksim Khramov 2013-02-24 08:26:31 UTC
Created attachment 131794 [details]
Netbeans threads dump

Netbeans threads dump
Comment 11 Maksim Khramov 2013-03-15 09:03:43 UTC
Created attachment 132636 [details]

Deploy project. Server started but project not deployed in 20 minutes.
last message seen in log:
>> Initializing....
Comment 12 TomasKraus 2013-03-16 01:08:51 UTC
Problem with 201302212300 build is not related to this bug. There is already another bug# 226298 opened to resolve this issue.
Comment 13 marco76 2013-03-16 11:12:37 UTC
Created attachment 132679 [details]

writing facelet code
Comment 14 Sergey Petrov 2013-04-30 11:22:33 UTC
Created attachment 133972 [details]

craeate ws< deploy to, 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.
Comment 15 Sergey Petrov 2013-04-30 12:03:58 UTC
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.
Comment 16 TomasKraus 2013-04-30 22:25:54 UTC
Sergey, please, can you let us know what version did you use? Was it dev build from trunk, or 7.3.1 build.
Comment 17 Sergey Petrov 2013-05-01 04:18:46 UTC
Comment 18 TomasKraus 2013-05-02 19:52:05 UTC
OK, thanks. Then it's bug# 226298 which was fixed by Peter B. today.

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo