Troubleshooting
Problem
Health Monitor connects as anonymous to perform MBean lookup for JMS Queue Depth
Symptom
Is there a way to specify a security principal and credential when
performing this Queue Depth lookup,
or is enabling "Anonymous Admin
Lookup Enabled" on WebLogic the recommended solution?
Error in HealthMonitor log:
2008-09-11 08:03:38,604:ERRORDTL:Timer-8:
[1221134618604]java.lang.IllegalArgumentException: JNDI naming exception:
javax.naming.NoPermissionException: User <anonymous> does not have permission
on weblogic.management.adminhome to perform lookup operation. [Root exception
is javax.naming.NoPermissionException: User <anonymous> does not have
permission on weblogic.management.adminhome to perform lookup operation.]
at weblogic.management.Helper.getMBeanHomeForName(Helper.java:110)
at
weblogic.management.Helper.getAdminMBeanHome(Helper.java:38)
at
com.yantra.ycp.hm.jms.WLSQueueBrowser.getQueueDepth(WLSQueueBrowser.java:33)
at
com.yantra.ycp.hm.jms.YHMJMSCollectable.collect(YHMJMSCollectable.java:52)
at
com.yantra.ycp.hm.jms.YHMSchedulableJMSMonitor.run(YHMSchedulableJMSMonitor.java
:46)
at java.util.TimerThread.mainLoop(Timer.java:512)
at
java.util.TimerThread.run(Timer.java:462)
Cause
Resolving The Problem
Resolution: By enabling Anonymous Admin Lookup on the WebLogic server where
the queue resides:
[WebLogic 9.2 console] -> Domain -> Security (tab) ->
"Anonymous Admin Lookup Enabled" -> CHECKED, then restart domain
"Specifies whether anonymous, read-only access to WebLogic Server MBeans should
be allowed from the MBeanHome API."
the HealthMonitor appears to work
properly.
Historical Number
PRI49824
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21543421