I just tried to run Druid 0.15.1 against Java11, but got an exception: https://gist.github.com/Fokko/72b57edd47e2d2da08426bf6caca6d55
This also killed the processes. Not sure if this is already fixed in master. I'll dive into it later. Cheers, Fokko Op di 27 aug. 2019 om 09:41 schreef Clint Wylie <clint.wy...@imply.io>: > I just tested latest master with openjdk 12 and saw the same error in my > logs, however overall things appeared to be functioning. I was able to > bring up a cluster, index some data with native batch, and query the > resulting segments. Maybe we call it "experimental" and let people help us > shake out the issues? ;) > > On Mon, Aug 26, 2019 at 10:47 PM David Lim <david...@apache.org> wrote: > > > Hey Druids, > > > > Recently I've been seeing more activity around Java 11 support, both from > > the side of user inquiries and from contributors submitting patches to > > resolve compatibility issues. I thought it would be worthwhile to have a > > thread to identify: > > > > - the level of testing that has been done so far by community members > > (including of various extensions and ingestion methods); related, it > would > > be helpful to know if anyone has been running Druid in production on Java > > 11 > > - if there are any known remaining issues that need to be addressed > > - in which release does the community feel comfortable declaring official > > Java 11 support > > > > I ran through the quickstart and now everything is starting up, but I ran > > into some issues with JAXB even after [ > > https://github.com/apache/incubator-druid/pull/7604] went in (see stack > > trace at end - Google search seems to indicate we also need to include > > org.glassfish.jaxb:jaxb-runtime). > > > > Big thanks to @xvrl for spearheading much of the work on Java 11 support, > > most of which is linked from the issue: > > https://github.com/apache/incubator-druid/issues/5589. Xavier, do you > know > > of any significant areas of the codebase that need to be looked at before > > we can declare Java 11 support? What about issues/restrictions around > > Hadoop integration? > > > > --- > > 2019-08-27T05:05:54,776 ERROR [main] > > com.sun.jersey.server.impl.wadl.WadlApplicationContextImpl - > Implementation > > of JAXB-API has not been found on module path or classpath. > > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > found > > on module path or classpath. > > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:177) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at javax.xml.bind.ContextFinder.find(ContextFinder.java:364) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:508) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:465) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:366) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at > > > > > com.sun.jersey.server.impl.wadl.WadlApplicationContextImpl.<init>(WadlApplicationContextImpl.java:107) > > [jersey-server-1.19.3.jar:1.19.3] > > ... > > Caused by: java.lang.ClassNotFoundException: > > com.sun.xml.internal.bind.v2.ContextFactory > > at java.base/ > > > > > jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > > ~[?:?] > > at > > > > > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > > ~[?:?] > > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] > > at > > > > > javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:122) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at > > > javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:155) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:174) > > ~[jaxb-api-2.3.1.jar:2.3.0] > > >
