The runner fails to receive JVM properties from the worker

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download and compile caliper, example, tutorial folders
2. Try to run Benchmark1 with: scripts/caliper tutorial.Tutorial.Benchmark1
3. Few seconds after start the experiment raises an issue 
"java.lang.IllegalStateException: Optional.get() cannot be called on an absent 
value"

What is the expected output? What do you see instead?
Launch the Benchmark1 without problems

What version of the product are you using? On what operating system?
commit 48b1f239a98604b13731e0b635b24edbe5be6ab0 

Environment:
Distributor ID: Ubuntu
Description:    Ubuntu 12.10
Release:    12.10
Codename:   quantal
Java(TM) SE Runtime Environment (build 1.7.0_09-b05)

Original issue reported on code.google.com by jbotnasc...@gmail.com on 12 Feb 2013 at 1:52

[GoogleCodeExporter]

Patch

Original comment by jbotnasc...@gmail.com on 12 Feb 2013 at 2:02

Attachments:

• patchIssue219.patch

[GoogleCodeExporter]

That throws an ISE on purpose.  If the properties haven't been received from 
the worker, something has gone seriously wrong.  If you run with --verbose, is 
there anything in the output that might indicate why it has failed?

Original comment by gak@google.com on 12 Feb 2013 at 10:45

• Changed title: The runner fails to receive JVM properties from the worker

[GoogleCodeExporter]

No obvious errors or indication of problems at least, attached is full output 
running it with --verbose

Original comment by jbotnasc...@gmail.com on 13 Feb 2013 at 9:15

Attachments:

• log.output

[GoogleCodeExporter]

another log, now launching with java -verbose 

Original comment by jbotnasc...@gmail.com on 13 Feb 2013 at 9:22

Attachments:

• outputJavaVerbose.output

[GoogleCodeExporter]

The issue is on line 1098 of your first attachment.  Messages with the 
//ɹǝdıʃɐↃ// prefix are control messages.  They're supposed to be 
interpreted as such, but for some reason, the one for your jvm properties keeps 
failing that test.  Unfortunately, I have absolutely no idea why this would be 
happening on your particular machine for _just_ that message. I'll see if I can 
get a test case running with that string to figure out what's going on.

Original comment by gak@google.com on 13 Feb 2013 at 7:21

[GoogleCodeExporter]

A quick JUnit test with that string shows that the prefix test and the parsing 
are both working fine.  Maybe it's the Guice bindings?

Original comment by gak@google.com on 13 Feb 2013 at 7:53

• Changed state: Accepted
• Added labels: Milestone-1.0