Description of problem:
When invoking the start operation on an EAP 6 server, the operation fails when the connection setting Start Script Environment Variables is not set. This prevents the target start script from building the environment as normally expected (JAVA_HOME, PATH, etc) and requires the JBoss ON administrator to dynamically edit these values depending on the target script. 

Furthermore, this results in RPM installed JBoss packages from being started without setting some dummy value for this setting.

Bottom line, there should be no requirement that any environment variables be defined. Environment variables are just that -- environment -- and can be set by the execution environment invoked by the target start script.

Version-Release number of selected component (if applicable):
4.4.0.JON312GA

How reproducible:
Always

Steps to Reproduce:
#.  Start EAP 6 standalone server.
#.  Start JBoss ON 3.1.2 system.
#.  Import EAP 6 resources into inventory.
#.  Configure EAP 6 connection settings.
#.  Verify EAP server is reported as available.
#.  Unset _Start Script Environment Variables_ for EAP 6 server resource.
#.  Invoke the _Shutdown_ operation for the EAP 6 server resource.
#.  Invoke the _Start_ operation for the EAP 6 server resource.

Actual results:
Operation fails with the error message:
    java.lang.Exception: This Resource's connection properties contain errors: [No start script environment variables are set. At a minimum, PATH should be set (on UNIX, it should contain at least /bin and /usr/bin). It is recommended that JAVA_HOME also be set, otherwise the PATH will be used to find java.]
        at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:636)

Expected results:
Operation should succeed.

Additional info:
This appears to be due to some strange check on whether there is a value assigned to this connection property. I am not sure why it seemed necessary to perform such a check:

  1. the property value is optional
  2. the environment should only be used in default cases or when overrides are being sent to the script