com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 503 (Service Unavailable)

[Former Member]

Hi,

We have PI 7.4 system which is only JAVA, I had restarted the system and now as we checked in JCMON system is stuck at Starting Apps.

While checking the default trace we found below errors.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

#2.#2016 02 17 17:20:36:439#+0300#Error#com.sap.aii.utilxi.sld.XIEntityInSld#

#BC-XI-IBD#com.sap.xi.util.misc#C000AC1028480075000000010000290B#555932850000007374##com.sap.aii.utilxi.sld.XIEntityInSld#Guest#0##2B3C6C14D57A11E5AA35000C299C188C#2b3c6c14d57a11e5aa35000c299c188c##0#SAP_AFScheduler.Worker#Plain##

Exception while pinging the SLD

Thrown:

com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 503 (Service Unavailable)

        at com.sap.lcr.api.cimclient.HttpRequestSender.newClientException(HttpRequestSender.java:719)

        at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:608)

        at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:352)

        at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:205)

        at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:153)

        at com.sap.lcr.api.cimclient.CIMOMClient.getCIMClass(CIMOMClient.java:552)

        at com.sap.lcr.api.cimclient.CIMClient.getCIMClass(CIMClient.java:1195)

        at com.sap.lcr.api.cimclient.CIMClient.getCIMClass(CIMClient.java:1206)

        at com.sap.lcr.api.cimclient.CIMClient.ping(CIMClient.java:295)

        at com.sap.aii.utilxi.sld.CimClientProxy.pingCimClient(CimClientProxy.java:1897)

        at com.sap.aii.utilxi.sld.XIEntityInSld.isSldPingable(XIEntityInSld.java:744)

        at com.sap.aii.af.service.sld.SLDRegistrationJob.invoke(SLDRegistrationJob.java:238)

        at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:529)

        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

        at java.security.AccessController.doPrivileged(Native Method)

        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)

        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)

#

#2.#2016 02 17 17:20:36:439#+0300#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#

#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1028480075000000020000290B#555932850000007374##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##2B3C6C14D57A11E5AA35000C299C188C#2b3c6c14d57a11e5aa35000c299c188c##0#SAP_AFScheduler.Worker#Plain##

SLD Registration Job: No access to SLD. Waiting for next retry. Error: SldProxy.pingCimClient() did not succeed.#

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Regards,

Deepak

[Former Member · Accepted solution]

Guys thanks for your replies, this issue has been resolved.

Default trace was misleading us as this issue was not related to SLD, while checking the std_server.out we came across some memory issue, we reduced the heap memory in configtool and restarted the system, after restart system came up successfully.

Regards,

Deepak

[former_member182412]

Hi Deepak,

As per the error it is look like SLD is down, you need to check the start up logs for more details.

Startup and control framework logs:
Contain information about the startup process. You can check these files if errors or undesired behavior occur during the startup process. By default, the data from the last three restarts is kept.
The developer trace files and system output of all the executables belonging to an instance are located in the directory /usr/sap/<SAPSID>/<instance_name>/work, where <SAPSID> is the SAP system ID (for example, CE1) and <instance_name> is the instance name (for example, JC00 or SCS01).

Regards,

Praveen.

[Former Member]

The JAVA system itself was connected to its local SLD, If system is down means its SLD is also down.

[former_member186851]

Hello Deepak,

Check with basis team whether all the jobs/services are up after the restart.