- (sc1-a) Make sure the IntegratedWebLogicServer is down (process exited).
- (sc1-b) Run a page in a web application (like an ADF Faces JSF JSP page), which will start the IntegratedWebLogicServer and will deploy the web application.
- (sc1-c) Open a browser and request http://localhost:7101/console (no need to authenticate) which causes the "IntegratedWebLogicServer - Log" panel in JDeveloper to show:

questions:
- (q1) How can this error message in the WebLogic Server log be explained, what does it mean?
- (q2) Has this behaviour or error message been documented? Where?
- (q3) Are there other scenario's causing the same "ServletContainerAdapter manager not initialized correctly" error message?

this has been filed as a bug and closed because it appears to be the correct behavior

ServletContainerAdapter manager not initialized correctly." is an expected condition, one that we handle within the console through the use of theconsole log4j configuration that we include within the console:

If someone overrides these by somehow overriding the console's log4j configuration, then this message can show

The fix thus is to ensure to include the following property in the log4j.properties of the console application
+(WL_HOME\server\lib\consoleapp\consolehelp\WEB-INF\classes\log4j.properties)+log4j.logger.org.apache.beehive.netui.pageflow.internal.AdapterManager = FATAL

The fix thus is to ensure to include the following property in the log4j.properties of the console application
(WL_HOME\server\lib\consoleapp\consolehelp\WEB-INF\classes\log4j.properties)
log4j.logger.org.apache.beehive.netui.pageflow.internal.AdapterManager = FATAL

I have checked ...
D:\oracle\jdevstudio111130-mw\wlserver_10.3\server\lib\consoleapp\consolehelp\WEB-INF\classes\log4j.properties
... on my machine and with some colleagues, and that log4j.properties file always has ...

Searching http://support.oracle.com for "7585620" results in a bug from 2005 with the strange title "(04) V04257W" and as "Product Source" has "JD Edwards".
So, are you sure that is the correct bug number? What would be the reason for the bug to be "not published"?