Known Issues and Limitations

• Known Issues

• Limitations

We take all efforts to ensure that our customers do not waste their time and resources unnecessarily. This section lists out the known issues available with the product at the time of the release. The limitations have also been mentioned.

Known Issues

1. Known issues related to JDK 1.3 in RedHatLinux :  When we do a redeployment of the SNMP adaptor in the application, the Rule Engine server is not started. This is because the TCP session used by the Rule Engine server remains alive even after the SNMP adaptor is undeployed. More Information on this issue can be seen in Java Developer Connection with the Bug ID : 4344135. http://developer.java.sun.com/developer/bugParade/bugs/4344135.html

2. A few harmless exceptions are thrown while working with SNMP Adaptor for JMX. They are displayed underneath:

java.lang.NullPointerException at javax.swing.plaf.basic.BasicProgressBarUI.paintDeterminate (BasicProgressBarUI.java:673) at javax.swing.plaf.metal.MetalProgressBarUI.paintDeterminate (MetalProgressBarUI.java:45) at javax.swing.plaf.basic.BasicProgressBarUI.paint(BasicProgressBarUI.java:335) at javax.swing.plaf.ComponentUI.update(ComponentUI.java:142) at javax.swing.JComponent.paintComponent(JComponent.java:537) at javax.swing.JComponent.paint(JComponent.java:804) at javax.swing.JComponent.paintChildren(JComponent.java:643)

3. The following harmless exception is logged into the server.log file when j2eeJtaStatTable of J2EE MIB is queried.
    

   [org.jboss.management.j2ee.JTAResource] Failed to retrieve stats javax.management.AttributeNotFoundException: Readable attribute 'TransactionCount' not found at org.jboss.mx.capability.ReflectedMBeanDispatcher.getAttribute(ReflectedMBeanDispatcher.java:136) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:456) at org.jboss.management.j2ee.JTAResource.getStats(JTAResource.java:111) at java.lang.reflect.Method.invoke(Native Method)

4. A harmless message is printed in the console when the Rule Engine server is stopped though all the threads related to Rule Engine are cleaned up. The following table shows the message:
    

   Scheduler:RuleEngineScheduler did not stop properly: 0 threads stopped out of 5 The remaining 5 threads of scheduler:RuleEngineSchedulerdid not stop in 15 seconds Scheduler:RuleEngineServerConnectionScheduler did not stop properly: 0 threads stopped out of 5 The remaining 5 threads of scheduler:RuleEngineServerConnectionSchedulerdid not stop in 15 seconds RuleEngineServer stopped...

5. When a class file is loaded in the SNMP Configuration wizard (when the agent status is not running), the loaded class file is not listed by default. Double-clicking the root node solves the problem.

Limitations

1. The MIB objects related to JDBC Resource are not implemented in the JBoss SNMP agent.

2. Remote deployment of the JBoss SNMP agent is not supported.

3. While configuring the SNMP adaptor for user-defined MBeans, it is not possible to connect to the TMX4J agent.

4. While configuring scalar MBeans by loading the jars/classes in the tool, the object name pattern cannot be used to identify the MBeans, though the object name and the class name can be used. However the object name pattern can effectively be used to configure a table MBean.

5. For Websphere 6.0 and 6.1 application servers, SNMP Adaptor will be supported only for the user-defined MBeans.  

6. While configuring the SNMP Adaptor for Tomcat application server MBeans, the SNMP Adaptor cannot be created for the UserDataBase Mbean.  

7. Remote configuration of the SNMP Adaptor for Weblogic version 9.x is not supported.