-
1. Re: JBoss 5.1.0 GA - issue with startup time
"binuksuk" wrote:
while JBoss5 takes 90 seconds to startup (default configuration).
It's true that JBoss AS-5 is slower than AS-4, but 90 seconds for the default configuration is too much. I have a clean default profile booting in around 40 seconds. What is your system configurations? Can you post the console logs (not server.log)?Is there a way to decrease JBoss5 startup time?
Removing unwanted services is one way to do that. But it depends on the applications that you want to deploy on that server.
While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted. -
2. Re: JBoss 5.1.0 GA - issue with startup time
I am not sure which is the console log that you want me to post.
The default server that I use has server.log and boot.log.
Shall I post boot.log? -
3. Re: JBoss 5.1.0 GA - issue with startup time
How do you start the server? I assumed you started it from a command prompt window. And that's what i was referring to as the console logs. The server.log is too verbose and won't be of use. The boot.log is too minimal and won't be of use either :)
-
4. Re: JBoss 5.1.0 GA - issue with startup time
Got it :)
System configuration - Pentium 4 CPU, 2.80 GHz, 2 GB RAM
OS: Windows XP 5.1 (x86)
Here is the console logD:\TIC\JBOSS_510\jboss-5.1.0.GA\bin>run Calling D:\TIC\JBOSS_510\jboss-5.1.0.GA\bin\run.conf.bat =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: D:\TIC\JBOSS_510\jboss-5.1.0.GA JAVA: c:\jdk50\bin\java JAVA_OPTS: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -server CLASSPATH: D:\TIC\JBOSS_510\jboss-5.1.0.GA\bin\run.jar =============================================================================== 20:09:46,505 INFO [ServerImpl] Starting JBoss (Microcontainer)... 20:09:46,505 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build:SVNTag=JBoss_5_1_0_GA date=200905221053) 20:09:46,505 INFO [ServerImpl] Bootstrap URL: null 20:09:46,505 INFO [ServerImpl] Home Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA 20:09:46,505 INFO [ServerImpl] Home URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/ 20:09:46,521 INFO [ServerImpl] Library URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/lib/ 20:09:46,521 INFO [ServerImpl] Patch URL: null 20:09:46,521 INFO [ServerImpl] Common Base URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/common/ 20:09:46,521 INFO [ServerImpl] Common Library URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/common/lib/ 20:09:46,521 INFO [ServerImpl] Server Name: default 20:09:46,521 INFO [ServerImpl] Server Base Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server 20:09:46,521 INFO [ServerImpl] Server Base URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/ 20:09:46,521 INFO [ServerImpl] Server Config URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/conf/ 20:09:46,521 INFO [ServerImpl] Server Home Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default 20:09:46,521 INFO [ServerImpl] Server Home URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/ 20:09:46,521 INFO [ServerImpl] Server Data Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default\data 20:09:46,521 INFO [ServerImpl] Server Library URL: file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/lib/ 20:09:46,521 INFO [ServerImpl] Server Log Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default\log 20:09:46,521 INFO [ServerImpl] Server Native Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default\tmp\native 20:09:46,521 INFO [ServerImpl] Server Temp Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default\tmp 20:09:46,521 INFO [ServerImpl] Server Temp Deploy Dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default\tmp\deploy 20:09:48,130 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/conf/bootstrap.xml 20:09:50,724 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache] 20:09:50,724 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]] 20:09:51,693 INFO [CopyMechanism] VFS temp dir: D:\TIC\JBOSS_510\jboss-5.1.0.GA\server\default\tmp 20:09:51,693 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled. 20:09:56,037 INFO [ServerInfo] Java version: 1.5.0_08,Sun Microsystems Inc. 20:09:56,052 INFO [ServerInfo] Java Runtime: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03) 20:09:56,052 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_08-b03,Sun Microsystems Inc. 20:09:56,052 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 20:09:56,052 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dg c.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.dirs=D:\TIC\JBOSS_510\jboss-5.1.0.GA\lib\endorsed 20:09:56,177 INFO [JMXKernel] Legacy JMX core initialized 20:10:01,709 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@15837e8[domain=default, server=default, name=default] 20:10:05,052 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 / 20:10:16,771 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core 20:10:16,771 INFO [NativeServerConfig] 3.1.2.GA 20:10:18,990 INFO [AttributeCallbackItem] Owner callback not implemented. 20:10:20,943 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss .mx.server.MBeanServerImpl@6c5356[ defaultDomain='jboss' ] 20:10:45,709 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23644046{vfsfile:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/defau lt/deploy/profileservice-secured.jar/} 20:10:45,709 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23644046{vfsfile:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/defau lt/deploy/profileservice-secured.jar/} 20:10:45,709 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23644046{vfsfile:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/defau lt/deploy/profileservice-secured.jar/} 20:10:45,725 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23644046{vfsfile:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/defau lt/deploy/profileservice-secured.jar/} 20:10:49,975 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector 20:10:50,303 INFO [MailService] Mail Service bound to java:/Mail 20:10:58,772 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages f rom one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 20:10:58,788 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent 20:10:58,975 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent 20:10:59,100 INFO [TransactionManagerService] JBossTS Transaction Service (JTAversion - tag:JBOSSTS_4_6_1_GA) - JBoss Inc. 20:10:59,100 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 20:10:59,663 INFO [TransactionManagerService] Initializing recovery manager 20:10:59,882 INFO [TransactionManagerService] Recovery manager configured 20:10:59,882 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 20:10:59,960 INFO [TransactionManagerService] Starting transaction recovery manager 20:11:00,757 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java .library.path: c:\jdk50\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\oracle\product\10.2.0\client_1\bin;D:\oracle\product\10.2.0\client_1;C:\Program Files\IBM\CICS Transaction Gateway\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\cvsnt;C:\Program Files\PerotSystems\Xcelys\Interop;C:\Program Files\Sybase\SQL Anywhere 9\win32;C:\Program Files\Sybase\Shared\win32;C:\ProgramFiles\Sybase\SQL Anywhere 9\drivers;C:\Program Files\Sybase\Shared\Sybase Central 4.3\win32;C:\Program Files\Sybase\Shared\PowerBuilder;C:\Program Files\Sybase\ InfoMaker 10.5\Tutorial;C:\Program Files\Sybase\Shared\Web Targets;;C:\Program Files\PerotSystems\Xcelys\Interop;D:\TIC\JWSDP\jwsdp-shared\bin 20:11:00,928 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080 20:11:00,944 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009 20:11:01,147 INFO [StandardService] Starting service jboss.web 20:11:01,163 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA 20:11:01,257 INFO [Catalina] Server startup in 304 ms 20:11:01,288 INFO [TomcatDeployment] deploy, ctxPath=/invoker 20:11:02,647 INFO [TomcatDeployment] deploy, ctxPath=/web-console 20:11:03,210 INFO [TomcatDeployment] deploy, ctxPath=/jbossws 20:11:03,397 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml 20:11:03,428 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml 20:11:03,491 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml 20:11:03,538 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml 20:11:03,569 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml 20:11:03,757 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main 20:11:03,803 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 20:11:03,819 INFO [RAMJobStore] RAMJobStore initialized. 20:11:03,819 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' 20:11:03,819 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 20:11:03,819 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 20:11:04,725 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 20:11:05,600 INFO [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started 20:11:05,929 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds 20:11:05,929 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1bd0815 started 20:11:05,975 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 20:11:05,975 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000 20:11:06,007 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds 20:11:06,007 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@41f02d started 20:11:06,007 INFO [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover 20:11:06,007 INFO [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory wil l *not* support load balancing 20:11:06,022 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds 20:11:06,022 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@901849 started 20:11:06,304 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 20:11:07,038 INFO [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar 20:11:07,069 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3 20:11:07,069 INFO [JBossASKernel] with dependencies: 20:11:07,069 INFO [JBossASKernel] and demands: 20:11:07,069 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService 20:11:07,069 INFO [JBossASKernel] and supplies: 20:11:07,069 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView 20:11:07,069 INFO [JBossASKernel] jndi:SecureManagementView/remote 20:11:07,069 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.ManagementView 20:11:07,085 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar 20:11:07,085 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3 20:11:07,085 INFO [JBossASKernel] with dependencies: 20:11:07,085 INFO [JBossASKernel] and demands: 20:11:07,085 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jbo ss.deployers.spi.management.ManagementView 20:11:07,085 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService 20:11:07,085 INFO [JBossASKernel] and supplies: 20:11:07,100 INFO [JBossASKernel] jndi:SecureProfileService/remote 20:11:07,100 INFO [JBossASKernel] jndi:SecureProfileService/remote-org.jbo ss.profileservice.spi.ProfileService 20:11:07,100 INFO [JBossASKernel] Class:org.jboss.profileservice.spi.Profi leService 20:11:07,100 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secu red.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profiles ervice-secured.jar 20:11:07,100 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservic e-secured.jar,name=SecureDeploymentManager,service=EJB3 20:11:07,100 INFO [JBossASKernel] with dependencies: 20:11:07,100 INFO [JBossASKernel] and demands: 20:11:07,100 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService 20:11:07,116 INFO [JBossASKernel] and supplies: 20:11:07,116 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote-org. jboss.deployers.spi.management.deploy.DeploymentManager 20:11:07,116 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote 20:11:07,116 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management .deploy.DeploymentManager 20:11:07,116 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profi leservice-secured.jar 20:11:07,132 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData@cf4da0{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJ B3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true} 20:11:07,147 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData@13a447e{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true} 20:11:07,147 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData@2d19c3{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service =EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true} 20:11:07,475 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3 20:11:07,491 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView 20:11:07,585 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: SecureManagementView/remote - EJB3.x Default Remote Business Interface SecureManagementView/remote-org.jboss.deployers.spi.management.Managemen tView - EJB3.x Remote Business Interface 20:11:07,741 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3 20:11:07,757 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService 20:11:07,788 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: SecureProfileService/remote - EJB3.x Default Remote Business Interface SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface 20:11:07,944 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3 20:11:07,944 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager 20:11:07,975 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI: SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface 20:11:08,288 INFO [TomcatDeployment] deploy, ctxPath=/admin-console 20:11:08,507 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console' 20:11:15,054 INFO [TomcatDeployment] deploy, ctxPath=/ 20:11:15,179 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console 20:11:15,413 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 20:11:15,476 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 20:11:15,507 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 1m:28s:986ms -
5. Re: JBoss 5.1.0 GA - issue with startup time
"binuksuk" wrote:
20:10:20,943 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss .mx.server.MBeanServerImpl@6c5356[ defaultDomain='jboss' ] 20:10:45,709 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@23 644046{vfsfile:/D:/TIC/JBOSS_510/jboss-5.1.0.GA/server/defau lt/deploy/profileservice-secured.jar/}
The similar code take half the time at my end, check this16:01:44,951 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@e3ffdf[ defaultDomain='jboss' ] 16:01:56,746 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@14554400{vfsfile:/home/vicky/JBOSS/freshJBoss5/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
Can you try the results on linux OS and with jdk1.6?
I am able to boot the system under 50 seconds16:02:14,326 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 48s:811ms
-
6. Re: JBoss 5.1.0 GA - issue with startup time
I had to request for a linux m/c. Hence the delay in posting.
On linux, default server starts up in 30 seconds!
Our development environment is on Windows. -
7. Re: JBoss 5.1.0 GA - issue with startup time
I noticed significant delay too. On my XP box the difference is enormous (~ 4 times slower).
D:\apps\jboss-4.2.3.GA>bin\run -c default ... 13:02:18,776 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 20s:48ms
D:\apps\jboss-5.1.0.GA>bin\run -c default ... 13:06:37,650 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 1m:25s:786ms
OS Name : Windows XP OS Version : 5.1 OS Path Level : Service Pack 2 CPU Name : CPU Archecture : x86 CPU Count : 2 Java VM Vendor : Sun Microsystems Inc. Java Version : 1.6.0_16
-
8. Re: JBoss 5.1.0 GA - issue with startup time
Even with the "minimal" server configuration JBoss 5 takes very long in compare to JBoss 4.
D:\apps\jboss-4.2.3.GA>bin\run -c minimal =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: D:\apps\jboss-4.2.3.GA JAVA: D:\Programs\Java\jdk1.6.0_16\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.ser ver.gcInterval=3600000 CLASSPATH: D:\Programs\Java\jdk1.6.0_16\lib\tools.jar;D:\apps\jboss-4.2.3.GA\bin\run.jar =============================================================================== 16:42:09,855 INFO [Server] Starting JBoss (MX MicroKernel)... 16:42:09,855 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439) 16:42:09,855 INFO [Server] Home Dir: D:\apps\jboss-4.2.3.GA 16:42:09,855 INFO [Server] Home URL: file:/D:/apps/jboss-4.2.3.GA/ 16:42:09,855 INFO [Server] Patch URL: null 16:42:09,855 INFO [Server] Server Name: minimal 16:42:09,871 INFO [Server] Server Home Dir: D:\apps\jboss-4.2.3.GA\server\minimal 16:42:09,871 INFO [Server] Server Home URL: file:/D:/apps/jboss-4.2.3.GA/server/minimal/ 16:42:09,871 INFO [Server] Server Log Dir: D:\apps\jboss-4.2.3.GA\server\minimal\log 16:42:09,871 INFO [Server] Server Temp Dir: D:\apps\jboss-4.2.3.GA\server\minimal\tmp 16:42:09,871 INFO [Server] Root Deployment Filename: jboss-service.xml 16:42:10,277 INFO [ServerInfo] Java version: 1.6.0_16,Sun Microsystems Inc. 16:42:10,277 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.2-b01,Sun Microsystems Inc. 16:42:10,293 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 16:42:10,605 INFO [Server] Core system initialized 16:42:11,465 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 16:42:11,715 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started i n 1s:844ms
D:\apps\jboss-5.1.0.GA>bin\run -c minimal Calling D:\apps\jboss-5.1.0.GA\bin\run.conf.bat =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: D:\apps\jboss-5.1.0.GA JAVA: D:\Programs\Java\jdk1.6.0_16\bin\java JAVA_OPTS: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun .rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -server CLASSPATH: D:\apps\jboss-5.1.0.GA\bin\run.jar =============================================================================== 16:41:37,479 INFO [ServerImpl] Starting JBoss (Microcontainer)... 16:41:37,479 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053) 16:41:37,479 INFO [ServerImpl] Bootstrap URL: null 16:41:37,479 INFO [ServerImpl] Home Dir: D:\apps\jboss-5.1.0.GA 16:41:37,479 INFO [ServerImpl] Home URL: file:/D:/apps/jboss-5.1.0.GA/ 16:41:37,479 INFO [ServerImpl] Library URL: file:/D:/apps/jboss-5.1.0.GA/lib/ 16:41:37,479 INFO [ServerImpl] Patch URL: null 16:41:37,479 INFO [ServerImpl] Common Base URL: file:/D:/apps/jboss-5.1.0.GA/common/ 16:41:37,479 INFO [ServerImpl] Common Library URL: file:/D:/apps/jboss-5.1.0.GA/common/lib/ 16:41:37,479 INFO [ServerImpl] Server Name: minimal 16:41:37,479 INFO [ServerImpl] Server Base Dir: D:\apps\jboss-5.1.0.GA\server 16:41:37,479 INFO [ServerImpl] Server Base URL: file:/D:/apps/jboss-5.1.0.GA/server/ 16:41:37,479 INFO [ServerImpl] Server Config URL: file:/D:/apps/jboss-5.1.0.GA/server/minimal/conf/ 16:41:37,479 INFO [ServerImpl] Server Home Dir: D:\apps\jboss-5.1.0.GA\server\minimal 16:41:37,479 INFO [ServerImpl] Server Home URL: file:/D:/apps/jboss-5.1.0.GA/server/minimal/ 16:41:37,479 INFO [ServerImpl] Server Data Dir: D:\apps\jboss-5.1.0.GA\server\minimal\data 16:41:37,479 INFO [ServerImpl] Server Library URL: file:/D:/apps/jboss-5.1.0.GA/server/minimal/lib/ 16:41:37,479 INFO [ServerImpl] Server Log Dir: D:\apps\jboss-5.1.0.GA\server\minimal\log 16:41:37,479 INFO [ServerImpl] Server Native Dir: D:\apps\jboss-5.1.0.GA\server\minimal\tmp\native 16:41:37,479 INFO [ServerImpl] Server Temp Dir: D:\apps\jboss-5.1.0.GA\server\minimal\tmp 16:41:37,479 INFO [ServerImpl] Server Temp Deploy Dir: D:\apps\jboss-5.1.0.GA\server\minimal\tmp\deploy 16:41:38,448 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/D:/apps/jboss-5.1.0.GA/server/minimal/conf/b ootstrap.xml 16:41:39,463 INFO [VFSCacheFactory] Using VFSCache [NoopVFSCache] 16:41:39,542 INFO [CopyMechanism] VFS temp dir: D:\apps\jboss-5.1.0.GA\server\minimal\tmp 16:41:39,542 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled. 16:41:41,682 INFO [ServerInfo] Java version: 1.6.0_16,Sun Microsystems Inc. 16:41:41,682 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_16-b01) 16:41:41,682 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.2-b01,Sun Microsystems Inc. 16:41:41,682 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 16:41:41,682 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dg c.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.di rs=D:\apps\jboss-5.1.0.GA\lib\endorsed 16:41:41,729 INFO [JMXKernel] Legacy JMX core initialized 16:41:46,214 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@55bfaf[domain=default, server=default, name=min imal] 16:41:48,214 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Start ed in 10s:719ms
Is there plan to improve these start up time? -
9. Re: JBoss 5.1.0 GA - issue with startup time
There are many initiatives under way to improve boot time, e.g.:
https://jira.jboss.org/jira/browse/JBAS-7329 -
10. Re: JBoss 5.1.0 GA - issue with startup time
We will be using 5.1.0GA for a while..
Can you please give tips on increasing start up time?
Any config file changes / patches that I can try out? -
11. Re: JBoss 5.1.0 GA - issue with startup time
Ideally, slimming down JBoss should be the first step http://www.jboss.org/community/wiki/JBoss5xTuningSlimming. But that wiki for AS-5 isn't actually updated so i am not sure how much useful that's going to be.
After JBoss AS 5.1.0 was released, there were some fixes around deployment times. Some of it was within EJB3 component. So you might want to apply the latest EJB3 plugin http://www.jboss.org/ejb3/ejb3plugin.html.
The latest EJB3 plugin can be downloaded from here http://www.jboss.org/ejb3/downloads.html.
There was a time consuming deployer (EJB3Deployer) which we had fixed too https://jira.jboss.org/jira/browse/JBAS-7004. But to get this applied to the AS, you will have to checkout JBoss AS 5.1.0 tag, apply the patch and then build it.
I don't know if this is going to be a huge improvement, but we have seen users reporting better deployment times with these changes. Give them a try, if it's feasible.