CLIENT_SEND_FAILED - Error while sending by HTTP 503

[Former Member]

Hi Experts,
we have a problem when sender message to PI system (single stack). In the Tcode /nsxi_monitor display the following message;

<Trace type="T" level="1">HTTP-client: status code = 503</Trace>
<Trace type="System_Error" level="3">Error while sending by HTTP (error code: 503 , error text: Service Unavailable) </Trace>
</Trace>
</Trace>
<Trace type="System_Error" level="3">Error exception return from pipeline processing! </Trace>
-<Trace type="B" level="1" name="CL_XMS_LMS_EXTR_FILTER-GET_VALUES">
<Trace type="T" level="1">total processing time: 0.0000820 sec [0 filter(s)] </Trace>

This message used the RFC "PI_AEE" (type G) you can see this in SM59 (tcode)

Now, this is the message error in SXI_MONITOR

<Trace type="System_Error" level="3">Error while sending by HTTP (error code: 503 , error text: Service Unavailable) </Trace>

</Trace>

</Trace>

<Trace type="System_Error" level="3">Error exception return from pipeline processing! </Trace>

-<Trace type="B" level="1" name="CL_XMS_LMS_EXTR_FILTER-GET_VALUES">

<Trace type="T" level="1">total processing time: 0.0000570 sec [0 filter(s)] </Trace>

</Trace>

<Trace type="T" level="1">Failure because of too many retries!!! </Trace>

<Trace type="B" level="1" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_TO_PERSIST"/>

<!-- ************************************ -->

<Trace type="T" level="3">Persisting message Status = 018</Trace>

<Trace type="T" level="3">Message version 001</Trace>

<Trace type="T" level="3">Pipeline SENDER</Trace>

</SAP:Trace>

Please can you help me check this error?

Best Regards,
Basis Team.

[MarioDeFelipe]

Hello Basis

I see on your log that the error is while sending by HTTP (receiver scenario) but you say that this is Sender HTTP scenario

Can you tell some more info on where is the message being sent to? probably to ECC enviroment using proxies?

can you attach full trace?

thanks

[Former Member]

Hi Mario,

We attah file in this message. Thanks.

Best Regards,

BT

all_trace.txt.zip

[MarioDeFelipe]

Maybe its an stupid question, but can you try to see if user "administrator" in PI system 10.240.160.58 is not locked?

try to login with that user, to make sure it has correct password, and out of valid date

thanks

[Former Member]

Hi Mario,

Yes, the user administrator work fine.

Best Regards,

BT

[MarioDeFelipe]

do you see any related error in SMICM in PI system, or in SXMB_MONI in PI system?

regards

[former_member227283]

Hi,

Can you share what detail like Suffix has been defined in RFC ?

Regards,

Anil Bhandary

[avadhesh_sap]

Hi ,

Can you check transaction SMICM if http port registered

Thanks,

Avadhesh

[Former Member]

Hi Avadhesh,

yes, the port java is correct and the telnet is fine.

Best Regards,

Basis Team.

[Sriram2009]

Hi Basis,

Check this sap Note  1779237 - MessagingSystem/receive/AFW/XI is temporary unavailable

BR

SS

[former_member227283]

Hi,

Can you check the RFC PI_AEE is working with status code 200 or not.

Hope RFC is pointing to right system and working fine.

It might be the case you have multiple Server nodes on PI java node and one server node might have a issue.

Better restart complete PI java instance and try if it resolve the problem. Some cases restart help to solve the problem.

Regards,

Anil Bhandary

[Former Member]

Hi Anil, the test for RFC "PI_AEE" is fine. the test finish with status 200

The PI instance was restarted several times.

Best Regards,

BT

[former_member227283]

Hi,

Please share the PI java stack default trace file in which it has error specific to 503 code.

Regards,

Anil Bhandary