Re: Getting a "Cannot publish to a deleted Destination" but eventually works after a couple of retries

Not sure how increasing the number of files limit could have resolved this issue? Please help me understand. -- View this message in context:

Re: Getting a Cannot publish to a deleted Destination but eventually works after a couple of retries

Apologies for not giving an immediate response. It seems that our problem was solved by increasing the open files limit setting for both Centos and Ubuntu hosting Glassfish, Fuse and ActiveMQ. But to answer your question, yes we are using a broker network comprised by 4 Ubuntu nodes. 1 has a

Re: Getting a Cannot publish to a deleted Destination but eventually works after a couple of retries

How are you setting up the connection factory for these things? Is this a single broker or some network or brokers? On Wednesday, June 25, 2014, tikboy tikboy.balat...@gmail.com wrote: Hi We have an application that runs on Glassfish 3.1. It uses Camel to publish a request/reply JMS message

Getting a Cannot publish to a deleted Destination but eventually works after a couple of retries

Hi We have an application that runs on Glassfish 3.1. It uses Camel to publish a request/reply JMS message to an AMQ broker. The message is then consumed by a Camel JMS listener running on Fuse 7.0. This setup works most of the time but sometimes, when the camel route on Fuse is sending the