Without gateway preference setting for compute resources, experiment stuck in CREATED

When experiment is saved and launched prior to configuring the gateway preferences for the relevant compute resource in PGA experiment is in CREATED. No errors, messages or experiment FAILED.

But in api-orchestrator log already the experiment has failed with errors. it has errors [1]

This should be reflected in PGA, by either changing the status to FAILED or by notifying the user and gateway admin of the issue in hand and once the preferences are set it should get launched.

This way user doesn't have to create another one due to gateway admin level configuration issue.

[1]
2017-04-03 20:11:00 [pool-15-thread-6] INFO o.a.a.m.c.impl.ExperimentConsumer - Message Received with message id 'LAUNCH.EXP-2b62c33f-8fd5-486b-8f79-daafebc32b74' and with message type 'EXPERIMENT' for experimentId: Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273
2017-04-03 20:11:00 [pool-15-thread-6] INFO o.a.a.o.s.OrchestratorServerHandler - Launching experiment with experimentId: Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273 gateway Id: seagrid
2017-04-03 20:11:00 [pool-15-thread-6] ERROR o.a.a.o.s.OrchestratorServerHandler - Experiment launch failed due to Thrift conversion error, experimentId: Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273, gatewayId: seagrid
org.apache.thrift.TException: Experiment 'Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273' launch failed. Unable to figureout execution type for application Test_Lammps_7e68727f-b0ca-4895-81af-4527a9c1183d
at org.apache.airavata.orchestrator.server.OrchestratorServerHandler.launchExperiment(OrchestratorServerHandler.java:253)
at org.apache.airavata.orchestrator.server.OrchestratorServerHandler.launchExperiment(OrchestratorServerHandler.java:668)
at org.apache.airavata.orchestrator.server.OrchestratorServerHandler.access$500(OrchestratorServerHandler.java:78)
at org.apache.airavata.orchestrator.server.OrchestratorServerHandler$ExperimentHandler.onMessage(OrchestratorServerHan