Hmmm. I think the build.xml is failing because
the database directory doesn’t exist. I should probably add a step to
create it. ;-)
As for the JPA and TPTP projects, just
close them. I proposed in our last DC call that we just mothball them until
after our June deliverable.
If you’re going to run tests (I’ve
been distracted so I haven’t put that wiki page
up yet), just do the following once the runtime is up and cooking:
Start the rmi
registry on some port (I’ll use 9999 for this example)
Run the JMX sample: org.eclipse.cosmos.dc.tests.component.fixture.JMXSample
as a simple java application. You’ll see Waiting forever...
on the command
line.
From the DC OSgi
console:
Osgi> dc load JMXPollingSample.xml
Osgi> dc activate JMXPollingSample
You’ll see samples come in every 2
seconds
Osgi> dc deactivate JMXPollingSample
That’ll stop the collection
Osgi> dc list datasets
Will list all the
captured dataset. Mine looks like this:
dc list datasets
DataSet RandomJVM1180107832535
Source RandomJVM
Start
Fri May 25 11:43:52 EDT 2007
Stop
Fri May 25 11:43:52 EDT 2007
Flow Application:DemoKeyset
Type Application
Dimensions
Dim DemoKey1
Dim DemoKey2
Dim DemoKey3
DataSet RandomJVM1180107910415
Source RandomJVM
Start
Fri May 25 11:45:10 EDT 2007
Stop
Fri May 25 11:45:10 EDT 2007
Flow Application:DemoKeyset
Type Application
Dimensions
Dim DemoKey1
Dim DemoKey2
Dim DemoKey3
You can then run the query like this:
Osgi> spec query stat StatQuery
RandomJVM1180107910415 DemoKeyset "Fri May 25 11:43:52 EDT 2007" "Fri May 25 11:43:53 EDT 2007"
Of course, you’ll
have to change the dataset name and timestamps, but you get the idea.
Cheers,
Joel
=00