My Oracle Support Banner

Start_Primavera.bat Cannot Connect to NodeManager When SSL Implemented On WebLogic (Doc ID 2614660.1)

Last updated on SEPTEMBER 09, 2020

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 18.8.9.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to run the startup script start_primavera.bat
the following error occurs.

ERROR
-----------------------
NMProcess: SEVERE: Fatal error in NodeManager server
NMProcess: java.io.IOException: Could not obtain exclusive lock with lockFile '<WEBLOGIC_HOME>\wlserver\..\user_projects\domains\PrimaveraP6EPPM\nodemanager\nodemanager.process.lck'. This most likely indicates another NodeManager process is already running in this NodeManaagerHome.
NMProcess: at weblogic.nodemanager.server.NMServer.getNMFileLock(NMServer.java:254)
NMProcess: at weblogic.nodemanager.server.NMServer.(NMServer.java:153)
NMProcess: at weblogic.nodemanager.server.NMServer.getInstance(NMServer.java:134)
NMProcess: at weblogic.nodemanager.server.NMServer.main(NMServer.java:589)
NMProcess: at weblogic.NodeManager.main(NodeManager.java:31)
NMProcess:
NMProcess: ( was unexpected at this time.
NMProcess: Stopped draining NMProcess
NMProcess: Stopped draining NMProcess
Connecting to Node Manager ...
PRM-Unable to connect to the Node Manager. It may not be running,
PRM-or communications may be blocked by a firewall.
PRM-Completed. Returned error level: 1

 

ACTUAL BEHAVIOR
-------------------------
Cannot start P6 EPPM using start_primavera.bat, but as a workaround can start WebLogic manually and managed servers in the WebLogic Administration Console

EXPECTED BEHAVIOR
-------------------------
The start_primavera.bat script should start the Nodemanager, admin server, and all managed servers

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run start_primavera.bat
2. See this error in weblogic command window

When running stop_primavera.bat, to stop the environment, get a different error:


This Exception occurred at Wed Nov 13 16:14:22 CST 2019.
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://<SERVERNAME>:<PORT_NO>: Destination 0:0:0:0:0:0:0:1, <PORT_NO>unreachable.; nested exception is:
  java.net.ConnectException: Connection refused: connect; No available router to destination.; nested exception is:
  java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: t3s://<SERVERNAME>:<PORT_NO>: Destination<IP_ADDRESS>, <PORT_NO> unreachable.; nested exception is:
  java.net.ConnectException: Connection refused: connect; No available router to destination.; nested exception is:
  java.rmi.ConnectException: No available router to destination.]
Problem invoking WLST - Traceback (innermost last):
  File "<P6_HOME>\scripts\stop_Primavera.py", line 4, in ?
  File "", line 19, in connect
  File "", line 553, in raiseWLSTException
WLSTException: Error occurred while performing connect : Cannot connect via t3s or https. If using demo certs, verify that the -Dweblogic.security.TrustKeyStore=DemoTrust system property is set. : Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://<SERVERNAME>:<PORT_NO>: Destination 0:0:0:0:0:0:0:1, 7002 unreachable.; nested exception is:
  java.net.ConnectException: Connection refused: connect; No available router to destination.; nested exception is:
  java.rmi.ConnectException: No available router to destination.
Use dumpStack() to view the full stacktrace :

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.