DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Testcase Required Testcase Required
Assignee: Unassigned
Reporter: Andrew Bourgeois
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus AccessPlatform loaded before Maven dependencies are loaded

Created: 21/Oct/12 02:07 AM   Updated: 15/Nov/12 03:38 PM   Resolved: 31/Oct/12 09:01 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Severity: Development

 Description  « Hide
Try pointing towards a file with the following content:

"# register SLF4JBridgeHandler as handler for the j.u.l. root logger
handlers = org.slf4j.bridge.SLF4JBridgeHandler

.level = ALL


The dependency containing that handler is this one:

<!-- DataNucleus uses java.util.Logging, this is needed to forward the calls to SLF4J -->

What you'll get when your JVM starts:

Bad level value for property: DataNucleus.JDO.level
Bad level value for property: DataNucleus.General.level
Can't load log handler "org.slf4j.bridge.SLF4JBridgeHandler"
java.lang.ClassNotFoundException: org.slf4j.bridge.SLF4JBridgeHandler
java.lang.ClassNotFoundException: org.slf4j.bridge.SLF4JBridgeHandler
at Method)
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
at java.util.logging.LogManager$
at Method)
at java.util.logging.LogManager.loadLoggerHandlers(
at java.util.logging.LogManager.initializeGlobalHandlers(
at java.util.logging.LogManager.access$1100(
at java.util.logging.LogManager$RootLogger.getHandlers(
at java.util.logging.Logger.log(
at java.util.logging.Logger.doLog(
at java.util.logging.Logger.log(
at java.util.logging.Logger.fine(
at org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(
at org.codehaus.plexus.DefaultPlexusContainer.<init>(
at org.codehaus.plexus.DefaultPlexusContainer.<init>(
at org.apache.maven.cli.MavenCli.container(
at org.apache.maven.cli.MavenCli.doMain(
at org.apache.maven.cli.MavenCli.main(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
at org.codehaus.plexus.classworlds.launcher.Launcher.main(

Andy Jefferson added a comment - 21/Oct/12 02:05 PM
I have no problem with logging. Loggers are created statically and only when the NucleusLogger is utilised, with what is in the CLASSPATH. A testcase demonstrating any "problem" is required with all issues marked as "Bug" since being unable to see something precludes it from any consideration

Andy Jefferson made changes - 21/Oct/12 02:05 PM
Field Original Value New Value
Priority Major [ 3 ] Incomplete [ 6 ]
Andy Jefferson added a comment - 31/Oct/12 09:01 AM
Repost here if you have a way of reproducing this

Andy Jefferson made changes - 31/Oct/12 09:01 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Cannot Reproduce [ 5 ]
Andy Jefferson made changes - 15/Nov/12 03:38 PM
Status Resolved [ 5 ] Closed [ 6 ]