|
|
Some of the problems that you might encounter during the course of MBean configuration and management are listed below. The cause of the snag and the key to its resolution are offered to prevent you from facing a deadlock.
Problem:
The product does not get installed while executing the binary or the exe
file.
Cause: When the JDK set in the environment path is corrupted,
the installation process cannot be invoked.
Solution: Run the binary or the exe file as mentioned below
with a valid Java Home as the argument:
For Linux and Solaris:
|
./binfile.bin -is:javahome <JREHOME> |
For Windows:
|
binfile.exe -is:javahome <JREHOME> |
Problem: When any WAR/EAR file is deployed in WebLogic 7.0, the following exception is thrown:
|
"weblogic.management.NoAccessRuntimeException:" |
Cause: Users might not have permission to invoke certain operations in the WebLogic server.
Solution: Specify the system variable -Dweblogic.disableMBeanAuthorization=true while starting WebLogic Server 7.0.
Problem:
Error message while setting an attribute of RequiredModelMBean through
SNMP in JMX RI.
Cause: In RequiredModelMBean, whenever an attribute is set,
an AttributeChangeNotification is emitted. When there are no AttributeChangeNotification
listeners registered with RequiredModelMBean, emission of the notification
fails. Hence the error message while setting the attribute.
Solution: Register an AttributeChangeNotification listener to
the corresponding RequiredModelMBean using the addAttributeChangeNotificationListener
method.
Problem:
For Linux systems, unable to view the jbossPerformance scalar group and
the Process table in WebNMS JBoss MIB.
Cause 1: By default, the view access to Host-Resources-MIB is
not provided in the file snmpd.conf
under /etc/snmp/
Solution 1: Verify if the view access to mib-2 is set in the
file snmpd.conf. If not, enable
view access to mib-2 as follows:
Default Settings
|
# Third, create a view for us to let
the group have rights to: # name incl/excl subtree mask(optional) view systemview included system
# Finally, grant the group read-only
access to the systemview view. # group context sec.model sec.level prefix read write notif access notConfigGroup "" any noauth exact systemview none none
|
Modified Settings
|
# Third, create a view
for us to let the group have rights to: # name incl/excl subtree mask(optional) view mib2 included
.iso.org.dod.internet.mgmt.mib-2
fc # Finally, grant the
group read-only access to the systemview view. # group context sec.model sec.level prefix read write notif access notConfigGroup "" any noauth exact mib2 none none |
|
|