0 Replies Latest reply on Feb 27, 2009 1:33 PM by John G

    Improving Startup time - JARDeployer wasteful scanning?

    John G Newbie

      Hi, I'm using JBoss 4.0.4 GA on a Red Hat Linux 4 box. Our app server previously took 10 minutes to startup, but we managed to cut it in half thanks to many of the suggestions here! (especially through editing the JARS Ignored For Scanning list in the EJB3 Deployer).

      However, I'm still trying to improve the speed. In the server.log file, I see hundreds of messages like the following:

      [org.jboss.deployment.JARDeployer] No xml files found


      Turning up the TRACE settings, I see that the RepositoryClassLoader is having the JARDeployer scan hundreds of jar files to determine if a descriptor xml file exists in the META-INF directory.

      After the JARDeployer determines that there are no relevant xml files in the JAR file, it passes it to a Unified Class Loader, as noted in the following line:

      2009-02-26 18:35:29,833(GMT-7) DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/opt/jboss-4.0.4.GA/server/default/deploy/liferay-extranet.ear/lib/secure-filter.jar, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@7cd61b{ url=file:/opt/jboss-4.0.4.GA/server/default/deploy/liferay-extranet.ear/ ,addedOrder=53}


      My questions is this: Is there any way to "speed up" this process? Scanning every file within the JAR seems wasteful and adds about minute to the startup time.

      Ideally, I was hoping I could provide a list of jars so that they are not scanned to see if descriptor xml files exist in there - so far I can't find an Ignore list, like I found with the EJB3 deployer!