runspecvirt.sh not progressing

[lroderic]

Tom, this isn't my area of expertise, though we have others on the team looking into it. Another user was able to get this working and documented what he did in https://www.spec.org/forums/index.php?topic=54.msg319#msg319. Would you please check that out and see if we missed something that should be in the Technical Support FAQ? Thanks.

[tdeneau]

I tried everything I can think of including changing the Protocol in /opt/SPECvirt/Testbed.config and /opt/SPECweb2005/Test.config to be "TLS_RSA_WITH_AES_128_CBC_SHA"

Still getting the "no appropriate protocol" errors.  Not sure how to debug this further...


On the plus side, when I switch back to a single workload, with the workload being the appserver (instead of the webserver), I think it is running fine (although I am not quite sure how to confirm this)

Here is the output in client_1091.log after about 5 minutes:

2016-12-08 14:01:57:408 Creating jappclient using RMI Registry port 1091
2016-12-08 14:01:57:432 client1:1091 ready...
Driver Host: client1      Tile Number:0
2016-12-08 14:02:50:776 matchOut() messages set ...
2016-12-08 14:02:50:776 Starting rmiregistry; bindWait = 45000
2016-12-08 14:03:35:776 Starting Controller; bindWait = 45000
2016-12-08 14:03:35:783 waiting for: Binding controller to /
rec'd notifyInterrupt(101) call
Binding controller to //client1:2098/Controller
Launcher: done in waitMatch(0)
2016-12-08 14:04:20:905 Starting Agents
---------------//client1: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)...
2016-12-08 14:05:05:960 waiting for: waiting2ramp
RunID for this run is : 1
Output directory for this run is : /opt/SPECjAppServer2004/output/1
loadFactor=5
changeRate=30
burstyCurve from run.properties=37,72,61,87,132,77,0,49,137,93,187,103,174,138,200,173,153,107,225,44,36,44,48,68,138,125,116,88,38,50
scaleFactor=1.0
Curve avg txRate = 100.0
maxTxRate=225
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 100 linearly, over 900 seconds.
Steady-State IR transition stepRate(ms)=40000
Burst Curve StartPoint Tile Multiplier=7
smoothFactor=1
Using default timeSkewTolerance value: 3
Dec 08, 2016 2:05:06 PM com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
Dec 08, 2016 2:05:06 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: list ==> specdelivery:3700
Dec 08, 2016 2:05:06 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: corbaloc url ==> iiop:1.2@specdelivery:3700
Initial Audit
For txRate(100), loadFactor(5), and load_scale_factor(1.0), your DBIR must be built for 500IR
finished validateInitialValues()
Dealer Threads Per Agent=2250
Mfg Threads Per Agent=675
TTF1 = 2333
ttf = 2333
rec'd notifyInterrupt(101) call
waiting2ramp
Waiting for trigger signal from SPECvirt...
Launcher: done in waitMatch(0)
2016-12-08 14:05:13:365 jappScript.runDriver() completed successfully.
2016-12-08 14:05:13:367 Looking up polling host: specdelivery:8001
Waiting for steady state signal...
2016-12-08 14:05:14:400 waiting for: Starting Steady State
Configuring 1 DealerAgent(s)...
Configuring 1 MfgAgent(s)...
Dec 08, 2016 2:05:50 PM com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
Dec 08, 2016 2:05:50 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: list ==> specdelivery:3700
Dec 08, 2016 2:05:50 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: corbaloc url ==> iiop:1.2@specdelivery:3700
Configuring 2 LargeOLAgent(s)...
woRatePerAgent for LO: 59.99988000024
Dec 08, 2016 2:06:03 PM com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
Dec 08, 2016 2:06:03 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: list ==> specdelivery:3700
Dec 08, 2016 2:06:03 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: corbaloc url ==> iiop:1.2@specdelivery:3700
Dec 08, 2016 2:06:06 PM com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
Dec 08, 2016 2:06:06 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: list ==> specdelivery:3700
Dec 08, 2016 2:06:06 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: corbaloc url ==> iiop:1.2@specdelivery:3700

Warmup      = Thu Dec 08 14:10:14 CST 2016
SteadyState = Thu Dec 08 14:25:14 CST 2016
Rampdown    = Thu Dec 08 16:25:14 CST 2016
Finish      = Thu Dec 08 16:25:14 CST 2016

sleeptime is 246135 note this is time in excess needed for trigger
2016-12-08 14:10:14:401: Starting 900-second Warm-up...
2016-12-08 14:10:14:402: starting RTStats thread
2016-12-08 14:10:14:405: done starting RTStats thread
2016-12-08 14:10:14:425 Starting warmup phase for SPECjAppServer2004 using IR=100
2016-12-08 14:10:14:428 Starting linear warmUp phase for 900000ms.

[lroderic]

What version of Java are you using?

On the other hand, appserver is starting successfully. You should start to see response times in primectrl.out.

[tdeneau]

 java -version
java version "1.7.0_121"
OpenJDK Runtime Environment (rhel-2.6.8.1.el6_8-x86_64 u121-b00)
OpenJDK 64-Bit Server VM (build 24.121-b00, mixed mode)


Yes, I see response times in primectrl.out when the workload is appserver.

-- Tom

[tdeneau]

Question about the appserver Example VM.

If I reboot it, what starts the appserver daemon processes?  Do I have to run setup_files.sh every time the app-server is booted?

-- Tom

[lroderic]

jAppInit.sh and jAppInitRstr.sh contain the commands to stop and start GlassFish and Postgres. All the optdir scripts are for one-time use during set up.

You also might consider putting the SPECpoll start line in /etc/rc.local to make sure it starts on boot.

Lisa

[tdeneau]

OK, thanks.
It might be good to add all the appserver startup commands to /etc/rc.d/rc.local as well.

[tdeneau]

What is the recommended way to set up Control.config for one workload but something other than the appserver?  I have been going thru and interchanging indexes 0 and 1 (for webserver) or 0 and 2 (for mailserver) but is there a cleaner way?

-- Tom

[lroderic]

You're doing it the easiest way I think. You're probably already finished by now. I put the parameters I change a lot at the top:

NUM_TILES = 1
#NUM_TILES = 5
NUM_WORKLOADS = 4
#NUM_WORKLOADS = 1

#WARMUP_SECONDS= 900
WARMUP_SECONDS= 300
#POLL_INTERVAL_SEC = 7200
POLL_INTERVAL_SEC = 1200

I pre-fill the prime client (PRIME_HOST) and workload client (WORKLOAD_CLIENTS) entries with ten or more tiles so I only have to do this once. Then I create a copy of Control.config and save it with a suffix indicating what the first workload is (Control.config-web where web = 0 and app = 1 and so on). And I save those suckers to Dropbox or somewhere away from my testbed so I never have to do that again.

Lisa

[ChrisFloyd]

Lisa --

Following the directions in https://www.spec.org/virt_sc2013/docs/SPECvirt_TechnicalSupport.html#Webserver
have made those changes on just the webserver, do they need to be made anywhere else?

Also after making the changes, what do I have to restart if anything on the webserver or infraserver?

-- Tom

Tom,

Sorry I didn't catch this earlier. The changes to the java security settings need to be applied on the client machine (only), not the webserver VM.  Some webserver implementations may need to have SSL explicitly permitted (on the web VM), however if you are following the Example VM guide and using Apache, you shouldn't have to change anything on the web VM.

[andchri]

Hi Tom,

The changes need to be made to java.security on your client rather than webserver.
The client for the webserver workload is a java app.

regards,

Andrew