cancel
Showing results for 
Search instead for 
Did you mean: 

java.util.StackOverflowError when trying to call web application

Former Member
0 Kudos

Hi all,

I've deployed an Enterprise Application (ear) with the Deploy Tool, everything worked fine. Then I redirected the console output of WAS to a file (The Application uses Log4J with COnsole Output). Unfortunately, now the web appliaction does not work anymore. I'm getting a <b>HTTP 404 Page not found error</b> with the following log:

#1.5#000D60AB3BBC005800000018000006C40003EBE8400D4897#1103807669687#com.sap.engine.services.servlets_jsp.client.RequestInfo#sap.com/Integrationkernel#com.sap.engine.services.servlets_jsp.client.RequestInfo#J2EE_GUEST#0##sapwas1_NK1_4878050#Guest#2beae42054dd11d9c60e000d60ab3bbc#SAPEngine_Application_Thread[impl:3]_21##0#0#Warning##Plain###<b>Processing an http request to servlet [jsp] finished with error. The error is: java.lang.StackOverflowError</b>#

#1.5#000D60AB3BBC00580000001A000006C40003EBE8400E64AD#1103807669765#com.sap.engine.services.servlets_jsp.client.RequestInfo#sap.com/Integrationkernel#com.sap.engine.services.servlets_jsp.client.RequestInfo#J2EE_GUEST#0##sapwas1_NK1_4878050#Guest#2beae42054dd11d9c60e000d60ab3bbc#SAPEngine_Application_Thread[impl:3]_21##0#0#Warning##Plain###<b>Cannot send an http error response [500 Application error occurs during processing the request. (details: <pre>java.lang.StackOverflowError

</pre>)]. The error is: java.lang.StackOverflowError</b>

#

It seems that com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.doError and [...].sendError are calling each other.

So I used the "Installation Defaults" button in the Visual Admin Tool --> Log Configuration and re-assembled and redeployed my application exactly as I did it before. The Error still exists.

Does anybody has an idea of what could be the problem and how to resolve it?

Thanks a lot for any ideas and suggestions.

Nadine

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

problem solved. I restartet the cluster and redeployed the application under a different name - and it worked.

Nadine