[ 
https://issues.apache.org/jira/browse/TOMEE-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763527#comment-16763527
 ] 

Salomon Mayengue commented on TOMEE-2465:
-----------------------------------------

Can some of the Jira admins please assign this ticket to me : [~mayens]  ?
 * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13204826]

> JDK 11 compatibility on Tomee 7.1.1
> -----------------------------------
>
>                 Key: TOMEE-2465
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2465
>             Project: TomEE
>          Issue Type: Bug
>    Affects Versions: 7.1.1
>            Reporter: Salomon Mayengue
>            Priority: Major
>
> Hello, 
> I started to use the TomEE 7.1.1-SNAPSHOT with JDK 11 and I still have issue 
> related to unSafeClass exception. Here is the complete stacktrace: 
> --------------------------
> 06-Feb-2019 10:42:03.955 INFO [pc04141-startStop-1] 
> org.apache.openejb.cdi.OpenEJBLifecycle.startApplication OpenWebBeans 
> Container has started, it took 223 ms.
> 06-Feb-2019 10:42:03.974 SEVERE [Catalina-startStop-1] 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke A child container failed 
> during start
>  java.util.concurrent.ExecutionException: 
> org.apache.catalina.LifecycleException: Failed to start component 
> [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]]
>  at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
>  at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
>  at 
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942)
>  at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872)
>  at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>  at 
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1420)
>  at 
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1410)
>  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:825)
> Caused by: org.apache.catalina.LifecycleException: Failed to start component 
> [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]]
>  at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
>  ... 6 more
> Caused by: java.lang.NoClassDefFoundError: 
> org.apache.openejb.util.proxy.LocalBeanProxyFactory$Unsafe (initialization 
> failure)
>  at 
> java.base/java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:141)
>  at 
> org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:137)
>  at 
> org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:147)
>  at 
> org.apache.tomee.catalina.TomcatWebAppBuilder.eagerInitOfLocalBeanProxies(TomcatWebAppBuilder.java:1563)
>  at 
> org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1441)
>  at 
> org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1125)
>  at 
> org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:133)
>  at 
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94)
>  at 
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5154)
>  at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>  ... 6 more
> --------------------------
> To fix this issue in my branch, I applied the same corrections of 
> - TOMEE-2272
> - + jdk 11 compatibility on LocalBeanProxyFactory.java (cf 
> 37e56343b92996ef3bed4535a2728c034f8d7725 of master branch)
> So , in order to make 7.1.1 version fully compatible with JDK 11, do you plan 
> to report these changes in the 7.1.X branch?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to