[
https://issues.apache.org/jira/browse/TOMEE-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656704#comment-17656704
]
Eric Hamilton commented on TOMEE-4114:
--------------------------------------
Just looking at the documentation differences, TomEE 7.x versions uses Tomcat
8.5.x, where the startStopThreads is documented to support zero and negative
values: [https://tomcat.apache.org/tomcat-8.5-doc/config/host.html]
TomEE 8.x versions uses Tomcat 9.0.x, where the startStopThreads is no longer
documenting support for those values. Maybe that behavior has changed, in
which case you should set your own custom maximum thread count.
> TomEE 8 Webapp Fails to Load
> ----------------------------
>
> Key: TOMEE-4114
> URL: https://issues.apache.org/jira/browse/TOMEE-4114
> Project: TomEE
> Issue Type: Bug
> Reporter: Tim Clapp
> Priority: Major
>
> I can't get a simple webapp (war) to load in TomEE 8.13
> Here's the stack trace:
>
> {code:java}
> SEVERE: Application could not be deployed:
> /Volumes/ext/tomee/apache-tomee-plus-8.0.13/apps/other/tomee8webapp.war
> javax.enterprise.inject.spi.DeploymentException: couldn't start owb context
> at
> org.apache.openejb.cdi.ThreadSingletonServiceImpl.initialize(ThreadSingletonServiceImpl.java:263)
> at org.apache.openejb.cdi.CdiBuilder.build(CdiBuilder.java:43)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:974)
> at
> org.apache.openejb.assembler.classic.Assembler.createApplication(Assembler.java:762)
> at
> org.apache.openejb.assembler.classic.Assembler.buildContainerSystem(Assembler.java:640)
> at org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:497)
> at org.apache.openejb.OpenEJB$Instance.<init>(OpenEJB.java:150)
> at org.apache.openejb.OpenEJB.init(OpenEJB.java:307)
> at org.apache.tomee.catalina.TomcatLoader.initialize(TomcatLoader.java:245)
> at
> org.apache.tomee.catalina.ServerListener.lifecycleEvent(ServerListener.java:165)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:137)
> at org.apache.catalina.startup.Catalina.load(Catalina.java:724)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:760)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
> Caused by: org.apache.openejb.OpenEJBRuntimeException:
> org.apache.webbeans.exception.WebBeansConfigurationException: Problem while
> loading CDI Extensions
> at
> org.apache.openejb.cdi.OpenEJBLifecycle.startApplication(OpenEJBLifecycle.java:200)
> at
> org.apache.openejb.cdi.ThreadSingletonServiceImpl.initialize(ThreadSingletonServiceImpl.java:261)
> ... 20 more
> Caused by: org.apache.webbeans.exception.WebBeansConfigurationException:
> Problem while loading CDI Extensions
> at
> org.apache.webbeans.service.DefaultLoaderService.load(DefaultLoaderService.java:64)
> at
> org.apache.openejb.cdi.OptimizedLoaderService.loadExtensions(OptimizedLoaderService.java:87)
> at
> org.apache.openejb.cdi.OptimizedLoaderService.load(OptimizedLoaderService.java:81)
> at
> org.apache.webbeans.portable.events.ExtensionLoader.loadExtensionServices(ExtensionLoader.java:100)
> at
> org.apache.webbeans.portable.events.ExtensionLoader.loadExtensionServices(ExtensionLoader.java:89)
> at org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:218)
> at
> org.apache.openejb.cdi.OpenEJBLifecycle.startApplication(OpenEJBLifecycle.java:196)
> ... 21 more
> Caused by: java.util.ServiceConfigurationError:
> javax.enterprise.inject.spi.Extension: Provider
> org.apache.bval.cdi.BValExtension could not be instantiated
> at java.util.ServiceLoader.fail(ServiceLoader.java:232)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:566)
> at
> org.apache.webbeans.service.DefaultLoaderService.load(DefaultLoaderService.java:54)
> ... 27 more
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.bval.jsr.xml.ValidationParser
> at
> org.apache.bval.jsr.ConfigurationImpl.createBootstrapConfiguration(ConfigurationImpl.java:416)
> at org.apache.bval.util.Lazy.get(Lazy.java:53)
> at
> org.apache.bval.jsr.ConfigurationImpl.getBootstrapConfiguration(ConfigurationImpl.java:326)
> at org.apache.bval.cdi.BValExtension.<init>(BValExtension.java:92)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380)
> ... 37 more {code}
> The class java is looking for does exist and the path to the jar is set in
> catalina.properties:
> {code:java}
> common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar"
> {code}
> I've verified the value of catalina.base / catalina.home are accurately
> pointing to the correct directories.
> As far as webapps go, is there any real difference between running a webapp
> in TomEE 7 versus TomEE 8 ?
> In TomEE 7, the webapp loads w/o issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
