503 Service Unvailable-The server connection 'AFW' is currently not started

[Marçal_Oliveras]

Hello,

I've get this error in my production PI 7.11 system (development is running ok).

The error is happening at SXI_MONITOR, for all the messages. All the messages from diferent interfaces reach PI without any problem, then the mapping is executed right, but finally, when the message must be sent to the Adapter Framework in order to deliver it to the target system, this is what happens:

503 Service Unavailable

The server connection 'AFW' is currently not started.

I've found these threads about the same problem, and they gave me some possible solutions to the issue but no one worked.

[http://forums.sdn.sap.com/thread.jspa?messageID=5430143]

[https://forums.sdn.sap.com/thread.jspa?threadID=38988]

[https://forums.sdn.sap.com/thread.jspa?threadID=818633]

[http://forums.sdn.sap.com/message.jspa?messageID=9229262]

OSS about similar problem 803145

But I'm totally sure of something, if I check this url http://xxx.xxx.xx:XXXXX/MessagingSystem/receive/AFW/XI I get the confirmation that this service is down, but I can't turn it up in NWA.

What else can can I do?

[former_member4985 · Accepted solution]

Hi Marshal,

Check if the J2EE Engine is not in "SAFE_DEPLOY" state. I should be in the normal operating mode. It could lead to some non-start of the applications. Normally this could happens from the deployment of the apps.

You also can have a look in the NWA. Under "Operation management" -> "systems" -> "start & stop" -> JAVA EE applications, you can see in the "application list" the status of the applications. All applications which are flagged as "always" (visible in "application details" -> tabstrip "details"-> field "startup mode") must run. Applications which have startup mode = "lazy" only start if the application is triggered.

Hope it helps even more.

Regards,

Caio Cagnani

[Former Member · Accepted solution]

I told my basis team to look into this, here is their reply

"I found that the system was running in safe mode.I made it to run in normal mode." //Basis team

Now it works as expected.

[oren_harlap]

Hello,

We had the same problem and were very disappointed that this thread did not provide the solution.

So after a while we managed to solve this problem ourselves. The problem was that in Config Tool the parameter for messaging.connections was shomehow deleted for one of the servers. That's why AFW was available on one application server and was not started on the other one.

Go to Config Tool -> Cluster Data -> template Usage_Type_All_In_One -> Instance xx -> services -> com.sap.aii.af.ms.svc.

Our problem was that the value for messaging.connectios parameter was missing (but the problem can arise from any other missing parameter). We clicked on 'Restore to inherited value' for this parameter so that it will inherit its value from the template. Once the parameter had a value we restarted this application server and the problem was sloved.

We have PI 7.11 SP8. The good thing about Config Tool in PI is that you can search the tool. We serached for 'AFW' and found an extra line that indicated where the problem was.

Hope this helps anyone.

Oren Harlap

[former_member4985]

Hello,

For the generic description, please see:

Error: The error message 503 Service unavailable Application stopped! is displayed.

Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

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

u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine

u2022 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.

u2022 Refer SAP Note 803145,807000,791655

Also, check if the J2EE is up and properly working.

Regards,

Caio Cagnani

[Marçal_Oliveras]

Thank you both,

I've already read those links and we are still having the same problem.

It looks that the PI server doesn't start automatically the some of the AF services. But then when I start them manually the AFW is still down and giving me that error.

We are waiting for SAP help because we need a fast solution. When we know the solution I will post it here.

[Former Member]

Hiii,

Can you try to bring whole PI server down and restart it again?

Sometime it works as it clears of the memory of PI server.

Try it if it works.

Thanks,

Hetal

[Marçal_Oliveras]

Hello,

After a lot of time, the problem has been resolved by the basis team... The basis team isn't from the same company as me, and they didn't want to tell me what was wrong.

All that I could get is, "There was a parameter wrong in production, that it was right in development". So all I can tell you is that they made a mistake during the installation... I've lost a lot of time because this error, but finally it's solved.

[sowmya_krishna]

Hi Marshal,

We are facing the same issue in PI7.11. From past 2 days we are working on it but not able to resolve.

You told its a BASIS problem. plz help how did u resolve?

[rajasekhar_reddy14]

Hi Sowmya,

The service connection AFW is currently not started means..there is a problem while starting the server.

as a developer you can't solve this problem.better to intiamte this prob to your basis team.

Regards,

Raj

[Marçal_Oliveras]

FYI:

-I've checked the IE URL and it's working fine (the SLD Business system data is OK too): [http://XXX.XX.XX.XX:xxxx/sap/xi/engine?type=entry]

-I've tried turned on the sevices at NWA

-I've executed the report RSXMB_ACTIVATE_ICF_SERVICES

-No users are blocked

The last thread I linked is not related to this issue, sorry. I can't edit the 1st message anymore.

EDIT: If I check the services at NWA, some of the af.XXX are not started. I started them manually, but the error is still there.

Edited by: Marshal on Jun 28, 2010 11:42 AM

[Former Member]

Hi Marshal,

503 Error comes due to server overload/server busy. So after some time again check. Still it is not working check this links and follow the steps mentioned.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4061 (Check 503 error)

Regards

Ramesh