While looking at system call traces from domain startup, I'm seeing
that the derby JAR files are being accessed very early, i.e., before
OSGi bundles are read in.
Is this expected?
What causes derby to be brought into the system?
AFAIK, there isn't anything in the startup benchmark application that
uses a database.
Can we gain some improvement in startup time if we avoid bringing in derby?
Thanks.
Tom