OHS12c: Unable to Use Weblogic.StartScriptName and Weblogic.StartScriptEnabled to Start OHS Post Node Manager Startup
(Doc ID 2231548.1)
Last updated on AUGUST 24, 2023
Applies to:
Oracle HTTP Server - Version 12.2.1.2.0 to 12.2.1.2.0 [Release 12c]Information in this document applies to any platform.
Symptoms
When trying to call a script that will start the OHS after nodemanager has been started, by setting weblogic.StartScriptName and weblogic.StartScriptEnabled the script fails to run and OHS is not started.
From the stdout of nodemanager startup it seems the parameters weblogic.StartScriptName and weblogic.StartScriptEnabled are not being set.
It is expected that the OHS component would be started from the call to the scripts and that the output of the nodemanger would show the parameters.
The issue can be reproduced at will with the following steps:
1. Create a startup script for OHS. In this example it is named startOHS.sh.
2. Set the weblogic.StartScriptName = startOHS.sh and weblogic.StartScriptEnabled = true in the nodemanager.properties.
3. Start nodemanager.
4. Verify OHS did not start and the stdout does not show the parameters being set.
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 |
| Cause |
| Solution |