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 229904 - Unable to start more than 3-4 projects at the same time
Summary: Unable to start more than 3-4 projects at the same time
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P1 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-17 07:55 UTC by karamba84
Modified: 2013-06-08 05:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (80.32 KB, text/plain)
2013-05-23 08:03 UTC, karamba84
Details

Note You need to log in before you can comment on or make changes to this bug.
Description karamba84 2013-05-17 07:55:02 UTC
I have a multi-tier application which runs with about 13 jetty instances, providing some services. Unfortunately since 7.3 its not possible to run more than 3-4 of my jetty instances (embedded jetty). When i select all of them and click on "run" only 3 get started, all others do simply nothing. When i select them single i can also run only about 3-4 of them.
When i do exactly the same in Netbeans 7.2.1 it works as expected. What does also not work in NB 7.2.1 is selected all of them and click on "run". At least one is always missing (randomly).

This is pretty critical to us, unfortunately. Is there some known workaround for this? Why is NB blocking creating new threads?
Comment 1 Marian Mirilovic 2013-05-23 07:57:05 UTC
could you please attach messages.log file and reopen ? Thanks in advance.
Comment 2 karamba84 2013-05-23 08:03:58 UTC
Created attachment 134778 [details]
messages.log
Comment 3 karamba84 2013-05-29 07:38:58 UTC
This is NOT a jetty problem. It is a problem how netbeans executes maven tasks. Probably some kind of WorkerQueue which blocks execution of new maven goals.
Comment 4 Milos Kleint 2013-06-06 09:29:31 UTC
    //8 means 4 paralel builds, one for input, one for output.
    private static final RequestProcessor PROCESSOR = new RequestProcessor("Maven ComandLine Output Redirection", 8); //NOI18N

yes, we have this code in the nb.org codebase.

The hard part here is to guess the right maximum. 4 builds consume not only 8 threads but at least 12. the additional one being managed by ExecutionEngine. Then we spawn an external process + jvm for the build. And then sometimes the maven build jvm spawns yet another jvm.

according to http://vanillajava.blogspot.cz/2011/07/java-what-is-limit-to-number-of-threads.html the number of maximum threads in jvm is fairly high to be save to increase, however the number of threads is not the only limiting factor, memory processing could be as well..
Comment 5 karamba84 2013-06-06 09:42:05 UTC
This problem is stopping us from using Netbeans 7.2.1+ 
Isnt it possible to use some kind of configuration for that? 
This would kill all requirements for users with only small amount of threads (could be the default configuration) but also those who use heavy-threaded applications (like we do).
Comment 6 Milos Kleint 2013-06-06 09:59:33 UTC
http://hg.netbeans.org/core-main/rev/3eeafe9ee549

increases the count to 16 builds.

will only work in dev builds + 7.4-beta, older releases are unaffected.
Comment 7 Quality Engineering 2013-06-08 01:09:20 UTC
Integrated into 'main-golden', will be available in build *201306072301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/3eeafe9ee549
User: Milos Kleint <mkleint@netbeans.org>
Log: #229904 increased the throughput of output processing RP to 32, meaning 16 builds in paralel.
Comment 8 karamba84 2013-06-08 05:42:03 UTC
Thanks!! :)