You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2023/06/01 13:11:00 UTC

[jira] [Resolved] (HBASE-27820) HBase is not starting due to Jersey library conflicts with javax.ws.rs.api jar

     [ https://issues.apache.org/jira/browse/HBASE-27820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wellington Chevreuil resolved HBASE-27820.
------------------------------------------
    Resolution: Fixed

Also merged the branch-2.4 PR.

> HBase is not starting due to Jersey library conflicts with javax.ws.rs.api jar
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-27820
>                 URL: https://issues.apache.org/jira/browse/HBASE-27820
>             Project: HBase
>          Issue Type: Task
>          Components: dependencies
>    Affects Versions: 3.0.0-alpha-3
>            Reporter: Rahul Agarkar
>            Assignee: Rahul Agarkar
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
>
>
> With some recent Atlas changes for supporting HTTP based hook support, HBase is not starting because of conflicts between jersey jars and rs-api jar.
> This Jira is to exclude the javax.ws.rs-api.jar from the HBase classpath.
> HBase uses shaded jersey jars and hence does not need to use this jar directly. However, it still adds this jar to the CLASSPATH while starting the server. Atlas on the other hand is using a non-shaded version of javax.ws.rs-api jar which causes this conflict and causes the hbase server fail while initializing atlas co-processor.
> Since hbase is using shaded jersey jar and not using this jar directly, it should be removed from the bundle as it may cause similar conflicts with other client applications potentially using it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)