I have to do other things for a while, got as far as creating an ActiveMQ config that does not allow creation of new queue destinations on the fly. Using this with an invalid replyTo in the endpoint configuration of the producer template causes the infinite retries (every 5 seconds) as described in this thread earlier. (I do have the a complete JUnit test for it, but no resolution of it yet, not sure what the behavior should be.) Setting an invalid reply queue with this setup results in: 2013-04-15 18:22:51,655 [nsumer[REQUEST]] WARN EndpointMessageListener - Execution of JMS message listener failed. Caused by: [org.apache.camel.RuntimeCamelException - org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: User user is not authorized to create: queue://REPLYX] org.apache.camel.RuntimeCamelException: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: User user is not authorized to create: queue://REPLYX
Maybe you can use this to further investigate? <broker xmlns="http://activemq.apache.org/schema/core"; brokerName="localhost" id="broker" useJmx="false" persistent="false" start="true" dataDirectory="target/data"> <destinations> <queue physicalName="REQUEST" /> <queue physicalName="REPLY" /> <queue physicalName="DEADLETTER" /> </destinations> <plugins> <simpleAuthenticationPlugin> <users> <authenticationUser username="user" password="password" groups="users" /> </users> </simpleAuthenticationPlugin> <authorizationPlugin> <map> <authorizationMap> <authorizationEntries> <authorizationEntry queue=">" write="users" read="users" admin="admins" /> <authorizationEntry topic=">" write="users" read="users" admin="users" /> </authorizationEntries> </authorizationMap> </map> </authorizationPlugin> </plugins> </broker> 2013/4/15 Magnus Palmér <magnus.palmer.w...@gmail.com> > The best way is to create a JUnit test that uses ActiveMQ so it can > potentially become a part of the source. > Using ActiveMQ you will need to make sure that you don't dynamically > create new destinations on the fly. > http://activemq.apache.org/how-do-i-create-new-destinations.html > > I think I would then go for the option of creating the destinations needed > upon startup. > http://activemq.apache.org/configure-startup-destinations.html > > Maybe someone who is more experienced with the Camel JMS component has > some other input? > > > 2013/4/15 praveenbillampati <praveenbillamp...@gmail.com> > >> Thanks for the try magnuspalmer. I too tried for junit tests but don't >> find >> any.. Let me know if you have any other ideas on the approach.. I can try >> it >> out.. >> >> >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/org-springframework-jms-InvalidDestinationException-while-trying-to-place-a-message-on-queue-tp5730697p5730895.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > > > -- Brgds, Magnus Palmér +46736845680
