Webdynpro is stoppedd - error 503 service unavailable

[Former Member]

All,

After us installed the GRC (WeB AS Java+ Abap, add-on PI_Basis, SAP_BW, SAP_ABA, SAP_BASIS, SAP_AP, SLL-NFE), tried to access the Webdynpro and NWA by SAPJ2EE ENGINE START PAGE and shown us the following message:

Application stopped.

Details: You have requested an application that is currently stopped

I've ever checked some configurations on Visual Adm and Config Tools, and all parameters are Ok. On SAP MMC everything is green.

Could someone help me??

Thanks

Erik Brison

[Former Member]

Erik

Try to restart the entire SAP system.

Let it come up completely and try again.

If it does not help that means some of the deployed application could not start.

If nwa could not start, it is possible you have issue with sap.com/tc_lmwebadmin_mainframewd

If webdynpro tools cannot be accessed, there may be an issue with sap.com/tc_wdtools

Login to VisAdmin, go to Deploy, click on Application radio button and check the status of the apps.

Go to Log Viewer and analyze the reason why apps are not running. If J2EE engine fails to start an application, there will be an error in the Default trace.

Regards,

Slava

[Former Member]

Hi there,

We checked this ones but we haven't found any trouble with this two components - both are correctly deployed...

Any other idea?

Thanks

[Former Member]

Are they deployed or running?

What did Default trace tell you?

Run HTTP trace of your IE session and see what URL it tried to access before it failed?

Look for /webdynpro/dispatcher/<sap apps url>

<sap apps url> will tell you what apps are involved.

Regards,

Slava

[Former Member]

Hi Slava,

We looked for two default traces:

1 - C:\usr\sap\GD0\DVEBMGS74\j2ee\cluster\server0\log, the content was:

#1.5 #000C2935D5FC00720000008E00000E9C00045E3CBB685B10#1229514842127#System.err#sap.com/tc_{kw_tc#System.err#J2EE_GUEST#0##n/a##62372d70cc3111dd8219000c2935d5fc#SAPEngine_Application_Thread[impl:3]_22##0#0#Error##Plain###Dec 17, 2008 6:54:02 AM com.sap.kw.framework.XMLConfiguration [SAPEngine_Application_Thread[impl:3]_22] Path: Caught java.io.FileNotFoundException: C:
usr
sap
GD0
DVEBMGS74
j2ee
cluster
server0
apps
sap.com
tc}kw_tc
servlet_jsp
SAPIKS2
root
WEB-INF
ApplConfig.xml (The system cannot find the file specified)

at java.io.FileInputStream.open(Native Method)

at java.io.FileInputStream.<init>(FileInputStream.java:106)

at java.io.FileInputStream.<init>(FileInputStream.java:66)

at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)

at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)

at java.net.URL.openStream(URL.java:913)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)

at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)

at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:151)

at com.sap.kw.framework.XMLConfiguration.<init>(XMLConfiguration.java:49)

at com.sap.kw.actions.ApplConfig.init(ApplConfig.java:83)

at com.sap.kw.framework.FrontController.init(FrontController.java:222)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)

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

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

=====================================

2 - C:\usr\sap\GD0\DVEBMGS74\j2ee\cluster\dispatcher\log, the content was:

5 #000C2935D5FC0014000000030000171800045E3CB418E2D0#1229514719429#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#######SAPEngine_System_Thread[impl:6]_10##0#0#Warning#1#/System/Server#Java###JMX connector exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 316 | src: cluster target-node: 742010100 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=742010100,SAP_J2EECluster="" null null null ]

[EXCEPTION]

#1#com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to de-serialize request parameters, message [ JMX request (java) v1.0 len: 316 | src: cluster target-node: 742010100 req: invoke params-number: 4 params-bytes: 0 | :name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=742010100,SAP_J2EECluster="" null null null ]

at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:537)

at com.sap.engine.services.jmx.RequestMessage.getParams(RequestMessage.java:586)

at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:90)

at com.sap.engine.services.jmx.JmxServiceConnectorServer.receiveWait(JmxServiceConnectorServer.java:172)

at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:81)

at com.sap.engine.core.cluster.impl6.ms.MSListenerThread.run(MSListenerThread.java:47)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:80)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:150)

Caused by: javax.management.InstanceNotFoundException: MBean with name com.sap.default:name=com.sap.portal.prt.bridge.service.mbeans.PRTMBeanRuntime,j2eeType=PRTBridge_JMX_SECTION,SAP_J2EEClusterNode=742010100,SAP_J2EECluster=GD0 not found in repository

at com.sap.pj.jmx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1408)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getClassLoaderFor(MBeanServerWrapperInterceptor.java:455)

at com.sap.engine.services.jmx.CompletionInterceptor.getClassLoaderFor(CompletionInterceptor.java:576)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getClassLoaderFor(BasicMBeanServerInterceptor.java:438)

at com.sap.jmx.provider.ProviderInterceptor.getClassLoaderFor(ProviderInterceptor.java:330)

at com.sap.engine.services.jmx.RedirectInterceptor.getClassLoaderFor(RedirectInterceptor.java:501)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getClassLoaderFor(MBeanServerInterceptorChain.java:443)

at com.sap.engine.services.jmx.RequestMessage.readParams(RequestMessage.java:531)

... 8 more

======================================

Unfortunately we didn't used HTTP trace from IE because we don't know how to find it! But we tried to use SAP DiagTool to reproduce the error when using IE to access any web dynpro page. We found this log:

getLoggedInUser

[EXCEPTION]

com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)

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

at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)

at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)

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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)

at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)

at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)

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

at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)

at javax.security.auth.login.LoginContext.login(LoginContext.java:534)

at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.getLoggedInUser(SAPJ2EEAuthenticator.java:146)

at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:264)

at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doPost(SAPMLogonServlet.java:60)

at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doGet(SAPMLogonServlet.java:78)

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

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

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

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

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

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

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

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

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

===========================================

Regards,

Erik

[Former Member]

I forgot one detail to say... it's deployed but I don't know if it's running - neither how to run it...

How to run it?

Thnaks,