CDV ❯ SIGAR libraries not included when using mvn tc:run
-
Bug
-
Status: Closed
-
1 Critical
-
Resolution: Fixed
-
Kit & Installation
-
-
qa
-
Reporter: ari
-
December 02, 2008
-
0
-
Watchers: 0
-
February 12, 2013
-
February 03, 2009
Description
As far as I can tell, when using maven to build and run Terracotta-based apps, sigar is not included at all. If I look in ~/.m2/repository all I find is tc jars. No binaries and, as a result, the L1 and L2 will both start w/o sigar present.
To reproduce:
- install examinator from svn
- run mvn tc:run (after compile and hibernate3:hbm2dll)
- then download and install 2.7.1 into another directory
- cd to the installed directory and run bin/admin.sh
- go to either clients or server runtime stats and it will show an error in place of CPU stats.
Here’s some proof that I am not running JDK 1.6 or some silliness
$ java -version java version “1.5.0_16” Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284) Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing) $ which java /usr/bin/java $ echo $JAVA_HOME /Library/Java/Home $ ls -la /usr/bin/java lrwxr-xr-x 1 root wheel 74 Sep 29 11:01 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java ari-laptop:~ ari$
Comments
jvoegele 2009-01-29
nadeem ghani 2009-01-29
This still seems broken
Starting admin.sh under either kit, connecting to a cluster started with mvn tc:run (in exam/branches/tc-2.7 or exam/tags/release1.0.3) Host CPU panel shows error message for both server and clients
Hung Huynh 2009-01-29
I think you might have tested against an old version of 2.7.4-SNAPSHOT (which was built a couple days back without Jason’s fix)
If you test with examinator/tc-2.7, it’s certainly the case.
Test with examinator/trunk, that should be latest.
jvoegele 2009-01-30
Hung is correct that 2.7.4-SNAPSHOT doesn’t contain my fixes yet. Once we start publishing nightlies of 2.7.4-SNAPSHOT again the fix will be available. Until then, the fix is only in trunk/2.8.0-SNAPSHOT
nadeem ghani 2009-01-30
deleting the maven repo and running again shows this is fixed
Fiona OShea 2009-02-03
Resolving based on Nadeems comment
Applied fixes to trunk and 2.7 branch. QA please verify.