[ 
https://jira.terracotta.org/jira//browse/CDV-232?page=comments#action_21440 ] 
            
Tim Eck commented on CDV-232:
-----------------------------

Actually this might be fixed as a side effect of not creating mbean servers 
from our code (which can have the side effect of initializing JDK logging). 
good catch. 

I'm not 100% sure what the impact of this exception is. Is definitely printed, 
and from looking at the JDK logging code, what ends up happening is the default 
logging manager implementation is used (instead of the glassfish one). I'm sure 
there is some downside to that, but not sure how bad it is


> Exception setting up logging in Glassfish + DSO
> -----------------------------------------------
>
>                 Key: CDV-232
>                 URL: https://jira.terracotta.org/jira//browse/CDV-232
>             Project: Community Development
>          Issue Type: Bug
>          Components: DSO:L1
>            Reporter: Tim Eck
>         Assigned To: Tim Eck
>
> I'm sure this is classloader related, but not sure what impact it is has 
> (glassfish still starts okay AFAICT). Also unsure if the L1 JMX stuff is 
> really part of the problem or not.
> Could not load Logmanager "com.sun.enterprise.server.logging.ServerLogManager"
> java.lang.ClassNotFoundException: 
> com.sun.enterprise.server.logging.ServerLogManager
>       at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>       at java.security.AccessController.doPrivileged(Native Method)
>       at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>       at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
>       at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>       at java.util.logging.LogManager$1.run(LogManager.java:166)
>       at java.security.AccessController.doPrivileged(Native Method)
>       at java.util.logging.LogManager.<clinit>(LogManager.java:156)
>       at java.lang.Class.forName0(Native Method)
>       at java.lang.Class.forName(Class.java:164)
>       at com.sun.jmx.trace.Trace.initDestination(Trace.java:46)
>       at com.sun.jmx.trace.Trace.<clinit>(Trace.java:25)
>       at 
> javax.management.MBeanServerFactory.debug(MBeanServerFactory.java:543)
>       at 
> javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:502)
>       at 
> javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:530)
>       at 
> javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:304)
>       at 
> javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:219)
>       at 
> javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:180)
>       at 
> com.tc.management.L1Management.attemptToRegister(L1Management.java:138)
>       at com.tc.management.L1Management.access$000(L1Management.java:39)
>       at com.tc.management.L1Management$1.run(L1Management.java:81)
>       at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev

Reply via email to