Derby Server is Always Launched When WebLogic AdminServer Is Started
(Doc ID 1986892.1)
Last updated on AUGUST 15, 2022
Applies to:
Oracle Fusion Middleware - Version 12.1.3.0.0 to 12.1.3.0.0 [Release 12c]Information in this document applies to any platform.
Symptoms
After successfully installing an Infrastructure 12c version 12.1.3 on Windows 7 with Java 7, a base domain is created using the ORACLE_HOME/oracle_common/common/bin/config.cmd script. When starting the AdminServer using DOMAIN_HOME\startWebLogic.cmd, the AdminServer is being started on the current cmd line screen but a second cmd screen is started and it shows:
Derby Server for WLS Examples Server
Fri Dec 26 13:45:51 EST 2014 : Security manager installed using the Basic server security policy
Fri Dec 26 13:45:51 EST 2014 : Apache Derby Network Server - <IP> - (...) Started and ready to accept connections on port 1527
The only FMW 12c component that ask for the installation of the examples is the infrastructure. The Derby Server is being started with the AdminServer even if the examples were not installed. So, the infrastructure installation always install Derby Server, with or without the examples.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |