Message Queue already registered

264 views
Skip to first unread message

Jochen

unread,
Nov 15, 2015, 4:48:07 PM11/15/15
to Immutant
Hi...

with Immutant 2.1.1, when deploying my war to wildfly 9.0.0, I get an exception:

Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.messaging.default.jms.queue.rapida-evts-in is already registered

Cause is the simple call 
(queue "rapida-evts-in")

The queue is declared in wildly config as follows:
<jms-queue name="rapida-evts-in">
    <entry name="/java:jboss:exported/queue/rapida-evts-in"/>
</jms-queue>

When I remove the queue call, the app deploys fine.

I appended the complete logged error message for more info.

Any idea what I do wrong?

Ciao

...Jochen


22:32:24,282 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 80) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./: java.lang.RuntimeException: java.lang.RuntimeException: Application initialization failed
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:85)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Application initialization failed
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:224)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
... 6 more
Caused by: java.lang.RuntimeException: Application initialization failed
at org.projectodd.wunderboss.as.ServletListener.contextInitialized(ServletListener.java:155)
at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:195)
... 8 more
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.projectodd.wunderboss.clojure.ClojureLanguage.eval(ClojureLanguage.java:73)
at org.projectodd.wunderboss.ApplicationRunner.start(ApplicationRunner.java:52)
at org.projectodd.wunderboss.as.ServletListener$1.start(ServletListener.java:104)
at org.projectodd.wunderboss.as.ServletListener$2.run(ServletListener.java:116)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.projectodd.wunderboss.LoaderWrapper.callInLoader(LoaderWrapper.java:35)
at org.projectodd.wunderboss.clojure.ClojureLanguage.eval(ClojureLanguage.java:64)
... 8 more
Caused by: java.lang.reflect.InvocationTargetException
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:497)
at org.projectodd.wunderboss.as.messaging.wildfly.WildFlyDestinationManager.installService(WildFlyDestinationManager.java:106)
at org.projectodd.wunderboss.as.messaging.wildfly.WildFlyDestinationManager.installQueueService(WildFlyDestinationManager.java:45)
at org.projectodd.wunderboss.as.messaging.ASMessaging.createQueue(ASMessaging.java:59)
at org.projectodd.wunderboss.messaging.jms.JMSMessagingSkeleton.findOrCreateQueue(JMSMessagingSkeleton.java:236)
at immutant.messaging$queue.doInvoke(messaging.clj:113)
at clojure.lang.RestFn.invoke(RestFn.java:410)
at rapidamicro.messaging$rapida_evts_in_queue.invoke(messaging.clj:9)
at rapidamicro.messaging$start_rapida_evts_in_queue_listener.invoke(messaging.clj:25)
at rapidamicro.messaging$start_queue_listeners.invoke(messaging.clj:28)
at rapidamicro.server$start_server.invoke(server.clj:22)
at rapidamicro.server$start_server.invoke(server.clj:14)
at rapidamicro.server$start_server.invoke(server.clj:12)
at rapidamicro.server$_main.doInvoke(server.clj:37)
at clojure.lang.RestFn.invoke(RestFn.java:397)
at clojure.lang.Var.invoke(Var.java:375)
at immutant.wildfly$init_deployment.invoke(wildfly.clj:90)
at clojure.core$eval68.invoke(NO_SOURCE_FILE:0)
at clojure.lang.Compiler.eval(Compiler.java:6782)
at clojure.lang.Compiler.eval(Compiler.java:6772)
at clojure.lang.Compiler.eval(Compiler.java:6772)
at clojure.lang.Compiler.eval(Compiler.java:6745)
at clojure.core$eval.invoke(core.clj:3081)
at clojure.lang.Var.invoke(Var.java:379)
at org.projectodd.wunderboss.clojure.ClojureLanguage$2.call(ClojureLanguage.java:68)
at org.projectodd.wunderboss.LoaderWrapper.callInLoader(LoaderWrapper.java:33)
... 9 more
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.messaging.default.jms.queue.rapida-evts-in is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
at org.jboss.as.messaging.jms.JMSQueueService.installService(JMSQueueService.java:134)
... 38 more

22:32:24,294 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./: java.lang.RuntimeException: java.lang.RuntimeException: Application initialization failed
    Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Application initialization failed
    Caused by: java.lang.RuntimeException: Application initialization failed
    Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
    Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
    Caused by: java.lang.reflect.InvocationTargetException
    Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.messaging.default.jms.queue.rapida-evts-in is already registered"}}

Toby Crawley

unread,
Nov 19, 2015, 11:24:50 AM11/19/15
to Jochen, Immutant
Sorry for the delayed response. Comments below.

On Sun, Nov 15, 2015 at 4:48 PM, Jochen <joc...@riekhof.de> wrote:
> with Immutant 2.1.1, when deploying my war to wildfly 9.0.0, I get an
> exception:
>
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service
> jboss.messaging.default.jms.queue.rapida-evts-in is already registered
>
> Cause is the simple call
> (queue "rapida-evts-in")
>
> The queue is declared in wildly config as follows:
> <jms-queue name="rapida-evts-in">
> <entry name="/java:jboss:exported/queue/rapida-evts-in"/>
> </jms-queue>

It looks like the docs for creating destinations[1] in standalone.xml
are out of date - we do actually now care about the entries for the
destination. If you change your jms-queue element to:

<jms-queue name="rapida-evts-in">
<entry name="java:/jms/queue/rapida-evts-in"/>
<entry name="/java:jboss:exported/queue/rapida-evts-in"/>
</jms-queue>

calling (queue "rapida-evts-in") should work.

Sorry for the confusion, I'll update the docs.



[1]: http://immutant.org/documentation/current/apidoc/guide-messaging.html#h5338

Toby Crawley

unread,
Nov 19, 2015, 12:28:38 PM11/19/15
to Jochen, Immutant
The docs have been fixed, and will be in 2.1.2, once that is released:
http://github.com/immutant/immutant/commit/bf4a72e96

-Toby

Jochen

unread,
Nov 19, 2015, 2:21:17 PM11/19/15
to Immutant, joc...@riekhof.de
Thanks Toby, works fine now!

Ciao

…Jochen
Reply all
Reply to author
Forward
0 new messages