prime client manager log

Messages from: 10.0.0.3:1084
-> 2013-10-25 18:42:44:841 Starting Controller; bindWait = 45000
-> 2013-10-25 18:42:44:849 waiting for: Binding controller to /
-> rec'd notifyInterrupt(101) call
-> Binding controller to //client01:2098/Controller
-> Launcher: done in waitMatch(0)
-> 2013-10-25 18:43:30:113 Starting Agents
-> ---------------//client01:2098/Controller
-> Calling switchLog as master
-> url[0] is : http://specemulator:8080/Emulator/EmulatorServlet?cmd=switchlog
-> url[1] is : http://specdelivery:8000/Supplier/DeliveryServlet?cmd=switchlog
-> calling driver.waitMatch(0)...
-> 2013-10-25 18:44:15:214 waiting for: waiting2ramp
-> RunID for this run is : 26
-> Output directory for this run is : /opt/SPECjAppServer2004/output/26
-> loadFactor=25
-> changeRate=30
-> burstyCurve from run.properties=7,14,13,17,26,15,0,11,27,19,37,21,34,28,40,35,31,21,45,8,6,8,10,14,28,25,24,18,8,10
-> scaleFactor=1.0
-> Curve avg txRate = 20.0
-> maxTxRate=45
-> tileNumber=0
-> Will run in bursty mode after rampup/warmup phases. Starting at burstPoint:0
-> WarmUp style = 0 (0=linear only, 1=burstycurve, 2=zigzag)
-> Phase one of warm up (start of transaction activity) will increase IR from 0 to 20 linearly, over 900 seconds.
-> Steady-State IR transition stepRate(ms)=40000
-> Burst Curve StartPoint Tile Multiplier=7
-> smoothFactor=1
-> Using default timeSkewTolerance value: 3
-> Exception encountered in auditor.validateInitialValues(). Aborting.
-> java.lang.ArrayIndexOutOfBoundsException: 1
^C2013-10-25 18:45:10:600 Done killing procs ...