JBoss 5.0 Taking LONG Time to Start Up

[ctf]

Hi,
I'm just starting to check out 5.0. I have pretty much a basic/default installation of JBoss AS 5.0. The same EJB app that takes about a minute to start up in 4.x takes more than 4 minutes in 5.0. Some sample output...

22:41:14,203 INFO [WebService] Using RMI server codebase: http://localhost:8083/
22:41:34,515 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
22:41:34,515 INFO [NativeServerConfig] 3.0.4.SP1
[..... LONG WAIT HERE .....]
22:43:44,359 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@7764591{vfsfile:/C:/jboss-5.0.0.GA/server/default/deploy/myApp.ear/myAppEJB.jar/}
22:43:44,359 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@7764591{vfsfile:/C:/jboss-5.0.0.GA/server/default/deploy/myApp.ear/myAppEJB.jar/}

As you can see, right after "[NativeServerConfig] 3.0.4.SP1", you can see that about 2 minutes elapse before the next line. I'm using Eclipse + JBoss plugin (Windows XP, JDK 6.x) to deploy and start up JBoss.
Is this normal? Any suggestions on how to speed this up? I don't need web services, so if that's the culprit, any tips on removing/disabling it?


Thanks!

[jaikiran]

22:41:34,515 INFO [NativeServerConfig] 3.0.4.SP1
[..... LONG WAIT HERE .....]
22:43:44,359 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@77
64591{vfsfile:/C:/jboss-5.0.0.GA/server/default/deploy/myApp.ear/myAppEJB.jar/}

Its not the EJB app thats taking time. The long wait that you are reporting, is just that there are no INFO level logs during that period. Keep a watch on the %JBOSS_HOME%/server/< serverName>/log/server.log file (which has more verbose logs) to see what's going on during that period.

[ctf]

Thanks,
Here's the relevant piece I found in the log. If I run it from command line instead of Eclipse plugin, it runs faster. If I remove my EAR from the deployment dir it runs even faster.

2009-01-03 13:49:12,640 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (main) vfsfile:/C:/jboss-5.0.0.GA/server/default/deploy/jmx-console.war/ endpoint mappings:

2009-01-03 13:49:12,640 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (main) Processing unit=jmx-console.war, structure:
jmx-console.war


2009-01-03 13:51:02,015 DEBUG [org.jboss.metadata.process.chain.ejb.jboss.JBossMetaDataProcessorChain] (main) Added Processor org.jboss.metadata.process.processor.ejb.jboss.SetDefaultLocalBusinessInterfaceProcessor@1e55518 to Chain org.jboss.metadata.process.chain.ejb.jboss.JBossMetaDataProcessorChain@135cde4

This piece takes almost 2 minutes. Is this normal? Do you think there's anything I can do?

[jaikiran]

"ctf" wrote:

2009-01-03 13:49:12,640 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (main) vfsfile:/C:/jboss-5.0.0.GA/server/default/deploy/jmx-console.war/ endpoint mappings:

2009-01-03 13:49:12,640 DEBUG [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer] (main) Processing unit=jmx-console.war, structure:
jmx-console.war


2009-01-03 13:51:02,015 DEBUG [org.jboss.metadata.process.chain.ejb.jboss.JBossMetaDataProcessorChain] (main) Added Processor org.jboss.metadata.process.processor.ejb.jboss.SetDefaultLocalBusinessInterfaceProcessor@1e55518 to Chain org.jboss.metadata.process.chain.ejb.jboss.JBossMetaDataProcessorChain@135cde4

This piece takes almost 2 minutes. Is this normal?

My clean JBossAS "default" server profile takes under a minute to boot on RHEL5 Operating System. So i wouldn't say your startup time is normal. Without any of your applications deployed, how much time does the "default" server take to start? A;so please post the first few lines from the jboss console which shows the JDK version being used. Just want to make sure, the correct JDK is being used.

[ctf]

Hi,

===============================================================================

 JBoss Bootstrap Environment

 JBOSS_HOME: C:\jboss-5.0.0.GA

 JAVA: C:\Program Files\Java\jdk1.6.0_02\bin\java

 JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

 CLASSPATH: C:\jboss-5.0.0.GA\bin\run.jar

For a completely clean & unmodified instance (no apps) of JBoss 5.0, it takes about 1 minute to start.

In Eclipse, using the JBoss plugin, it takes about 2 minutes to start the app using the "Run" command and 3-4 minutes to start in debug mode.

In other words, starting it in debug mode is taking significantly longer. I guess it should be slower than non-debug mode, but I don't remember the discrepancy ever being this drastic.

Anyway, I guess probably not much I can do about it.. unless you have some ideas. Thanks again for your help.

[jaikiran]

"ctf" wrote:

For a completely clean & unmodified instance (no apps) of JBoss 5.0, it takes about 1 minute to start.

Looks OK.

"ctf" wrote:

In Eclipse, using the JBoss plugin, it takes about 2 minutes to start the app using the "Run" command

I haven't used the Eclipse JBoss plugin, so not sure if that is expected. I guess, you could ask about this in the forum here http://www.jboss.com/index.html?module=bb&op=viewforum&f=201.

P.S: I hope, i am pointing you to the right forum - I don't know if the Eclipse Plugin you are talking about is different from the JBoss Tools :)

[ctf]

Your assumption is correct. I am using JBoss Tools. Yeah, I think that may be the next place to try. Thanks for the link.