activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From johnament <>
Subject [GitHub] activemq-artemis pull request #800: POC for CDI Integration in Artemis
Date Mon, 26 Sep 2016 01:04:43 GMT
GitHub user johnament opened a pull request:

    POC for CDI Integration in Artemis

    This PR isn't ready to go.  However, two issues I'm running into.
    - When running tests, it cannot locate the JBoss Log Manager.  I'm assuming theres some
JVM arguments missing.
    Could not load Logmanager "org.jboss.logmanager.LogManager"
    java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
    	at java.lang.ClassLoader.loadClass(
    	at sun.misc.Launcher$AppClassLoader.loadClass(
    	at java.lang.ClassLoader.loadClass(
    	at java.util.logging.LogManager$
    	at java.util.logging.LogManager$
    	at Method)
    	at java.util.logging.LogManager.<clinit>(
    	at org.jboss.logging.LoggerProviders.tryJBossLogManager(
    	at org.jboss.logging.LoggerProviders.findProvider(
    	at org.jboss.logging.LoggerProviders.find(
    	at org.jboss.logging.LoggerProviders.<clinit>(
    	at org.jboss.logging.Logger.getLogger(
    	at org.jboss.logging.Logger$
    	at Method)
    	at org.jboss.logging.Logger.getMessageLogger(
    	at org.jboss.logging.Logger.getMessageLogger(
    	at org.jboss.weld.logging.VersionLogger.<clinit>(
    	at org.jboss.weld.bootstrap.WeldStartup.<clinit>(
    	at org.jboss.weld.bootstrap.WeldBootstrap.<init>(
    	at org.apache.activemq.artemis.cdi.bootstrap.CDIBootstrapTest.shouldStartJMS(
    	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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
    	at org.junit.runners.model.FrameworkMethod.invokeExplosively(
    	at org.junit.internal.runners.statements.InvokeMethod.evaluate(
    	at org.junit.runners.ParentRunner.runLeaf(
    	at org.junit.runners.BlockJUnit4ClassRunner.runChild(
    	at org.junit.runners.BlockJUnit4ClassRunner.runChild(
    	at org.junit.runners.ParentRunner$
    	at org.junit.runners.ParentRunner$1.schedule(
    	at org.junit.runners.ParentRunner.runChildren(
    	at org.junit.runners.ParentRunner.access$000(
    	at org.junit.runners.ParentRunner$2.evaluate(
    	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(
    	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(
    	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(
    	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(
    	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(
    	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(
    	at org.apache.maven.surefire.booter.ForkedBooter.main(
    - Second, and I was hoping it was because I was flying and not paying attention closely,
however I'm stumped.  Even though it seems like the message is being sent, I'm not able to
receive it.  I also noticed the new CDI API doesn't give a good way to create a destination.

You can merge this pull request into a Git repository by running:

    $ git pull cdi-client

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #800
commit ad3f1fa544e7e2ac51255b515e6022d482b5017f
Author: John D. Ament <>
Date:   2016-08-01T02:12:50Z

    POC for CDI Integration in Artemis


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message