Known Issues and Limitations

 

The following are some of the known issues with this product at the time of release.

 

Please check the known issues page on the AdventNet web site, http://www.adventnet.com, for any updates to this list of known issues.

  1. SnmpSession.open has been known to hang with JIT in jdk1.1.7 on Windows systems and in jdk1.1.6 and 1.1.7 of Solaris. This is due to problem with the JIT. Either upgrade the JVM to a later release or please use older versions. This is because of the native threads problem in Solaris 2.5.1. Please take a look at the following URL from Sun Microsystems for more information.

  1. Even after killing rmipoller in rmiAppletDemo the polling thread in rmiserver is not cleaned up.

  2. CORBA examples cause a segmentation fault on the SNMP server side on Solaris 2.6 with JDK 1.2.

  3. While adding multiple clients to the SnmpSession, the debugPrint() method of all the clients are invoked with the debug messages. This causes irrelevant debug messages sent to other clients.

  4. In MibBrowser, BarGraph will not plot multiple values at a time.

  5. While using the EJB examples available in the ejbclient directory, the client applications must set the classpath to AdventNet EJB classes and AdventNetSnmp.jar before setting it to the Application Servers classes.

  6. The help icon in the MibBrowser bean will launch a web browser and try to load the help files from the installed directory of the package. If the MibBrowser bean is tested outside the package the help icon will not invoke the help files. Method setHelpURL() of the MibBrowser bean can be made use of for specifying the proper location.

  7. If the session used by the MibBrowser is used by some other bean, then the MibBrowser debug window will display PDU dumps of requests sent by other beans.

  8. Database support (for SNMPv3 user information) is not provided for async_create_v3_tables() in the high level API.

  9. In RMI, after receiving the TrapEvent instance if the client invokes the getTrapDefinition() method then the return value will always be null.

  10. Features like, database support for loading MIBs, storing v3 security parameters etc., are not available with the HTTPMibBrowser.

  11. RMI requests will be slow in Windows NT and Windows 2000 machines. This is because, the RMI Registry does a DNS lookup for the hostname specified. The work around for this problem is given in the FAQ section.

  12. There are some incompatibility issues in WebLogic 6.0 Application Server with respect to standard stubs and skeletons. The WebLogic 6.0 does not support the standard stub and skeleton classes i.e. it looks for weblogic specific stub and skeleton classes. The weblogic specific stub and skeleton classes have SomeClass_WLStub.class and SomeClass_WLSkel.class format. Therefore, if we run the startup class 'SnmpStarter' inside the WebLogic Server it may not succeed.

  13. When the same SnmpPDU is sent continuously say after changing some fields like remote host or remote port, the user has to take care of the requestID that needs to be set on the SnmpPDU. Otherwise, every request will be sent with the requestID generated first.

  14. In the case of applets, when the file name of the imported MIB is different from the module name, the MIB file could not be loaded.

JDK Issues

 

Policy files are one way of specifying permissions for RMI in the new security model. To do this, create a file containing the following.

 

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

 

For example, if you name this file as SnmpRmi.policy, then you have to run snmp_rmiserver as given below.

 

java -Djava.security.policy=SnmpRmi.policy com.adventnet.snmp.rmi.SnmpFactoryImpl

 

The other issue is related to applets. The appletviewer no longer takes the classpath setting into consideration. So, for some of the applets such as the requestServerDemo the command to be given is

 

appletviewer -J-Xbootclasspath:.;..\..\classes;

c:\jdk1.2\jre\lib\rt.jar requestServerDemo.html

 

Applets could instead be packaged into jar files for easy use in browsers. Also with JDK1.2 you can specify dependencies on other jars through extensions. Therefore, if you create an applet that uses AdventNet beans and the target platform is the JDK1.2-plugin, then just add a line including the CLASSPATH. The manifest for your

jar will look something like the following.

 

Manifest-Version: 1.0 Class-Path: AdventNetSnmp.jar

 

Limitations

  1. Currently, when an application sends an SNMPv1 PDU using a session whose version is set to SNMP_VERSION_3, an SNMPv3 message is sent to the peer. This problem arises because the API uses SNMP_VERSION_1 as the default PDU version and it could not distinguish between applications leaving the version in PDU to default and setting it explicitly to SNMP_VERSION_1. To circumvent this problem, applications should set session version to SNMP_VERSION_1 and set the PDU version explicitly to SNMP_VERSION_2C or SNMP_VERSION_3, while communicating with v2c and v3 peers.

  2. Currently, it is not possible to use SASClient.clientCall() method for doing asynchronous communication with SAServer.

  3. In the MibBrowser application, while querying for columnar OIDs through the multi-varbind option, the index also should be specified.

  4. Browse option provided in Load MIB dialog of the MibBrowser applet will not work for HTTP. Please enter the URL in the text field to load the MIB(s) from the server or from the jar file if available.

  5. Switching between TCP/IP and HTTP is not possible during runtime.

  6. Loading of MIB files from the signed jars is not supported.

 


Copyright © 1996-2006, AdventNet Inc. All Rights Reserved.