Changing DefaultDS and *-persistence-service.xml causes NameNotFoundException: DLQ not bound and deployments in error in JBoss EAP 5

Solution Verified - Updated -

Issue

  • We are trying to migrate from EAP 4.3.0_CP10 to EAP 5, we are getting this warning and deployments error after changing the DefaultDS and *-persistence-service.xml
WARN  [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@5d6e5fc5(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@ceee5f1 destination=queue/message-sender-test destinationType=javax.jms.Queue tx=true durable=false reconnect=60 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
javax.naming.NameNotFoundException: DLQ not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:750)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:710)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at org.jboss.util.naming.Util.lookup(Util.java:222)
    at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106)
    at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82)
    at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
    at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413)
    at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351)
    at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
    at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
    at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
18:59:25,223 INFO  [TomcatDeployment] deploy, ctxPath=/message-sender
18:59:25,245 INFO  [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/message-sender'
18:59:25,504 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey@5bb7b7a3[domain=default, server=default, name=default]
18:59:25,507 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
    Dependency "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging.destination:name=message-sender-test,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging:service=PostOffice" is missing the following dependencies:
    Dependency "jboss.jgroups:service=ChannelFactory" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **")

DEPLOYMENTS IN ERROR:
  Deployment "jboss.jgroups:service=ChannelFactory" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jgroups:service=ChannelFactory' **

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.