stopServerAgileManaged Script Ends In java.net.MalformedURLException Error

(Doc ID 2420967.1)

Last updated on JULY 09, 2018

Applies to:

Oracle Agile PLM Framework - Version 9.3.6.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
When attempting to stop the managed server using stopServerAgileManaged script
the following error occurs and could not stop the managed server.

FACT
This is a fresh install for Linux OS platform.
Admin server is running. This can be confirmed from accessing the admin console.

ERROR

Connecting to t3://xxx.com: with userid superadmin ...
This Exception occurred at Wed Jul 04 03:55:54 CDT 2018.
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
port expected: t3://xxx.com: [Root exception is java.net.MalformedURLException: port expected: t3://xxx.com:]
Problem invoking WLST - Traceback (innermost last):
  File "/u01/app/agile/agile936/agileDomain/shutdown-YYYY-1.py", line 3, in ?
  File "", line 19, in connect
  File "", line 553, in raiseWLSTException
WLSTException: Error occurred while performing connect : Error getting the initial context. There is no server running at t3://xxx.com: : Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
port expected: t3://xxx.com:
Use dumpStack() to view the full stacktrace :



STEPS
The issue can be reproduced at will with the following steps:
1. Run the stopServerAgileManaged script located in <AGILE_HOME>/agileDomain/bin

Changes

 

Cause

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