That doesn't seem right at all. How many EJBs/EntityManagers are you deploying? I've done some profiling with a EJB jar and one EntityManager being deployed. It takes 4-5 secs on my machine (3.4 GhZ). 80% of the time is in bootstrapping the kernel. This should be a fixed time. The 20% left, most of it is initializing Hibernate.
Also, maybe you are not writing your JUnit test correctly and are bootstrapping the container with every test method? Please download Alpha 3 and check out the JUnit example for how to initalize the kernel just once for the entire class run. Let me know.... Bill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911492#3911492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911492 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
