My jboss is full with messages about Name not found: 'queue/DLQ', how can I solve this ?

Document ID : KB000013623
Last Modified Date : 14/02/2018
Show Technical Document Details

I've noticed that my system is getting almost full. It is working fine, but the server.log file is getting bigger and bigger and it is full of errors

2017-02-23 23:59:58,990 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for BulkOperationMDB 
javax.naming.NameNotFoundException: Name not found: 'queue/DLQ' 
at com.tibco.tibjms.naming.TibjmsContext.lookup( 
at com.tibco.tibjms.naming.TibjmsContext.lookup( 
at javax.naming.InitialContext.lookup( 
at org.jboss.ejb.plugins.jms.DLQHandler.createService( 
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate( 
at org.jboss.system.ServiceMBeanSupport.create( 
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery( 
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ 

How can I solve this problem ?


This is actually a misconfiguration of the TIBCO queue. The DLQ is the Dead Letter Queue, which collects requests not going to the rest of the queues. What happens here is that likely there is an incorrect definition of the queue or its location in the queues.conf file, and therefore when trying to send data to the queue, it comes up as non-existant. 

To see if this is the casa:

  • Connect to TIBCO (tibemsadmin, then ssl://7243 with it username/password) and run show queues. Look at the queue definition for the one that has problems

ssl://localhost:7243> show queues 
Queue Name SNFGXIBCT Pre Rcvrs Msgs Size 
> --------- 5* 0 0 0.0 Kb 
queue/DLQ,store=$sys.failsafe --------- 5* 0 0 0.0 Kb 

  • Next verify in the queues.conf how the queue is defined. For instance instance in this case we have


  • Make sure that the different parameters make sense. For instance, if you see a store tag, make sure that points to a valid location in tibemsd.conf. In this case this is usually meant as a shared location for High availability, so if this is not needed the setting can be reverted to default, which is


  • Correct it and restart tibco and jboss and see if the problem is still there
Additional Information: