[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861758#comment-15861758
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9780:
--------------------------------------------

Github user swill commented on the issue:

    https://github.com/apache/cloudstack/pull/1938
  
    So the short answer is that I ran into this issue when I upgraded and since 
`jenv` did not correctly set the `JAVA_HOME` directory, I ran into this, so I 
don't have a deep understanding for all the details.  I made this change in my 
environment and everything worked.  I understand this is not a good answer, but 
that is what I have.
    
    I don't install to that path either, but for some reason it was populated 
in my environment.  Can you do an `$ ll /usr/lib/jvm/` and post what you get?  
I am curious what it would return.  
    
    Here is the result from my CentOS 6.8 setup.
    
    
![image](https://cloud.githubusercontent.com/assets/13644/22841453/ae384516-ef9f-11e6-835a-60736d6a03dc.png)
    
    The way I see it right now, people WILL run into this issue.  This at least 
reduces the number of people who have problems.  



> Default to Java8 if JAVA_HOME is not set
> ----------------------------------------
>
>                 Key: CLOUDSTACK-9780
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9780
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.10.0.0
>            Reporter: Will Stevens
>
> Now that PR1888 is merged, Java8 is required.  Unfortunately the file pushed 
> to `/etc/cloudstack/management/classpath.conf` will default to Java7 if the 
> JAVA_HOME is not set.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to