HTTP request failed. Error code: "503". Service Unavailable in RWB and Cache Refresh

[Former Member]

Dear Experts,,

We have MDM and PI in our landscape. We are using MDM Adapter for the integration between the two.

When we try to run the T Code SXMB_IFR, we are getting HTTP request failed error. i.e., “Error Code: 503 -- Service Unavailable”. And also the RWB communication channel is not working because of this error and we are unable to refresh the cache too because of this error.

We have checked from MDM side, and messages are flowing from ready folder but not coming into PI. We had monitored the messages using
SXMB_MONI.

We have restarted the Java Server but it’s taking too much time to restart around 12 to 15 hours & we checked after that but still facing the same issue.

Could you please help me to figure out this issue.

Thank you for your support in advance.

Thanks and Regards,

Priti.

[Former Member · Accepted solution]

Hi All,

I am glad to tell you that issue got resolved .There was issue with Database.

Some of database tables were corrupted so getting the mentioned error i.e503 -Service Unavailable.

There was an storage crash happened and due to which some of DB table were not available then they fixed this DB issue after that table is back to online now and accessible.

After getting confirmation from DB team we did a clean restart of the application; this would also need a Database stop-start.

After database restart we had done the application restart and checked the all PI functionality and issue got resolved ….

Thanks and Regards,

Priti.

[nabendu_sen]

Hi Priti,

Please check SAP Note: 803145 - Received HTTP response code 503.

Also SAP Note: 1779237 - MessagingSystem/receive/AFW/XI is temporary unavailable

Regards,

Nabendu.

[Former Member]

Hi Nabendu,

Our Basis team have already tried to implement note 1779237 but they didn’t find AF messaging service.As mentioned in note 803145, much of the threads are free in our case. Thread overloading could not be issue.

Thank you for your response.

Regards,

Priti.

[nabendu_sen]

Hi Priti,

You can check the suggestion of

Because of J2EE application com.sap.aii.af.ms.app not active

         The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.

Regards,

Nabendu.

[Former Member]

Hi Nabendu,

We have checked some of Java Application Services are stopped and we tried to start them manually but we are not able to start them please find attached screenshot for same.

Thanks and Regards,

Priti.

[naveen_chichili]

Hi Priti,

Check if all the Java services are up and running?

Thanks,

Naveen

[Former Member]

Hi All,

Thank you for your quick response.

We have checked that PI memory is not overload and we didn’t find any exception in st22  transaction code in PI and while restarting java server basis team found logs like MDM adapter listener could not start due to: Lookup of listener resources failed and port not found error.

We have checked in RWB in communication channel from receiver side as we are using JMS adapter at receiver end getting JMS Application is stopped. Channel deactivated error but not able to start the channels because of some xi related services are down but we are not able to up.

Thanks,

Priti.

[naveen_chichili]

Hi Priti,

>>some xi related services are down but we are not able to up.?

Are you able to provide any traces why the services are mot coming up

Regards,

Naveen

[Former Member]

Hi Naveen,

PFA for the application trace for more details.

Thanks and Regards,

Priti.

application_trc.txt.zip

[iaki_vila]

Hi Pitri,

Are you sure the endpoints are available when you find the error?

Have you checked the PI memory is not overload or the filesystem has not full in any directory?

Have you find any exception in st22 transaction in PI?

Regards.

[former_member184720]

503 typically means that service is unavailable.

Make sure that you java stack is up and running fine. i.e. you should be able to access sxmb_ifr/channel monitoring/rwb pages without any issues.

>>> We have restarted the Java Server but it’s taking too much time to restart around 12 to 15 hours & we

It should not take that long. Your basis team can analyze the logs and see if they can find some clue there.

If possible try to stop all the communication channels(sender) before restarting the system.