Weblogic.security.service.NotYetInitializedException using JMX

Question

Hi there,
I'm trying to use JMX to add a notification listener to listen for attribute changes to a WLS 8.1 MBean. My code when setting up the listener is as so:
String url = "t3://localhost:7001";
String serverName = "Server1";
String userName = "weblogic";
String password = "weblogic";
MBeanHome home = null;
RemoteMBeanServer rmbs = null;
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(userName);
env.setSecurityCredentials(password);
try {
     Context ctx = env.getInitialContext();
     home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
} catch (NamingException e) {
     e.printStackTrace();
rmbs = home.getMBeanServer();
WLListener listener = new WLListener();
WebLogicObjectName mbeanName = new WebLogicObjectName("examplesServer", "Server", "examples");
rmbs.addNotificationListener(mbeanName, listener, null, null);This seems to work fine, I do not get any error messages. As you can see I'm using the server started through the examples, and I'm adding a notification listener to the ServerMBean.
My notification listener code is as so:
public void handleNotification(Notification notification, Object arg1) {
     AttributeChangeNotification changedAttrib = (AttributeChangeNotification) notification;
     try {
          System.out.println("Changed value from: " + changedAttrib.getOldValue() + " to " + changedAttrib.getNewValue());
     } catch (Exception ex) {
          ex.printStackTrace();
public boolean isNotificationEnabled(Notification arg0) {
     return true;
}Only when a notification happens and I call getOldValue() I get:
weblogic.security.service.NotYetInitializedException: [Security:090392]SecurityServiceManager not yet initialized.
     at weblogic.security.service.SecurityServiceManagerDelegateImpl.getSecurityService(SecurityServiceManagerDelegateImpl.java:156)
     at weblogic.security.service.SecurityServiceManager.getSecurityService(SecurityServiceManager.java:175)
     at weblogic.management.internal.SecurityHelper.getRoleManager(SecurityHelper.java:402)
     at weblogic.management.internal.SecurityHelper.access$100(SecurityHelper.java:54)
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:493)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:393)
     at weblogic.management.internal.AttributeChangeNotification.getOldValue(AttributeChangeNotification.java:136)
     at com.xxxx.password.PasswordBme$WLListener.handleNotification(PasswordBme.java:76)
     at com.xxxx.password.PasswordBme$WLListener_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)Is there a step I'm missing out? The entry for this message in the documentation suggests calling BEA support.

Answer 1

Hi there,
I'm trying to use JMX to add a notification listener to listen for attribute changes to a WLS 8.1 MBean. My code when setting up the listener is as so:
String url = "t3://localhost:7001";
String serverName = "Server1";
String userName = "weblogic";
String password = "weblogic";
MBeanHome home = null;
RemoteMBeanServer rmbs = null;
Environment env = new Environment();
env.setProviderUrl(url);
env.setSecurityPrincipal(userName);
env.setSecurityCredentials(password);
try {
     Context ctx = env.getInitialContext();
     home = (MBeanHome) ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
} catch (NamingException e) {
     e.printStackTrace();
rmbs = home.getMBeanServer();
WLListener listener = new WLListener();
WebLogicObjectName mbeanName = new WebLogicObjectName("examplesServer", "Server", "examples");
rmbs.addNotificationListener(mbeanName, listener, null, null);This seems to work fine, I do not get any error messages. As you can see I'm using the server started through the examples, and I'm adding a notification listener to the ServerMBean.
My notification listener code is as so:
public void handleNotification(Notification notification, Object arg1) {
     AttributeChangeNotification changedAttrib = (AttributeChangeNotification) notification;
     try {
          System.out.println("Changed value from: " + changedAttrib.getOldValue() + " to " + changedAttrib.getNewValue());
     } catch (Exception ex) {
          ex.printStackTrace();
public boolean isNotificationEnabled(Notification arg0) {
     return true;
}Only when a notification happens and I call getOldValue() I get:
weblogic.security.service.NotYetInitializedException: [Security:090392]SecurityServiceManager not yet initialized.
     at weblogic.security.service.SecurityServiceManagerDelegateImpl.getSecurityService(SecurityServiceManagerDelegateImpl.java:156)
     at weblogic.security.service.SecurityServiceManager.getSecurityService(SecurityServiceManager.java:175)
     at weblogic.management.internal.SecurityHelper.getRoleManager(SecurityHelper.java:402)
     at weblogic.management.internal.SecurityHelper.access$100(SecurityHelper.java:54)
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:493)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:393)
     at weblogic.management.internal.AttributeChangeNotification.getOldValue(AttributeChangeNotification.java:136)
     at com.xxxx.password.PasswordBme$WLListener.handleNotification(PasswordBme.java:76)
     at com.xxxx.password.PasswordBme$WLListener_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)Is there a step I'm missing out? The entry for this message in the documentation suggests calling BEA support.