TIP: Upgrade issue when using WebSphere auto generated start_server1.sh to support autostart.
Note this is a tip and not a question.
Env: RHEL, WAS, IHS, Oracle
Summary:
We recently upgraded from 3.0.1.2 to 3.0.1.4. We got caught with hard coded environment values in an auto generated start_server1.sh file. Generated by startServer.sh -script ...
Symptoms:
We use start_server1.sh to support restart on server reboot. However the script contains hard coded JAZZ_HOME, et.al. JVM environment values. Even if you change the values in the WAS admin console, they are overridden by the command line values.
Solution:
Updated values in script for now, will see if we can strip out of script.
Env: RHEL, WAS, IHS, Oracle
Summary:
We recently upgraded from 3.0.1.2 to 3.0.1.4. We got caught with hard coded environment values in an auto generated start_server1.sh file. Generated by startServer.sh -script ...
Symptoms:
- JTS has problems chatting with CCM
-
logs with "failed to determine authentication method", even though the WAS plugin keys were fine.
-
log files say the version of the app is different than the version supported in the database (3.0.1.2 vs 3.0.1.4)
We use start_server1.sh to support restart on server reboot. However the script contains hard coded JAZZ_HOME, et.al. JVM environment values. Even if you change the values in the WAS admin console, they are overridden by the command line values.
Solution:
Updated values in script for now, will see if we can strip out of script.