i still can't see it.
What is "it"? And where are you looking for "it"?
What version of JBoss AS? Older versions (4.2.x and older) seemed to be single-threaded (i.e., did serial deployment) during startup but the 5.x version appears to be multi-threaded (i.e., parallel deployment) during startup. (Previous sentence is speculation based on my observations of CPU usage on my quad-core system.) Also, 5.x does a lot more with injecting aspects into the code, which causes it to be more CPU-bound. Either of these could account for the 100% CPU usage.
it being this:
talking about jboss 3.2.5 and jboss 4.2.3 launching them under eclispe 3.3.2 with jboss tools 2, took less cpu then under eclipse 3.4.2 with jboss tools 3.0
As said before - both of your issues were bugs that where present in the previous builds.
They are now fixed in GA. Please verify you are still using GA and seeing this. if you do then report it in jira with a screenshot of the missing link in the server editor.
See http://screencast.com/t/5dbBgHjtw for how it looks for me in JBT 3 an dJBDS 2.
With respect to AS start of 100% cpu usage then that were caused by some bad logic in the code that checks for AS starting-stopping. That code is gone now so if can reproduce that on the GA version then open a jira and provide whatever details you got.
ooooh, you changed the location (it used to reached via the right click context menu on the server itself, i'm assuming that's not a bug)
as for cpu usage, this is strange, when starting eclipse with a clean workspace, it's ok, but if i use with my current workspace then it spikes to 100%. this is the same workspace i've been using with eclipse 3.3.2 and jbos tools 2.0.0 nothing changed, i simply copied the new eclipse to a new directory and directed it to the old workspace, what could be the cause of that?
afaik, the location changed close to about 2 or 3 years ago when we moved from a custom server API to the WTP API when going from JBossIDE 1.5/1.6 to JBoss Tools 2 (my memory might be bad here though)
About the 100%, is it constant or just a spike ?
well at first i thought the spike was due to me using the old workspace, so i cleaned the .metadata folder and re-lauched eclipse, imported all the projects ,and changed my settings. i later tried the startup and again i saw the spike (all thought out jboss starting up). i noticed the javaw process of eclipse took about 700k memory (and rtvsscan antivirus process took 300k memory) i re-booted the pc, and stated with javaw process about 300k size, now i don't see the spike but around 50-70 cpu usage.
"all thought out jboss starting up"
you mean, all without jboss starting up ?
50-70% cpu usage sounds like a lot to me.
Whcih proces is taking all that time ?
i mean all through out jboss startup, when actually using jboss the cpu is normal.
i see now the problem continues there are 2 java processes which take up the cpu, the jboss and eclipse itself, eclipse takes up most of resources with 50-70 cpu usage, while jboss takes up the rest.
this is my command line
eclipse.exe -vm c:\Java\jdk1.5.0_15\bin\javaw -data c:\Workdir\clientworkspace\applications\ -showlocation
this might just be the cpu needed for all the console output - does the cpu return to "normal" when the startup have completed ?
yes, but it didn't require all that much when i was eclipse 3.3.2 ? what changed?
Not as far as I know.
Have you tried starting without using eclipse - does it take the same cpu ?
no only around 70-90% how much should it take?
well Eclipse needs to process the incoming console so that will add up a bit so if JBoss on it's self takes 90% then launching via eclipse might create a spiked cpu...but as long as it goes down when startup is completed i'm not that worried.
but that doens't explain how it's all good in eclips 3.3.2 ?