You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Neil Griffin (Jira)" <ji...@apache.org> on 2022/04/05 00:01:00 UTC
[jira] [Commented] (PLUTO-798) java 11 compatibility
[ https://issues.apache.org/jira/browse/PLUTO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517161#comment-17517161 ]
Neil Griffin commented on PLUTO-798:
------------------------------------
[~florian.hof]: Thank you so much for creating this issue and providing detailed findings as to how to make Pluto compatible with Java 11.
Pluto is basically on an annual release schedule. The last release was in December 2021 so the next release won't take place until (or sometime after) December 2022. At that time we will consider both Java 11 and Tomcat 9, and your findings will be very helpful to us. Thanks again.
> java 11 compatibility
> ---------------------
>
> Key: PLUTO-798
> URL: https://issues.apache.org/jira/browse/PLUTO-798
> Project: Pluto
> Issue Type: Improvement
> Affects Versions: 3.1.1
> Reporter: Florian Hof
> Assignee: Neil Griffin
> Priority: Major
>
> Please make Pluto working out-of-the-box with java 11. With the bundled tomcat, following steps are required:
> * Remove folder _endorsed_ or do not set the env variable _JAVA_ENDORSED_DIRS_ in the startup scripts.
> * Add Jaxb dependencies to Pluto's _lib_ because Jaxb disapears in java 11. More info in [Java 11 package javax.xml.bind does not exist|https://stackoverflow.com/questions/52502189/java-11-package-javax-xml-bind-does-not-exist]. I added the 3 jaxb-api.jar, jaxb-core.jar, xaxb-impl.jar but don't know if all are needed.
> That is sufficient to start Pluto on Tomcat. By the way, is there a plan to bundle Tomcat 9? (?)
> Deploying a portlet developed with the framework _OpenXava_ having the libraries _jandex.jar_ , _jboss-logging.jar_ and others gives the following error when starting. The not found class _UnsupportedVersion_ is in {_}jandex.jar{_}, so I suspect an older library is overriding it. Do you already experenced this problem? Have you a solution? (?)
> {noformat}
> java.lang.IllegalStateException: Erreur lors du démarrage du conteneur fils
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695)
> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1016)
> at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1903)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.catalina.LifecycleException: Echec de démarrage du composant [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/SCIS]]
> at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:755)
> ... 9 more
> Caused by: java.lang.IllegalStateException: WELD-ENV-000026: Unable to instantiate org.jboss.weld.environment.deployment.discovery.jandex.JandexDiscoveryStrategy using parameters: [org.jboss.weld.environment.deployment.WeldResourceLoader@11927f6a, org.jboss.weld.bootstrap.WeldBootstrap@54c936d6, [interface javax.enterprise.context.Dependent, interface javax.enterprise.context.RequestScoped, interface javax.enterprise.context.ConversationScoped, interface javax.enterprise.context.SessionScoped, interface javax.enterprise.context.ApplicationScoped, interface javax.interceptor.Interceptor, interface javax.decorator.Decorator, interface javax.enterprise.inject.Model, interface javax.enterprise.context.NormalScope, interface javax.enterprise.inject.Stereotype]].
> at org.jboss.weld.environment.deployment.discovery.DiscoveryStrategyFactory.create(DiscoveryStrategyFactory.java:58)
> at org.jboss.weld.environment.servlet.WeldServletLifecycle.createDeployment(WeldServletLifecycle.java:291)
> at org.jboss.weld.environment.servlet.WeldServletLifecycle.initialize(WeldServletLifecycle.java:155)
> at org.jboss.weld.environment.servlet.EnhancedListener.onStartup(EnhancedListener.java:61)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5221)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> ... 10 more
> Caused by: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> at org.jboss.weld.environment.deployment.discovery.DiscoveryStrategyFactory.create(DiscoveryStrategyFactory.java:56)
> ... 15 more
> Caused by: java.lang.NoClassDefFoundError: org/jboss/jandex/UnsupportedVersion
> at org.jboss.weld.environment.deployment.discovery.jandex.JandexDiscoveryStrategy.<init>(JandexDiscoveryStrategy.java:63)
> ... 20 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.jandex.UnsupportedVersion
> at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 21 more{noformat}
> {{ }}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)