Reducing JBoss startup time + OSGI + PAX web capability
vijaydaniel Sep 19, 2013 3:27 AMHi,
I'm trying to make a simple web application which is OSGI bundle and using PAX web capability as mentioned in the below thread.
Getting 404 when hitting OSGi WAB servlet deployed on JBoss AS7
But, I have some clarifications regarding the time taken to start JBOSS. After adding this configurations,
<capability name=
"org.ops4j.pax.web:pax-web-jetty-bundle:1.1.2"
/>
<capability name=
"org.ops4j.pax.web:pax-web-jsp:1.1.2"
/>
<capability name=
"org.ops4j.pax.web:pax-web-extender-war:1.1.2"
/>
time taken to start jboss has increased. Is there a better way to configure so that startup time could be reduced?
This is where lot of time is consumed:
[Server:server-one] 12:43:23,135 INFO [org.jboss.osgi.repository.core.RepositoryImpl] (MSC service thread 1-2) found matching caps: [AbstractIdentityCapability[osgi.identity,attributes={content.path=org/ops4j/pax/web/pax-web-jetty-bundle/1.1.2/pax-web-jetty-bundle-1.1.2.jar, osgi.identity=org.ops4j.pax.web.pax-web-jetty-bundle, content.url=file:/software/jboss-as-7.1.1.Final/jboss-7.1.1/domain/servers/server-one/data/osgi-store/bundle-0/repository/org/ops4j/pax/web/pax-web-jetty-bundle/1.1.2/pax-web-jetty-bundle-1.1.2.jar, type=osgi.bundle, version=1.1.2}]]
[Server:server-one] 12:43:23,159 INFO [org.jboss.osgi.repository.core.RepositoryImpl] (MSC service thread 1-2) find providers for: AbstractRequirement[maven.identity,attributes={maven.identity=org.ops4j.pax.web:pax-web-jsp:jar:1.1.2}]
[Server:server-one] 12:45:02,099 INFO [org.jboss.osgi.repository.core.RepositoryImpl] (MSC service thread 1-2) found matching caps: [AbstractIdentityCapability[osgi.identity,attributes={content.path=org/ops4j/pax/web/pax-web-jsp/1.1.2/pax-web-jsp-1.1.2.jar, osgi.identity=org.ops4j.pax.web.pax-web-jsp, content.url=file:/software/jboss-as-7.1.1.Final/jboss-7.1.1/domain/servers/server-one/data/osgi-store/bundle-0/repository/org/ops4j/pax/web/pax-web-jsp/1.1.2/pax-web-jsp-1.1.2.jar, type=osgi.bundle, version=1.1.2}]]
[Server:server-one] 12:45:02,114 INFO [org.jboss.osgi.repository.core.RepositoryImpl] (MSC service thread 1-2) find providers for: AbstractRequirement[maven.identity,attributes={maven.identity=org.ops4j.pax.web:pax-web-extender-war:jar:1.1.2}]
[Server:server-one] 12:46:47,488 INFO [org.jboss.osgi.repository.core.RepositoryImpl] (MSC service thread 1-2) found matching caps: [AbstractIdentityCapability[osgi.identity,attributes={content.path=org/ops4j/pax/web/pax-web-extender-war/1.1.2/pax-web-extender-war-1.1.2.jar, osgi.identity=org.ops4j.pax.web.pax-web-extender-war, content.url=file:/software/jboss-as-7.1.1.Final/jboss-7.1.1/domain/servers/server-one/data/osgi-store/bundle-0/repository/org/ops4j/pax/web/pax-web-extender-war/1.1.2/pax-web-extender-war-1.1.2.jar, type=osgi.bundle, version=1.1.2}]]
My observation is if I haven't configure proxy in JAVA_OPT then these capabilities are not found and I'm not able to make the web app work.
If the proxy is configured correctly then it works as expected [ since these pax bundles are downloaded via net], but the time to start jboss is increased.
Any help here is appreciated.
With Thanks and Regards,
Vijay