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.
JBoss server starts wery slow, deploing is wery slow. But when is an exception on server NetBeans output console write stack in wrong format and now is wery wery wery slow. Work witch j2ee projects witch jboss is not posible when you wont quickly offent deploy project ant test it.
What ?!? Could you tell me your machine configuration ? On my machine (2.8Ghz p4 with 1gb memory - it's minumum for normal j2ee development i think) the jboss in default configuration starts in 20 seconds. If you think that 20 seconds are too much try to contact jboss developers. Or if you still sit tight please tell us more details because from your description we are not able to do anything with it. Thanks.
Strong words. At first, all the information you are writing about are not supplied with the measurements, system configuration, IDE version, Jboss configuration, JBoss installation type, your application 'size' and type and whatever what you think is relevant. Second, NetBeans provides only very thin layer above the JBoss functionality which seem to be slow for you. 1. starting/stopping - we only run the scripts which a user would normally run from a command line. there may some short (in seconds) delay after the server is started/stopped because we are repeatedly testing the state and have there some sleeping phase to avoid busy waiting. 2. deploying - we use 'hot' deploy, copying the app unit into the deploy directory in fact, wait several seconds letting JBoss to detect that samething happend and continuing by running browser, if needed. 3. console data - we do not transform the output going from the JBoss 4. console speed - maybe the only thing we can influent and is not perfect now We would appreciate more data, also can try to see the server log and compare it with NB delays (there are some as I described above).
Ok, your right, i missed wery important informations, but i was think it is generaly problem. I install netbeans 5 beta 1, beta 2 and rc1 and problem was on all. This problem i have on all projects (private and in job) what i working on. In my job this problem is on every pc where we work witch netbeans and jboss. My home pc: AMD Athlon 2500 XP+, 1 GB Ram, Windows XP My pc in job: Sempron 3000, 1 GB Ram, Windows 2000 I traied difrents version of jboss 4.0.2 , 4.0.3 The problem is alweys. When i unzip orginal jboss and install netbeans is too. I done tests By run.bat/ By handly deploy By NetBeans Startup times: ~24s ~33s Deploy ear time: ~1s ~50s Example action: ~1s ~15s (start the same action on view) I attach the test file. First problem is dubele the same log on output. Second is write exceptions in wrong format (lf or cr sign problem). The realy problem i have when is an exception on server, i can't work with server (redeploy, or stop server) by few minutes (somtimes 10 minute). i must run system task manager and kill jboss. If you want more information pleas spec me what kind of information you want. Thanks. P.S. Sory of my english.
Created attachment 28503 [details] Example action when jboss starts from netbeans
Created attachment 28504 [details] Example action when jboss starts from run.bat
Created attachment 28505 [details] Deploy when jboss starts from netbeans
Created attachment 28506 [details] Deploy action when jboss starts from run.bat
Created attachment 28507 [details] Server startup log when jboss starts from netbeans
Created attachment 28508 [details] Server startup log when jboss starts from run.bat
P.S. Now i decide to don't use nebeanes support for jboss and i deploy app by ant coppy file to deploy dir when i build app (F11). :( It is wory non confortable.
Thanks, it begins to be very valuable report. I will explore the delays a little bit and ask for some additional information. I have now these questions: 1. What the EAR unit consists of? EJBs, WAR, some framework? 2. How is it 'big', e.g. in sense of number of classes? 3. Do the EAR deploy times differ in such a terrible way always or was it measured only once? 50:1 looks like an accident... 4. I see no problem with end line characters e.g. in the server startup log, also other logs seem to be same in this sense The last thing which is not clear to me is that paragraph about 'exception on server'. What does it mean? And what does it mean that you can't work with the server? Startup time delay corresponds with what I said earlier. Some automatic processes can be never as good as a human interaction. E.g. server state detection is quite reliable bcs it is done using JMX interface. It is a reasonable compromise between reliability and speed. The other delays (especially during deploy) are strange to me and were not observed by me nor QA team. The data I have asked for could be valuable.
Another question, can you notice this behavior with the simple modules? I.e. when you create a simple EAR (with one WAR, EJB) with some servlet, EJB?
Answers: 1. It is not important what is in a ear, the problem is always, when contains same ejb jar, sar, har and/or war. 2. It is to not importatnt. ear from examle have 200 kb contains ~100 classes in 3 jars, and 1 har. But i have the same problem with any project with few classes and hundreds classes in few libs. 3. Problem is always, on diffrens machines and diffrents os, i have this problem on beta 1 and beta 2 (and daily) netbeans 4. End line character problem is only when is an exception, stack trace is writen in output window in one/two long line, is broke posibly by window . Exeption on server means the exeption wos throw by aplication deployed on server by netbeans. It is simply exception. It is not problem the startup time. This look like jboss work wery wery slowly, look at attachments, diffrents in times is to big, especially look at example action log. I do anather test. I install new clear jboss. I create new J2EE Project with EJB and WAR Module I add one sessionbean I add one echo method to session bean I add one servlet to war module, and call from it the echo method from sessionbean In echo method i call System.out.println("Call...."); I deploy app and call the servlet. It is out: 01:20:07,328 INFO [STDOUT] EchoServlet start 01:20:07,406 INFO [STDOUT] NewSessionBean: 1 call of echo method 01:20:07,406 INFO [STDOUT] NewSessionBean: 2 call of echo method ... 01:20:07,421 INFO [STDOUT] NewSessionBean: 8 call of echo method 01:20:07,703 INFO [STDOUT] NewSessionBean: 9 call of echo method 01:20:07,703 INFO [STDOUT] NewSessionBean: 10 call of echo method ... 01:28:14,312 INFO [STDOUT] NewSessionBean: 1000 call of echo method 01:28:14,312 INFO [STDOUT] EchoServlet done The full time wos 8 minutes !!!! I remove in echo method System.out.println And redeploy app and: 2006-01-21 01:31:41,578 INFO [STDOUT] EchoServlet start 01:31:41,578 INFO [STDOUT] EchoServlet start 2006-01-21 01:31:42,062 INFO [STDOUT] EchoServlet done 01:31:42,062 INFO [STDOUT] EchoServlet done One second !!!!! But the log is duble. Problem is with output log, but it is not with writing it in output window, problem is beacouse jboss 'wait' for netbeans to write log. When the exeption have a long stack trace, jboss 'wait' for netbeans write it all on out it may take few minutes. In my applications i use hibernate, in development proccess i want see queries and it is the reasone why my project works so slowly. But in my opinion it is wery importatnt defect. In this simple test this is not to accept. Especially in development proccess where is meny exeptions work is wery no comfortable.
Could you please run your test with the System.out.println() calls but without NetBeans? I would like to know how much time it will take. Do you have enough memory? Couldn't NetBeans and JBoss together exceed memory evailable?
I have 1GB Ram. I always work with netbeans and jboss runed in the same time (and more apps sometimes with photoshop and flash). I run my simple test on jboss (startup by run.bat) with system.out in bussines method and : 15:40:45,078 INFO [STDOUT] EchoServlet start 15:40:45,109 INFO [STDOUT] NewSessionBean: 1 call of echo method ... 15:40:46,375 INFO [STDOUT] NewSessionBean: 1000 call of echo method 15:40:46,375 INFO [STDOUT] EchoServlet done One second !! So what with jboss support in netbeans. Why in this, so simple test it work so long ? It is only my problem ? Did you saw it somewhere else ? I runed this test on 4 diffrents machines whith Win XP and 2000, whith jboss 4.0.2 and 4.0.3, whith netbeans 5 beta 1 ... RC 1.
I started to use the JBoss integration with NetBeans in 5.0 and am now using 5.5 dev from 200603130300 on WINXPSP2, Pentium M 1.8GHz, 1 GB RAM. The problem description from majo44 is exact: deployment is slow to begin with, and runs more slowly on each redeployment. During the second redeployment (I have an EJB jar, no war or ear), about one line per second from the output from the JBoss server is displayed, I can watch the memory consumption grow at about 100 to 200 KB per line. The intesting thing is that the deployment itself is fast, as I can see from the timestamps (takes about 3 seconds, from first to last EJB): 2006-03-28 16:42:49,406 INFO [org.jboss.ejb.EjbModule] Deploying EntityEB ... 2006-03-28 16:42:52,505 INFO [org.jboss.ejb.EJBDeployer] Deployed: ... It seems that generating the output puts extreme stress on the machine. And majo44 is right: EJB (re)deployment is so slow that it renders the JBoss integration completely unusuable.
Just a quick question/note: are really the actions on JBoss slow or just appropriate output to console window? This behavior may be related somehow to Issue 73385 part 1/.
I guess that problems are in the current implementation, not in JBoss. I am going to look at it ASAP.
Server output logging into the Outpu windows is now as fast as the server output itself. Also exception formating was fixed. More information can be found in the issue 73385.
*** Issue 76127 has been marked as a duplicate of this issue. ***
Verified