dev@glassfish.java.net

this message was emitted before....

From: Bobby Bissett <bobby.bissett_at_oracle.com>
Date: Wed, 25 Aug 2010 16:26:28 -0400

What should I make of these?

[#|2010-08-25T16:15:02.667-0400|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.server.logging|_ThreadID=1;_ThreadName=main;|This message was emitted before the logging service started:Total time to parse domain.xml: 105 milliseconds|#]

[#|2010-08-25T16:15:02.671-0400|SEVERE|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.server.logging|_ThreadID=1;_ThreadName=main;|This message was emitted before the logging service started:class com.sun.hk2.component.LazyInhabitant upgrading domain.xml failed org.jvnet.hk2.component.ComponentException: problem initializing|#]


I have two classes that create and use a logger in exactly the same way. One of the loggers works fine and resolves keys in the resource bundle; the other doesn't. The only difference that I can see is that the non-working logger is being used during upgrade. Is there a known issue that I can't do something like this in upgrade code?

    private static final Logger logger =
        LogDomains.getLogger(GMSConfigUpgrade.class, LogDomains.GMS_LOGGER);

I've seen other people using anonymous loggers, which might account for it, but I wanted to check in case this isn't expected behavior. I can get the anonymous logger and pass in my resource bundle, but I don't want to if I'm not supposed to.

Thanks,
Bobby