Agile Shutdown Script Fails and Cannot Stop Agile Application Managed Server
(Doc ID 2448766.1)
Last updated on MAY 20, 2023
Applies to:
Oracle Agile PLM Framework - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
On 9.3.6.6 cannot stop Agile application server using the following script and parameter :
stopServerAgileManaged1.sh FORCE (superadmin password)
ERROR
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://xxx.xxx.xxx.xxx:9001 with userid superadmin ...
This Exception occurred at Mon Aug 06 07:34:05 UTC 2018.
javax.naming.AuthenticationException: User failed to be authenticated. [Root exception is java.lang.SecurityException: User failed to be authenticated.]
Problem invoking WLST - Traceback (innermost last):
File "/u02/app/agile/agile936/agileDomain/shutdown-ManagedServer1.py", line 3, in ?
File "", line 19, in connect
File "", line 553, in raiseWLSTException
WLSTException: Error occurred while performing connect : User failed to be authenticated.
Use dumpStack() to view the full stacktrace :
Done
Stopping Derby Server...
FACT
1) Reviewed
<Document 2307908.1> - Application Server Is Taking More Time to Shut Down Due to "FORCE" Parameter Is Removed In Stop Scripts
but could not find WebLogicConfig.properties and WebLogicKey.properties files on Agile application server installed machine.
root@xxx ~]# cd /
root@xxx /# find . -name *WebLogicConfig.properties -print
find: './proc/29750': No such file or directory
root@xxx /# find . -name *WebLogicKey.properties
root@xxx /#
root@xxx ~# cd /
root@xxx /# find . -name *WebLogicConfig.properties -print
root@xxx /# find . -name *WebLogicKey.properties
root@xxx /#
2) User can login with superadmin user on admin console with superadmin password
3) User can stop Managed Server via above admin console
a) Login to WebLogic Admin console with superadmin user with superadmin password
b) Go to agileDomain > Environment > Servers > Control tab
c) Click checkbox near XXXXX-ManagedY (X can be your host name and Y can be number of managed server) with State : RUNNING
d) Press Shutdown > Force shutdown now. Press Yes
e) After waiting for a while and refresh page, confirm Managed Server with State changed from RUNNING to SHUTDOWN
f) If you have confirmed managed server shutdown, try the same to other managed servers and finally perform on admin server.
STEPS
The issue can be reproduced at will with the following steps:
1. Login to Agile 9.3.6.6 application server installed server machine
2. Go to
<AGILE_HOME>/agileDomain/bin
3. Run the following command
stopServerAgileManaged1.sh FORCE (superadmin password)
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 |
References |