503 Service Unavailable Application cannot be started.

[Former Member]

Hello XI Gurus,

The XI adapter was working fine and all of the sudden it was stop working. We looked at the adapter monitoring and we saw an error message "503 Service Unavailable Application cannot be started."

We thought maybe if we bounced the server and everything will be back up and running. Unfortunately it did not. We are running XI 7.0

Below is errors log.

Details for 'Ping Status'

Message: HTTP request failed. Error code: "503". Error message: "Service Unavailable [http://usplselux179:51000/AdapterFramework/rtc]"

Stacktrace:

com.sap.aii.rwb.exceptions.RequestFailedException: HTTP request failed. Error code: "503". Error message: "Service Unavailable [http://usplselux179:51000/AdapterFramework/rtc]"

at com.sap.aii.rwb.exceptions.RequestFailedException.forHttpErrorCode(RequestFailedException.java:79)

at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.request(GrmgConnector.java:238)

at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.ping(GrmgConnector.java:69)

at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:216)

at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:580)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:307)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:381)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:397)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:348)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at jsp_FC_Secure1171559313688._jspService(jsp_FC_Secure1171559313688.java:24)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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:100)

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

Thanks so much for your help in advanced,

David

[Former Member]

Hi David,

we have the same problem , we r on XI 3.0 SP19,

pls help, tell me how u resolved the issue,

[agasthuri_doss]

Hi,

>>'java.lang.NullPointerException']--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Instantiating the Adapter Framework service () failed. Reason: .

at com.sap.aii.af.service.impl.ServiceFrameImpl.handleStartupFailure(ServiceFrameImpl.java:194)

at com.sap.aii.af.service.impl.ServiceFrameImpl.start(ServiceFrameImpl.java:106)

Hence restart the Java Stack if you still encounter the error try to re install the Java stack.

Regards

Agasthuri Doss

[agasthuri_doss]

Hi,

The server might not able 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.

Try this to resolve

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

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

3) 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

Agasthuri Doss

[Former Member]

Hello Agasthuri,

Thanks so much for a quick response. I will try to sovled this problem based on your suggestion. I will keep you posted.

Thanks again,

David

[Former Member]

Agasthuri,

We have attempted the steps that you suggested, but we still having the same issue. Error log below.

#1.5#00144F0ED0FA0069000000220000048600043484ADD584CE#1183644363621#com.sap.aii.af.service.impl.ServiceFrameImpl##com.sap.aii.af.service.impl.ServiceFrameImpl

.start(ApplicationServiceContext)####usplselux179_XS1_104027650#Guest#ccb0de902b0011dc887e00144f0ed0fa#SAPEngine_System_Thread[impl:5]_37##0#0#Fatal##Java###I

nstantiating the Adapter Framework service () failed. Reason: . Aborting AF Core service startup#3#Channel Scheduling#com.sap.aii.af.service.administration.impl.scheduling.SchedulingManagerImpl#java.lang.NullPointerException# #1.5#00144F0ED0FA0069000000230000048600043484ADD58712#1183644363622#com.sap.aii.af.service.impl.ServiceFrameImpl##com.sap.aii.af.service.impl.ServiceFrameImpl .start(ApplicationServiceContext)####usplselux179_XS1_104027650#Guest#ccb0de902b0011dc887e00144f0ed0fa#SAPEngine_System_Thread[impl:5]_37##0#0#Error##Plain### AF Core service startup failed. Rolling back already started AF services# #1.5#00144F0ED0FA0069000000250000048600043484ADD5EF84#1183644363648#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.con tainer.ServiceRunner####usplselux179_XS1_104027650#Guest#ccb0de902b0011dc887e00144f0ed0fa#SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/System/Server#Plain ###Service com.sap.aii.af.svc error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Instantiating the Adapter Framework service () failed. Reason: .', Arguments: ['Channel Scheduling', 'com.sap.aii.af.service.administration.impl.scheduling.SchedulingManagerImpl', 'java.lang.NullPointerException']--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Instantiating the Adapter Framework service () failed. Reason: .

at com.sap.aii.af.service.impl.ServiceFrameImpl.handleStartupFailure(ServiceFrameImpl.java:194)

at com.sap.aii.af.service.impl.ServiceFrameImpl.start(ServiceFrameImpl.java:106)

Regards,

David