Search Engine: Elastic

Article ID: 131319, created on Aug 17, 2017, last review on Aug 17, 2017

  • Applies to:
  • APS 2.x

Symptoms

Task Provide backend for application Application name (instance #YYY) fails without any errors:

Method name
taskProvideApplicationInstanceBackend on SCREF:SaaSManagerTasks:0

The following exception is shown in core.log:

Aug 16 00:49:52.558 : DBG [task:66:973 p:-default-threadpool;-w:-Idle:352 pau]: c.p.p.tracer exit by exception: com.parallels.pa.service.endpoint.ejb.ApsEndpointManagerBean.provideApplicationBackendjava.lang.NullPointerException: null
    at com.parallels.pa.service.endpoint.ejb.ApsEndpointManagerBean.lambda$6(ApsEndpointManagerBean.java:373)
    at com.parallels.pa.service.endpoint.ejb.ApsEndpointManagerBean.call(ApsEndpointManagerBean.java:270)
    at com.parallels.pa.service.endpoint.ejb.ApsEndpointManagerBean.runContainer(ApsEndpointManagerBean.java:367)
    at com.parallels.pa.service.endpoint.ejb.ApsEndpointManagerBean.provideApplicationBackend(ApsEndpointManagerBean.java:359)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Cause

Docker image was not configured properly.

Resolution

Make sure that the parameters in deployment.xml file were set correctly:

<imageName>username/packagename</imageName>
<applicationPort>1443</applicationPort>
<applicationUrlPath>endpoint</applicationUrlPath>

If the values of applicationPort and applicationUrlPath were changed, make sure that they were also changed in related files inside the deploy-image folder.

70bf700e0cdb9d7211df2595ef7276ab 717db81efe94e616312b74fb03a5d474

Email subscription for changes to this article
Save as PDF