NPE in stopWeblogic.cmd with Server Logging Bridge

Question

I'm migrating an EAR that depends on JDK logging to WLS 10.3.3. To activate the JDK logging in my domain logs I followed [url http://download.oracle.com/docs/cd/E14571_01/web.1111/e13739/logging_services.htm#WLLOG199]the instructions given in the WLS manual. The logging part works as expected now. However, my stopWeblogic.cmd fails with the following NPE:
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://DT04748:7001 with userid weblogic ...
WLST detected that the RuntimeMBeanServer is not enabled. This
might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot
function without this MBeanServer.
This Exception occurred at Thu Jan 06 13:20:24 CET 2011.
java.lang.NullPointerException
        at weblogic.logging.ServerLoggingHandler.publish(ServerLoggingHandler.java:24)
        at java.util.logging.Logger.log(Logger.java:481)
        at java.util.logging.Logger.doLog(Logger.java:503)
        at java.util.logging.Logger.logp(Logger.java:619)
        at com.sun.jmx.remote.util.ClassLogger.finer(ClassLogger.java:130)
        at com.sun.jmx.remote.util.ClassLogger.trace(ClassLogger.java:88)
        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:333)
        at weblogic.management.remote.common.WLSRMIConnector.doConnect(WLSRMIConnector.java:150)
        at weblogic.management.remote.common.WLSRMIConnector.access$100(WLSRMIConnector.java:27)
        at weblogic.management.remote.common.WLSRMIConnector$2.run(WLSRMIConnector.java:138)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
        at weblogic.security.Security.runAs(Security.java:61)
        at weblogic.management.remote.common.WLSRMIConnector.connect(WLSRMIConnector.java:136)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
        at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:678)
        at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:398)
        at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
        at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
        at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
        at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.python.core.PyReflectedFunction.__call__(Unknown Source)
        at org.python.core.PyMethod.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at org.python.core.PyObject.invoke(Unknown Source)
        at org.python.pycode._pyx4.connect$1(<iostream>:16)
        at org.python.pycode._pyx4.call_function(<iostream>)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(Unknown Source)
        at org.python.pycode._pyx15.f$0(D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py:6)
        at org.python.pycode._pyx15.call_function(D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyCode.call(Unknown Source)
        at org.python.core.Py.runCode(Unknown Source)
        at org.python.util.PythonInterpreter.execfile(Unknown Source)
        at weblogic.management.scripting.WLST.main(WLST.java:131)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at weblogic.WLST.main(WLST.java:29)
Problem invoking WLST - Traceback (innermost last):
  File "D:\Oracle\Middleware\user_projects\domains\FLUX\shutdown.py", line 6, in ?
  File "<iostream>", line 22, in connect
  File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST."
Use dumpStack() to view the full stacktrace
Done
Stopping Derby Server...
Steps to reproduce
1. Create a logging.properties file with the following contents:
# Specify the handlers to create in the root logger
handlers = weblogic.logging.ServerLoggingHandler
# Register handlers for my.app and their child loggers
my.app.handlers = java.util.logging.ConsoleHandler, weblogic.logging.ServerLoggingHandler
# Do not send the my.app log messages to the root handler
my.app.useParentHandlers = false
# Set the default logging level for the root logger
.level = ALL
# Set the default logging level for new ConsoleHandler instances
java.util.logging.ConsoleHandler.level = INFO
# Set the default logging level for new FileHandler instances
weblogic.logging.ServerLoggingHandler.level = ALL2. Add the following directive in the setDomainEnv.cmd:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.util.logging.config.file=path/to/logging.properties3. Start-stop the domain and the above NPE occurs while WLS keeps running. Remove the directive from step 2 and the start-stop sequence goes back to normal.
Environment
Oracle JDK:
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)OS: Windows XP Pro SP3
Your help would be very much appreciated! Please let me know if you need any additional info.
Thanks,
Bas

Answer 1

Hi Sandeep,
Thanks a lot for your quick reply! You were right, the logging directive was used both client and server side. I moved
-Djava.util.logging.config.file=path/to/logging.propertiesfrom setDomainEnv.cmd to startWeblogic.cmd and WLS can be stopped correctly now.
Regards,
Bas