cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav" <bhais...@apache.org>
Subject Re: Review Request 25289: CLOUDSTACK-7474-Failed-to-start-MS-with-java7-version
Date Thu, 04 Sep 2014 19:13:31 GMT


> On Sept. 3, 2014, 9:32 a.m., Rajani Karuturi wrote:
> > client/tomcatconf/classpath.conf.in, line 37
> > <https://reviews.apache.org/r/25289/diff/1/?file=674877#file674877line37>
> >
> >     Can we get the JAVA_HOME from installed java instead of hardcoding it? The path
may be different for different os versions or distributions. 
> >     
> >     something similar to what we already did at https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=c468228fe807c621decc5919dadae9bcbb38c753
> >     
> >     May we should move this to a common file like setenv.sh and use it everywhere.
> 
> Frank Zhang wrote:
>     +1
> 
> Rayees Namathponnan wrote:
>     Hi Rajani,
>     
>     I checked your change list, if your machine in running with default java version
is 1.6,  this will always return 1.6 and management server will fails to start 
>     
>     
>     Even usage sever will be an issue in 4.5, if your machine is runnign with java1.6
>     https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blobdiff;f=packaging/centos63/cloud-usage.rc;h=8434e4d568a066d0766d055847725b1779eb33c4;hp=617037995755024a8c9d5e492bb56b7cc938e48f;hb=c468228fe807c621decc5919dadae9bcbb38c753;hpb=75c9a20c7773c268c02fb006d1a7820cb427c94c
>     
>     
>     Regards,
>     Rayees
> 
> Alex Brett wrote:
>     To expand on this a little bit - in RHEL 6.3 if you have both Java 1.6 and Java 7
installed, the default behaviour with the alternatives mechanism makes 1.6 the default Java
instance (you can manually set 1.7 as the default, but this is an extra step). This means
that the management server / KVM agent then fail to work.
>     
>     In 6.5 if you have both then by default Java 7 is used, and all works fine (not sure
about 6.4 or 7, I've not tested them).

Since, we want to use 1.7 if available and not 1.6; it makes sense to either use Rajani's
find JAVA_HOME fix as seen in the init scripts, or try searching in paths: JDK_DIRS="/usr/lib/jvm/java-7-openjdk-amd64
/usr/lib/jvm/java-7-openjdk-i386 /usr/lib/jvm/java-6-openjdk /usr/lib/jvm/java-6-openjdk-i386
/usr/lib/jvm/java-6-openjdk-amd64 /usr/lib/jvm/java-6-sun" ... like we used to do before Rajani's
fix


- Rohit


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25289/#review52151
-----------------------------------------------------------


On Sept. 3, 2014, 6:25 a.m., Rayees Namathponnan wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/25289/
> -----------------------------------------------------------
> 
> (Updated Sept. 3, 2014, 6:25 a.m.)
> 
> 
> Review request for cloudstack, Frank Zhang and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-7474
>     https://issues.apache.org/jira/browse/CLOUDSTACK-7474
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> Step 1: Deploy new RHEL 6.3 machine
> Step 2 : Install MS
> Step 3: run deploy script and start MS
> 
> Result 
> 
> Installation completed successfully,  both java7 and java got installed as part of MS
installation, but MS failed to start java version erro
> 
> we need to load java7 while start MS
> 
> 
> Diffs
> -----
> 
>   client/tomcatconf/classpath.conf.in 3ae0fb4 
> 
> Diff: https://reviews.apache.org/r/25289/diff/
> 
> 
> Testing
> -------
> 
> Yes
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message