Bindings

This document gives an overview of the most important bindings used in the JET framework. Bindings can also be called settings or properties. For information on how to set these, please refer to the SettingBindings document.

Machines and Rigs

Use these settings to tell JETBatch and JET which machines to run on.

jet.clientmachines: The machines (or JAG instances) to use as clients, comma separated, accepts hostname and port separated by colon

jet.servermachines: The machines (or JAG instances) to use as servers, comma separated, accepts hostname and port separated by colon

jet.rig.name

Used to communicate the name of the rig from JETBatch ro JET

jetbatch.rigs.clients: The number of client machines per rig

jetbatch.rigs.servers: The number of server machines per rig

jetbatch.rigs_per_machine: The number of rigs per machine (e.g run two tests per machine)

jetbatch.rigs_per_machine.client and .server: The possibility to create two rigs with one server and one client on three machines, where the clients share machine

Logging

jet.testlogpath: The path where JET will store its logs

jetbatch.finallogpath: The path where JETBatch stores its logs

JET can have many log handlers. They are set up like this:

jet.loghandler.<nr>.name: The name of the log handler, this is used to name the log file

jet.loghandler.<nr>.level: The lowest log level that will be logged to this log file, e.g. INFO, FINE, FINER, FINEST.

jet.loghandler.<nr>.logger: The packages that should be logged here, can be comma separated

Example:

 jet.loghandler.4.name=jetMemcachedINFO
 jet.loghandler.4.level=INFO
 jet.loghandler.4.logger=com.sun.jet.examples.memcached

It is normal to add loghandlers to the testsuite_jetdefaults.properties, for ones own test suite to be logged in special files.

Resources

jet.portbase: Set a port base so that your tests does not try to use the same network ports as other users.

jet.primarynetprefix: Used to get JAG and JET to use a special network if there are several networks on a machine

Test Runs

jet.maxduration: The default maximum duration of a test run in minutes

jet.waitstoptimeout: The number of milliseconds to wait for a client to stop after the call to stop()

Test Code

jag.jagopsjars: The names of the jar files that will be put in the JAG classloader, which you can load Ops and MBeans from

jet.installpath<name>: Directory that will be transfered to machines that run this test

jet.installpath<name>.subdirs: Subdiractories that will be copied

jet.installpath<name>.classpath: JAR files to place in the classpath when one start JET

See WriteTestSuite for more information.

JAG

jetbatch.start.jag: true or false - whether or not to start JAG embedded

jet.jag.port.http: The Port number JET uses to communicati with JAG for HTTP communication

jet.jag.port.jmxmp: The Port number JET uses to communicati with JAG for JMX MP communication

JET

jet.memory.max: The maximum heap size for the JVM that JET runs

jet.memory.min: The minimum heap size for the JVM that JET runs

jet.jvm.*: Makes it possible to configure more advanced settings for the JVM to run JET with. Important if you are testing Java software that runs in the JET JVM, and you want to try different architectures