Re: Understanding components in Airavata

Managed to fix this by adding job manager commands in client code ResourceJobManager resourceJobManager = RegisterSampleApplicationsUtils. createResourceJobManager(ResourceJobManagerType.FORK, null, null, null); resourceJobManager.setJobManagerBinPath("/bin/"); Map

Re: Understanding components in Airavata

Hi Suresh, I'm getting following error when launching the experiment [ERROR] Thread Thread[pool-41-thread-13,5,main] died java.lang.NullPointerException: null at org.apache.airavata.gfac.impl.job.ForkJobConfiguration.getSubmitCommand(ForkJobConfiguration.java:85) at

Re: Understanding components in Airavata

Hi Dimuthu, Since Airavata supports different type of computational resources from simple local executions to batch systems to cloud, the Resource Job Manager specifies the types of job submissions executed on a given resource, the protocol used and so forth [2]. The job manager commands are