David,
my experience is described below and has been like that ever since
NetBeans started to support JBoss (measured on a core i7, 2.66 GHz, 6
GB RAM, with JBoss console log level set to DEBUG, which is extremely
verbose, using the "default" configuration with a medium-sized EJB jar
deployed):
- outside NetBeans: 21:59:57,381 INFO ... [4.0.5.GA...] Started in
16s:471ms
- inside NetBeans: 21:51:42,517 INFO ... [4.0.5.GA...] Started in
1m:29s:49ms
On a less powerful box starting JBoss with unconditional debug level
logging inside NetBeans can take 30 minutes or more.
I once ran Sysinternals' File Monitor while starting up JBoss inside
NetBeans and it seemed to me that NetBeans implements displaying the
JBoss server log simply by polling the log file once per second and
adding the newly arrived lines to the output window. This seems to slow
down the JBoss boot process extremely.
In essence I always have to start JBoss outside NetBeans and avoid the
"View Server Log" menu entry.
Cheers,
Georg
David Salter wrote:
I am running NetBeans 6.8 Beta on a Vista PC and am starting the
"all" instance of a JBoss server version 4.3.0CP6.
Starting JBoss from within the IDE is consistently significantly
slower than starting JBoss from the command line.
Starting JBoss from the command line consistently takes 140
seconds whereas starting the same JBoss instance from
inside NetBeans (via a registered server) takes 190s.
I've raised issue 175504 regarding this. Does anyone else have
this issue?
Cheers,
Dave.
