Faster deployment to Glassfish

I meet Jerome Dochez a two weeks ago and complained slow deployment to Glassfish. Our J2EE application that is developed in our team as referential application with EJB 3.0 has about ten entity and session beans. Deployment this application with one EJB and one web module took about 40 sec. I think that it's too much. Jerome suggested me to try to disable security manager in Glassfish. Therefore, I commented out following line with jvm-options in domain.xml file:
<jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy</jvm-options>
Then restarted server and deployed application. The deployment took 25 sec. It means deployment time was decreased by 37 percent. I think that doesn't make a sense use security manager on testing servers and I guess that many users don't need this feature. This security feature can be setup during server's installation. There might be a panel where user can select which type of server's configuration he wants: production or development and when he selects development mode the security manager can be disabled and logging can be switched to higher level, ...
Comments:

Security will be out by default, starting Build 39 of GlassFish, so you'll see this performance improvement immediately, out of the box... Wait for a few days or hours:-) We are at build 38 currently.

Posted by ludo on February 24, 2006 at 04:44 AM CET #

Post a Comment:
Comments are closed for this entry.
About

pblaha

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
Bookmarks