Project: springxd
Issue XD-1352: Job Launch should throw exception if the job is not deployed in the container
While processing the "Job Launch" request, the ModuleDeployer checks if the job is already deployed, if not it deploys the job before launching it. This approach causes issue in case of multiple containers environment where the job is deployed in one container(1) but the "job launch" request is picked up by other container(2). Because the container(2) that processes "job launch" request deploys the job again, it conflicts with an existing job that is deployed in conatiner(1) with the same name in the JobRepository. Initially, the idea behind 'deploy before launch' was to enable launch shell command to also deploy. Because of the issue mentioned above, it is ok to assume that job launch needs to be performed on an existing deployed job.
Story points: 1