NMS Java Client Not Downloading After "clear Cache" (or First Time Logging In)
(Doc ID 2612872.1)
Last updated on SEPTEMBER 16, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.2.0 and laterOracle Network Management for Utilities - DMS - Version 2.3.0.2.0 and later
Information in this document applies to any platform.
Symptoms
The NMS Java Client is not downloading after completing a "clear cache" in the users Java Control Panel. The same problem occurs on a PC for the first time logging in.
The symptom is that the Java Console Log does not get passed downloading the first .jar file:
Java Web Start 11.231.2.11
Using JRE version 1.8.0_231-b11 Java HotSpot(TM) 64-Bit Server VM
JRE expiration date: 2/17/20 12:00 AM
User home directory = C:\Users\%USER%
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
0-5: set trace level to
----------------------------------------------------
file: C:\Users\%USER%\AppData\Local\.nms\cache\_\<WEB SERVER>_<PORT>
CacheEntry[http://<WEB SERVER>:<PORT>/nms/nms-ide.jar]: updateAvailable=false,lastModified=Fri Nov 11 05:18:40 CDT 2019,length=1994500
If the client has already logged in with the current version of NMS, then there is no problem since it is just using the cached jar files. However, if they are logging in on a PC they have not logged in on before, the client hangs.
Expect that the client would download.
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 |