WLS Console NOT Using The Current Context-Root Of A Web Module Inside A EAR
Last updated on DECEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 10.3.5 to 10.3.6
Information in this document applies to any platform.
When one targets a web application, shipped inside an EAR, to a Virtual Host, and the EAR has an associated deployment plan, then, on restart of the server, an exception is logged.
If this happens on a managed server, the server can never be rebooted in another state than the ADMIN mode
The user wanted for instance to use BI (example of a packaged application on top of WLS) in the following way:
- changing the default context root from /analytics to /bi
- associating the "analytics" web application inside the "analytics" EAR to virtual hosts.
- being able to restart the configuration.
This currently fails.
This is specially bad on a managed server, which cannot be brought up to life again until the config.xml is hand-corrected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms