[
https://issues.apache.org/jira/browse/AMBARI-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965519#comment-14965519
]
Hudson commented on AMBARI-13490:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.1 #714 (See
[https://builds.apache.org/job/Ambari-branch-2.1/714/])
AMBARI-13490. If there are more than one ambari-server*jar in classpath
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8bc1a98a5d50c78d9adb0f350d3dedaa9d723548])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
> If there are more than one ambari-server*jar in classpath we should fail to
> start
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-13490
> URL: https://issues.apache.org/jira/browse/AMBARI-13490
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> The problem was due to they had older version of ambari-server*.jar in
> /usr/lib/ambari-server, which they put there by themselves.
> The point of this jira is to pre-check this issue on stage of accessing
> ambari-server binary.
> And give the user appropriate message so he can move out his custom jar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
