problem facing while pushing code

hi i am using following code snippet to push my code to Cf.

try {   
  File artefactFile=new File("D:/PROVIDER COCKPIT/DEPLOYING JARS/SpringBootRestApp-0.0.1-SNAPSHOT.jar");
  File metaDataFile=new File("D:/PROVIDER COCKPIT/DEPLOYING JARS/sample.yml");
  YamlConfigDetails ymlBean = new YamlConfigDetails();
  Map<String, Object> yamlConfigDetails = ymlBean.getYamlConfigDetails(metaDataFile);
  @SuppressWarnings("unchecked")
  LinkedHashMap<String, Object> apps = (LinkedHashMap<String, Object>) yamlConfigDetails.get("applications");
  Integer memory = Integer.parseInt(apps.get("memory").toString());
  Integer instances = Integer.parseInt(apps.get("instances").toString());
  String buildpack = (String) apps.get("buildpack");
  String command = null;
  String domain = (String) apps.get("domain");
  String appName = 12345 + "_" + 12345+ "_" + 0.1;
  try {
    LOGGER.info("creating application starting:---");
    Mono<Void> push = defaultCloudFoundryOperations.applications()
        .push(PushApplicationRequest.builder().
        name(appName).
        path(artefactFile.toPath()).
        memory(memory).
        command(command).
        domain(domain).
        buildpack(buildpack).
        instances(instances).
        randomRoute(true).
        noRoute(false).
        noStart(false).
        build());
    LOGGER.info("creating application completed:---");
    push.doOnSuccess(x -> System.out.println("deployed succesfully !!")).subscribe();
    push.doOnError(x -> System.out.println("deployment failed !!")).subscribe();
    LOGGER.info("pushing application completed:---");
  } catch (Exception e) {
    LOGGER.error(e.getMessage());
  }
} catch (Exception e1) {
  LOGGER.error(e1.getMessage());
}

i am using this service in my controller. when i invoke that endpoint. it is JUST creating application in CF.

but there is no route binded to application & application is always in stop condititon.

[nebhale]

Looking over your code there are a couple of areas for improvement that will push your application properly.

1. There is no need for you to parse your manifest directly. The project provides both the tools and the APIs for using a reference to a manifest directly.

2. .subscribe()-ing twice to a reactive flow causes the flow to be triggered twice. Therefore, in your code, you’re telling the application to push twice in close succession leading to one (but which one is undefined) to fail.

3. The entire API is asynchronous and non-blocking. Therefore, once you’ve subscribed to your flow, control is returned to the calling method which promptly completes, before even the first response (push is an orchestration of ~13 network requests) has returned. Therefore, your application has completed before the flow has completed. Some environments like Servlet containers have a long enough lifecycle that even if your calling method returns, the execution can still complete before the container closes. If you are running your application in an environment where the method lifecycle is dictates the application lifecycle, you’ll need to ensure that your method is kept alive until the flow is complete.

An example of improving all of these issues would be as follows:

CountDownLatch latch = new CountDownLatch(1);

this.cloudFoundryOperations.applications()
    .pushManifest(PushApplicationManifestRequest.builder()
        .manifests(ApplicationManifestUtils.read(Paths.get("D:/PROVIDER COCKPIT/DEPLOYING JARS/sample.yml")))
        .build())
    .doOnSubscribe(s -> this.logger.info("Deployment Started"))
    .doOnError(t -> this.logger.error("Deployment Failed", t))
    .doOnSuccess(v -> this.logger.info("Deployment Successful"))
    .subscribe(System.out::println, t -> latch.countDown(), latch::countDown);

latch.await();

[parasuram-tanguturu]

@nebhale how to replace System.out::println with logger. in .subscribe(System.out::println, t -> latch.countDown(), latch::countDown);