Yicong-Huang opened a new issue, #6204:
URL: https://github.com/apache/texera/issues/6204
### What happened?
After #6201 (Hadoop 3.4.3 upgrade), `texera-web` crashes during Dropwizard
startup with `NoClassDefFoundError:
com/sun/jersey/core/provider/jaxb/AbstractRootElementProvider`. Hadoop 3.4
replaced `com.sun.jersey:jersey-json` with the fork
`com.github.pjfanning:jersey-json`, which the existing
`ExclusionRule(organization = "com.sun.jersey")` rules in
`common/workflow-core/build.sbt` and `amber/build.sbt` do not catch. Its
`META-INF/services` entries register Jersey 1 providers whose superclasses live
in the (excluded) jersey-core 1.x, so Jersey 2's ServiceFinder dies loading
them. Expected: the service boots. Fix: also exclude `com.github.pjfanning`
from the hadoop dependencies (jersey-json only serves hadoop's own web
endpoints; Iceberg/HDFS paths don't need it).
### How to reproduce?
On `main`, start `texera-web` (e.g. `bin/local-dev.sh up texera-web`); it
exits during Jetty startup.
### Version/Branch
1.3.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
1094a656953df71244ac1060c8082568e7bdcc58
### What browsers are you seeing the problem on?
_No response_
### Relevant log output
```shell
java.lang.NoClassDefFoundError:
com/sun/jersey/core/provider/jaxb/AbstractRootElementProvider
at
org.glassfish.jersey.internal.ServiceFinder$AbstractLazyIterator.hasNext(ServiceFinder.java:577)
...
at
org.apache.texera.web.TexeraWebApplication$.main(TexeraWebApplication.scala:77)
Caused by: java.lang.ClassNotFoundException:
com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
