You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jiri Danek (JIRA)" <ji...@apache.org> on 2016/08/02 08:52:20 UTC
[jira] [Commented] (ARTEMIS-597) java.lang.ClassNotFoundException:
org.jboss.logmanager.LogManager
[ https://issues.apache.org/jira/browse/ARTEMIS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403643#comment-15403643 ]
Jiri Danek commented on ARTEMIS-597:
------------------------------------
Possibly related. I noticed this comment on method {{AIOFileLockTimeoutTest#testAIOFileLockExpiration}}
{noformat}
When running this test from an IDE add this to the test command line so that the AssertionLoggerHandler works properly:
-Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dlogging.configuration=file:<path_to_source>/tests/config/logging.properties
{noformat}
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> -----------------------------------------------------------------
>
> Key: ARTEMIS-597
> URL: https://issues.apache.org/jira/browse/ARTEMIS-597
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.4.0
> Environment: Clean installation of Fedora 24 Cloud with just maven, git and the dependencies installed.
> Reporter: Jiri Danek
> Priority: Critical
>
> When running {{mvn clean package install}}, the following exception is printed when tests are being run
> {noformat}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ artemis-core-client ---
> [INFO] Surefire report directory: /home/vagrant/repos/activemq-artemis/artemis-core-client/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.activemq.artemis.ClientThreadPoolsTest
> Hello!
> java.lang.InterruptedException
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at org.apache.activemq.artemis.ClientThreadPoolsTest$2.run(ClientThreadPoolsTest.java:123)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Could not load Logmanager "org.jboss.logmanager.LogManager"
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.util.logging.LogManager$1.run(LogManager.java:195)
> at java.util.logging.LogManager$1.run(LogManager.java:181)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.<clinit>(LogManager.java:181)
> at org.jboss.logging.LoggerProviders.tryJBossLogManager(LoggerProviders.java:144)
> at org.jboss.logging.LoggerProviders.findProvider(LoggerProviders.java:85)
> at org.jboss.logging.LoggerProviders.find(LoggerProviders.java:34)
> at org.jboss.logging.LoggerProviders.<clinit>(LoggerProviders.java:31)
> at org.jboss.logging.Logger.getLogger(Logger.java:2465)
> at org.jboss.logging.Logger.getLogger(Logger.java:2490)
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.<clinit>(ServerLocatorImpl.java:79)
> at org.apache.activemq.artemis.ClientThreadPoolsTest.testSystemPropertiesThreadPoolSettings(ClientThreadPoolsTest.java:167)
> at org.apache.activemq.artemis.ClientThreadPoolsTest.testSmallPool(ClientThreadPoolsTest.java:163)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}
> As far as I can tell, this is harmless, except that it is a distraction when one is looking for source of real problems. Possibly, I'd venture to guess it prevents some log messages from being printed through the JBoss LogManager.
> Similar issue was already resolved once as ARTEMIS-224.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)