We have been testing for 10.1.0 CR1 and we see 20-30 second pauses in server startup during deployment phase. Previous versions (WLF 8-9) did not contain these pauses with our app and thus startup & deployment in those versions are much faster.

With info level logging on everything seems just be frozen for 20-30 seconds. When turning debug level logging on it seems that those pauses come from weld bootstrapping:

Weld Bootstrap part starts:

10:10:01,577 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000106: Bean: Implicit Bean [javax.enterprise.inject.spi.Interceptor] with qualifiers [@Default]

10:10:01,666 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000106: Bean: Built-in Bean [javax.transaction.UserTransaction] with qualifiers [@Default]

10:10:01,666 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000106: Bean: Implicit Bean [javax.enterprise.inject.spi.Bean] with qualifiers [@Default]

10:10:01,666 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000106: Bean: Managed Bean [class com.samaxes.filter.CacheFilter] with qualifiers [@Any @Default]

...

Weld Bootstrapping is already run for over 10 seconds and after this line comes 12s pause:

10:10:13,454 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000106: Bean: ValidatorBean [id=org.hibernate.validator.internal.cdi.ValidatorBean_default]

10:10:25,989 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000100: Weld initialized. Validating beans

10:10:27,028 DEBUG [org.jboss.weld.Reflection] (Weld Thread Pool -- 7) WELD-000620: interface javax.enterprise.inject.Intercepted is not declared @Target(METHOD, FIELD, PARAMETER, TYPE). Weld will use this annotation, however this may make the application unportable.

10:10:27,029 DEBUG [org.jboss.weld.Reflection] (Weld Thread Pool -- 7) WELD-000620: interface javax.enterprise.inject.Decorated is not declared @Target(METHOD, FIELD, PARAMETER,

TYPE). Weld will use this annotation, however this may make the application unportable.

10:10:27,069 DEBUG [org.jboss.weld.Bootstrap] (MSC service thread 1-5) WELD-000145: Bean identifier index built

Overal startup & deployment time is now around 60s.

Same app & machine with WLF 8.2:

14:08:34,662 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 38008ms - Started 12210 of 12390 services (292 services are lazy, passive or on-demand)

And with the WLF 10.1.0 CR1:

14:11:14,657 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.CR1 (WildFly Core 2.2.0.CR9) started in 60518ms - Started 12121 of 12483 services (616 services are lazy, passive or on-demand)

Is there any known issues related to slow startup in Wildfly 10 (tried to search issues related to it but couldn't find any). Or can we change our app some way to boost the weld bootstrapping?

Br,

Petri