You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/09/16 04:54:00 UTC
[jira] [Updated] (PHOENIX-6136) javax.servlet.UnavailableException
thrown when using Spark connector
[ https://issues.apache.org/jira/browse/PHOENIX-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth updated PHOENIX-6136:
---------------------------------
Description:
We get en exception from Spark when using the phoenix-spark connector.
{noformat}
2020-09-11 13:29:28,252 WARN [main] component.AbstractLifeCycle: FAILED org.glassfish.jersey.servlet.ServletContainer-62c42a3@f5c8fa49==org.glassfish.jersey.servlet.ServletContainer,jsp=null,order=-1,inst=true,async=true: javax.servlet.UnavailableException: Servlet class org.glassfish.jersey.servlet.ServletContainer is not a javax.servlet.Servlet
javax.servlet.UnavailableException: Servlet class org.glassfish.jersey.servlet.ServletContainer is not a javax.servlet.Servlet
at org.spark_project.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:505)
This seems to be caused by a conflict between the servlet implementation of jetty, and jersey.{noformat}
Shading both Jersey libraries in phoenix-client has solved the problem for us.
was:
We get en exception from Spark when using the phoenix-spark connector.
2020-09-11 13:29:28,252 WARN [main] component.AbstractLifeCycle: FAILED org.glassfish.jersey.servlet.ServletContainer-62c42a3@f5c8fa49==org.glassfish.jersey.servlet.ServletContainer,jsp=null,order=-1,inst=true,async=true: javax.servlet.UnavailableException: Servlet class org.glassfish.jersey.servlet.ServletContainer is not a javax.servlet.Servlet
javax.servlet.UnavailableException: Servlet class org.glassfish.jersey.servlet.ServletContainer is not a javax.servlet.Servlet
at org.spark_project.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:505)
This seems to be caused by a conflict between the servlet implementation of jetty, and jersey.
Shading both Jersey libraries in phoenix-client has solved the problem for us.
> javax.servlet.UnavailableException thrown when using Spark connector
> --------------------------------------------------------------------
>
> Key: PHOENIX-6136
> URL: https://issues.apache.org/jira/browse/PHOENIX-6136
> Project: Phoenix
> Issue Type: Bug
> Components: core, spark-connector
> Affects Versions: 5.1.0
> Reporter: Tamas Adami
> Assignee: Istvan Toth
> Priority: Major
>
> We get en exception from Spark when using the phoenix-spark connector.
> {noformat}
> 2020-09-11 13:29:28,252 WARN [main] component.AbstractLifeCycle: FAILED org.glassfish.jersey.servlet.ServletContainer-62c42a3@f5c8fa49==org.glassfish.jersey.servlet.ServletContainer,jsp=null,order=-1,inst=true,async=true: javax.servlet.UnavailableException: Servlet class org.glassfish.jersey.servlet.ServletContainer is not a javax.servlet.Servlet
> javax.servlet.UnavailableException: Servlet class org.glassfish.jersey.servlet.ServletContainer is not a javax.servlet.Servlet
> at org.spark_project.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:505)
> This seems to be caused by a conflict between the servlet implementation of jetty, and jersey.{noformat}
> Shading both Jersey libraries in phoenix-client has solved the problem for us.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)