[jboss-dev] Small boottime improvement

[Kabir Khan]

I am trying to do as you suggested, and am getting a problem that the server shuts itself down right away.

18:22:28,712 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.SNAPSHOT (build: SVNTag=JBoss_6.0.0-SNAPSHOT date=r100814)] Started in 10s:799ms
18:22:28,730 INFO  [STDOUT] Posting Shutdown Request to the server...
18:22:37,188 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] Stopping: JBossAS [6.0.0.SNAPSHOT (build: SVNTag=JBoss_6.0.0-SNAPSHOT date=r100814)]
18:22:37,298 INFO  [service] Restored bootstrap log handlers
18:22:43,686 INFO  [AbstractServer] Stopped: JBossAS [6.0.0.SNAPSHOT (build: SVNTag=JBoss_6.0.0-SNAPSHOT date=r100814)] in 6s:497ms

I'm trying to figure out what needs to remain in the deploy/ folder for the server to stay up, does anybody know what is required?

On 15 Feb 2010, at 15:35, Bill Burke wrote:

> 
> 
> Kabir Khan wrote:
>> 
>> Now that I'm more into profiling stuff, I'll see if profiling minimal as suggested by Bill makes more sense to me, if not I'll do a few more cycles of these.
>> 
> 
> You also might want to try removing stuff in deploy/ and just deploying 
> deployers (you'll need to remove the war and weld deployers though). 
> That may shed more light on things too.  Its how I found the deployer 
> sorting issue.
> 
> Correct me if I'm wrong, but after VFS3 is in, the next big thing I saw 
> is probably BeanInfo creation (all the reflection stuff).  I personally 
> don't think the JDK hacks that Carlo came up with for reflection are a 
> good idea.  This is why I thought all projects might want to consider 
> making their beans more coarse grain and do IoC within code.
> 
> 
> 
> -- 
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development