0 Replies Latest reply on Mar 1, 2010 7:21 PM by Dan Seaver

    Server boot time issue

    Dan Seaver Newbie
      I've just upgraded  from JBoss AS 4.2 to 5.1 and have encountered a boot time issue that did not  exist with 4.2. If I start the server while connected to my company's VPN, it  takes 5:32 mins. With 4.2, it took about 1 min. If I start the server  disconnected from the VPN, but still connected to internet (high speed cable),  it takes about 1:40 mins. If I disable my network card, it takes 1:10 mins. I  have not made any modifications to the server configuration that ships in the  jboss-5.1.0.GA-jdk6.zip (also tried the jboss-5.1.0.GA.zip with the same  results).
      Any ideas on why the  server startup would be network sensitive?
      After turning on  debug level logging for everything, I found these performance  killers:
      2010-02-25  12:56:31,003 DEBUG [org.jboss.management.j2ee.deployers.LocalJBossServerDomain]  (main) handleNotification:  javax.management.Notification[source=jboss.system:service=ServiceController][type=org.jboss.system.ServiceMBean.start][message=]
      2010-02-25  12:56:43,466 FINE  [sun.rmi.transport.tcp] (RMI Scheduler(0)) RMI Scheduler(0):  close connection
      2010-02-25 12:56:43,481 FINE  [sun.rmi.transport.tcp] (RMI  TCP Connection(2)- RMI TCP Connection(2)- (port 1851)  connection closed
      2010-02-25 12:56:43,481 FINE  [sun.rmi.transport.tcp] (RMI  TCP Connection(2)- RMI TCP Connection(2)- close  connection
      2010-02-25 12:56:43,481 FINE  [sun.rmi.transport.tcp] (RMI  Scheduler(0)) RMI Scheduler(0): close connection
      2010-02-25 12:56:43,481  FINE  [sun.rmi.transport.tcp] (RMI TCP Connection(1)- RMI TCP  Connection(1)- (port 1090) connection closed
      2010-02-25  12:56:43,481 FINE  [sun.rmi.transport.tcp] (RMI TCP Connection(1)-  RMI TCP Connection(1)- close connection
      2010-02-25 12:57:56,347  DEBUG [org.jboss.remoting.ServerInvoker] (main)  SocketServerInvoker[HCU-C1WYGC1:4446] added org.jboss.profileservice.management.upload.remoting.DeployHandler@18309b0 for subsystem 'DeploymentManager'
      As you can see,  SocketServerInvoker takes over a minute.
      2010-02-25  12:57:56,347 DEBUG [org.jboss.profileservice.management.ManagementViewImpl]  (main) addTemplate: org.jboss.resource.deployers.management.DsDataSourceTemplate@98843
      2010-02-25  12:57:56,347 DEBUG [org.jboss.profileservice.management.ManagementViewImpl]  (main) addTemplate: org.jboss.resource.deployers.management.DsDataSourceTemplate@1d11c11
      2010-02-25  12:59:21,346 DEBUG [org.jboss.profileservice.remoting.ProxyFactory] (main) Bound  ProfileService proxy under: ProfileService
      2010-02-25 12:59:21,424 DEBUG  [org.jboss.profileservice.remoting.ProxyFactory] (main) Created ManagementView  proxy
      Here, ProxyFactory  takes over a minute
      2010-02-25  12:59:28,508 DEBUG [org.jboss.aop.microcontainer.beans.GenericBeanAspectFactory]  (main) Creating advice InvocationContextInterceptor with loader  null
      2010-02-25 12:59:32,573 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger]  (Thread-14) Periodic recovery - second pass <Thu, 25 Feb 2010  12:59:32>
      2010-02-25 12:59:32,589 DEBUG  [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-14)  AtomicActionRecoveryModule: Second pass
      2010-02-25 13:00:24,142 DEBUG  [org.apache.catalina.session.ManagerBase]  (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions  StandardManager at 1267131624142 sessioncount 0
      Here, ManagerBase  takes nearly a minute.
      Thanks for any / all  help you can throw my way.