|
|
Known Issues
When
the remote host/device is down or its IP address is unresolved the login
times out after a long time independent of the login timeout value set
using selfLogingTimeout()
on the TelnetProtocolOptions instance passed to session open().
In Windows 2000 and Windows NT, when the CLI Browser 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.
When closing Telnet Application using exit menu item, the Telnet Window UI and connection gets closed but the application does not exit completely.
Issues Related to JDK 1.3 in RedHat Linux
When you 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 RedHatlinux7.1 and 7.2 GUI is not proper with jdk1.3.1 and lower versions.
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 the 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"; |
Limitations
In CLI Browser, there can be only one Data Set file associated with a Command Set file at a time.
|
|