I am trying to understand why our standalone application making an EJB call takes about 5-10 seconds longer to start when running agains GlassFish 3.1 compared to GlassFish 2. See below.
Anyone having an idea about what the problem could be?
Could it be the error about the findDerbyClient or javadb client jar file that is the problem?
GlassFish 2:
$ time bin/signserver getstatus brief all
CP: /opt/glassfish3.1/glassfish/lib/gf-client.jar:./conf:./lib/SignServer-AdminCLI.jar:./res/cesecore::./conf/glassfish:/opt/glassfish3.1/glassfish/lib/appserv-rt.jar
Current version of server is : SignServer 3.5.0alpha0
real 0m1.743s
user 0m1.580s
sys 0m0.136s
GlassFish 3.1.2:
$ time bin/signserver getstatus brief all
CP: /opt/glassfish3.1/glassfish/lib/gf-client.jar:./conf:./lib/SignServer-AdminCLI.jar:./res/cesecore::./conf/glassfish:/opt/glassfish3.1/glassfish/lib/appserv-rt.jar
Jul 17, 2013 8:26:07 PM com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
Current version of server is : SignServer 3.5.0alpha0
real 0m12.764s
user 0m13.237s
sys 0m0.396s