Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • APACHE ACTIVEMQ RESOURCE ADAPTER

    Posted on

    I need help in trying to make out why activemq is not deploying properly.
    I'm getting below error on server start up.

    14:15:03,804 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 54) MSC000001: Failed to start service jboss.deployment.unit."soar.war".component.QueueListner.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."soar.war".component.QueueListner.START: java.lang.RuntimeException: javax.resource.spi.InvalidPropertyException: Invalid settings: acknowledgeMode must be set to: Auto-acknowledge or Dups-ok-acknowledge.
    at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_112]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_112]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_112]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_112]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122)
    Caused by: java.lang.RuntimeException: javax.resource.spi.InvalidPropertyException: Invalid settings: acknowledgeMode must be set to: Auto-acknowledge or Dups-ok-acknowledge.
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:206)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:178)
    at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
    ... 6 more
    Caused by: javax.resource.spi.InvalidPropertyException: Invalid settings: acknowledgeMode must be set to: Auto-acknowledge or Dups-ok-acknowledge.
    at org.apache.activemq.ra.ActiveMQActivationSpec.validate(ActiveMQActivationSpec.java:136)
    at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:184)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:204)
    ... 8 more

    Below is the standalone configuration.

        
                
                    
                        activemq-rar-5.7.0.rar
                    
                    XATransaction
                    
                        default
                    
                    
                        default
                    
                    
                        tcp://host:port
                    
                    
                        
                            
                                1
                                20
                                false
                                false
                            
                            
                        
                    
                    
                        
                            
                                com.assets.v1.queue
                            
                                                
                    
                            
            
        
    

    MDB configuration.

    MDB deployed in war.

    @MessageDriven( activationConfig = {

    @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),

    @ActivationConfigProperty(propertyName="destination", propertyValue="com.assets.v1.queue"),

    @ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge"),

    })

    @ResourceAdapter("activemq-rar-5.7.0.rar")

    Awaiting response. Thanks!

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat