My Oracle Support Banner

When Starting Soa_Server1 Managed Server, The State is FAILED_NOT_RESTARTABLE (Doc ID 1442372.1)

Last updated on SEPTEMBER 23, 2019

Applies to:

Oracle Fusion Application Toolkit - Version and later
Information in this document applies to any platform.
Checked for relevance on 03-10-2013
Checked for relevance on 03-20-2015


When attempting to start soa_server1 managed service in the CRM Domain, the Weblogic Console showing the state as FAILED_NOT_RESTARTABLE

From the logs (soa_server1.out) , below errors are noticed:

<Mar 26, 2012 4:43:55 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Mar 26, 2012 4:43:55 AM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Mar 26, 2012 4:43:55 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Mar 26, 2012 4:43:55 AM> <FINEST> <NodeManager> <Waiting for the process to die: 27212>
<Mar 26, 2012 4:43:55 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Mar 26, 2012 4:43:55 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Caused by: Posted content doesn't set it's Content-Length
at weblogic.deploy.service.datatransferhandlers.MultipartParser.parseResponse(


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.