CLI Related

1. When the remote host/device is down or unreachable the login times out after a considerable time ( ~ 60 seconds ) based on underlying TCP connection timeout. This is independent of the Login timeout value set using setLoginTimeout() on the TelnetProtocolOptions instance passed to session open().

2. When closing Telnet Application using exit menu item, the Telnet Window UI and connection gets closed but the application does not exit which has to be separately terminated.

3. In Windows 2000 and Windows NT, when the CLIBrowser Application's help menu is invoked, the help files will not be displayed if the Netscape browser is already open. So if you have any web browser already opened while using the CLIBrowser application, please close that and invoke the help menu again.

JDK Related

1.Known issues related to JDK 1.3 in RedHat Linux

• When we do a session.close() in the application, the socket is not closed properly and the session is still alive. More information on this issue can be seen in the Java Developer Connection with the Bug ID : 4344135. http://developer.java.sun.com/developer/bugParade/bugs/4344135.html
• In RedHat Linux 7.1 and 7.2 GUI is not proper with jdk1.3.1 and lower versions.

2.RMI Related Issues

The RMI security manager does not allow socket connection. It does not allow reading of system properties. These access permissions are required for the functioning of WebNMS CLI API. One way of specifying these permissions is with policy files which is explained below.

Workaround

The java.policy file will be present under the jre/lib/security directory of the JDK installation. The file should have the following entries:

grant

permission java.net.SocketPermission"*:1024-65535","connect,accept";

permission java.net.SocketPermission "*:80","connect";

permission java.propertpermission "java.class.path", "read";