This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes jboss 4.2.3 takes 3 mintues!! to come up, the cpu usage is 100% Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "jboss 4.2.3 takes 3 mintues!! to come up, the cpu usage is 100%" Watch "jboss 4.2.3 takes 3 mintues!! to come up, the cpu usage is 100%" New topic
Author

jboss 4.2.3 takes 3 mintues!! to come up, the cpu usage is 100%

Elhanan Maayan
Ranch Hand

Joined: May 04, 2009
Posts: 113
hi..

i'm using jboss tool to control jboss, and for some reason, it takes forever to boot up, including cpu usage

for example:
16:40:41,944 INFO [EARDeployer] Init J2EE application: file:/C:/Workdir/jboss/jboss-4.2.3/server/pmp/deploy/underwrite.ear/
16:40:59,734 WARN [MainDeployer] Found non-jar deployer for lib/common/propertyset-1.3.jar: MBeanProxyExt[jboss.ejb:service=EJBDeployer]
16:41:05,850 WARN [MainDeployer] Found non-jar deployer for lib/webapp/oscore-2.2.4.jar: MBeanProxyExt[jboss.ejb:service=EJBDeployer]
16:41:15,332 WARN [MainDeployer] Found non-jar deployer for lib/common/propertyset-1.3.jar: MBeanProxyExt[jboss.ejb:service=EJBDeployer]

why does it take 10 seconds for the maindeployer to scan for jar? my ear is only 62 mb
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5836
    
    7

Is your EAR a file, or an exploded directory? If a file, the app server has to unpack the file into the temp directory before it can use it. And that is on top of processing the modules looking for EJBs to register. Try deploying as an exploded directory, that might cut down on the deployment time.


JBoss In Action
Elhanan Maayan
Ranch Hand

Joined: May 04, 2009
Posts: 113
it's allready an exploded directory, any other ideas? btw starting jboss alone (not with eclipse) takes "only" 2 minutes..
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5836
    
    7

Two minutes? What system are you running this one? On my ancient Pentium IV system running XP at work it takes only 30 seconds (on my quad-core system at home it takes all of 10 seconds). That is for 4.2.3.

Extrapolating the times then, I suspect that it would take about 45 seconds to bring up your app (on my work system). Which is acceptable.
Elhanan Maayan
Ranch Hand

Joined: May 04, 2009
Posts: 113
well would you like the entire log file and see the times? the computer it's running on is dual core, i mean 2 minutes including the ear deployment.
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10146
    
165

16:40:59,734 WARN [MainDeployer] Found non-jar deployer for lib/common/propertyset-1.3.jar: MBeanProxyExt[jboss.ejb:service=EJBDeployer]


Do you have Classpath entires in the MANIFEST.MF of jar files? If yes, then try removing them and see if there is a change in the deployment time (i guess there will be), Let us know how it goes.

[My Blog] [JavaRanch Journal]
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5836
    
    7

well would you like the entire log file and see the times?


I was not doubting that it takes 2 minutes. I was just amazed that it would take so long.

i mean 2 minutes including the ear deployment.


Ahah! Earlier you stated that "starting jboss alone" takes 2 minutes, which to me means without your app. It would really, really, really help if you were accurate and exact in your posts, otherwise you end up getting useless advice.

So the issue than becomes, what is in your app? Try bringing up JBoss AS without your app (from a command line, not from within Eclipse), and once the "started in xx seconds" log message shows up, then deploy your app (by manually copying the ear to the deploy directory - don't use Eclipse). The timestamps on the log messages for deploying the app might lead to some ideas on what is taking so long.
Elhanan Maayan
Ranch Hand

Joined: May 04, 2009
Posts: 113
but issue is not with jboss but with eclipse i think, becouse although jboss takes around 20-30 % of cpu, eclipse takes 60%! , i think i'm gonna back to europa release (didn't happen then) and drop ganymede, i've start to hear things about it, i think i'll wait for eclipse 3.5.2 for a new upgrade.
Tomas Studva
Greenhorn

Joined: Oct 06, 2009
Posts: 1
Hi,
I have the same problem running eclipse ganymede - 3.4.2 and jboss 5.1.0 GA. The problem is not with ear or application.

When starting jboss without eclipse, it starts fast. When starting jboss from eclipse, eclipse takes much of CPU, up to 90%, and star is very slow. The problem exists on single core CPU. When Multi core CPU is used, the eclipse takes one and jboss second. ANY ideas? Is it bug?
Elhanan Maayan
Ranch Hand

Joined: May 04, 2009
Posts: 113
jboss claimed it was a bug in a pre-release version and that they fixed it, i since then moved to eclipse 3.5 and do not expirience the same .
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jboss 4.2.3 takes 3 mintues!! to come up, the cpu usage is 100%