KBI 311417 Issue Addressed Argent for Java Failed To Monitor Multiple JVMs On A Single Unix/Linux Server


Argent Advanced Technology 3.1A-1601-T10 and earlier


Friday, 17 June 2016


An issue has been addressed in Argent for Java that it failed to connect to a Unix/Linux machine where multiple JVMs are running with an exception

“java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ConfigurationException [Root exception is java.rmi.UnknownHostException: Unknown host: TEST_JVM_1; nested exception is: java.net.UnknownHostException”

Technical Background

There are situations to monitor multiple JVMs that are running under a single Unix/Linux machine using Argent for Java

As per the design, Argent for Java requires separate licensing for each JVM which in turn requires unique names for all JVM

Even though this unique name identify each JVM, it requires to be filled the ‘Alternative IP’ field in the licensed Node property screen shown below for establishing the connectivity

In the earlier versions, the connectivity failed because, internally, Argent for Java always used the Node Name attribute for connecting to the Unix/Linux machine

The issue has been addressed by using the Alternative IP, if it is present, instead of Node Name for connectivity

If Alternative IP is not specified, it will use the Node Name for connectivity


Upgrade to Argent Advanced Technology 1601-T11 or later