date:20130331

Claus Ibsen created CAMEL-6227:
--

 Summary: json data format - Add support for configuring gson 
options
 Key: CAMEL-6227
 URL: https://issues.apache.org/jira/browse/CAMEL-6227
 Project: Camel
  Issue Type: Improvement
  Components: camel-gson
Affects Versions: 2.10.0
Reporter: Claus Ibsen


See
http://stackoverflow.com/questions/15686032/apache-camel-gson-formatter

We should make it possible to configure those gson options in the DSL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CAMEL-6227) json data format - Add support for configuring gson options


 [ 
https://issues.apache.org/jira/browse/CAMEL-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-6227.


   Resolution: Fixed
Fix Version/s: 2.11.0
 Assignee: Claus Ibsen

Updated wiki page
https://cwiki.apache.org/confluence/display/CAMEL/JSON

 json data format - Add support for configuring gson options
 ---

 Key: CAMEL-6227
 URL: https://issues.apache.org/jira/browse/CAMEL-6227
 Project: Camel
  Issue Type: Improvement
  Components: camel-gson
Affects Versions: 2.10.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.11.0


 See
 http://stackoverflow.com/questions/15686032/apache-camel-gson-formatter
 We should make it possible to configure those gson options in the DSL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618303#comment-13618303
 ] 

Claus Ibsen commented on CAMEL-6218:


Well the NPE should be fixed in camel-core, that is a bug.

Either we should handle that null, or thrown some other kind of exception 
saying something is wrong.

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
 Attachments: camel-6214-transferExchange.java


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618304#comment-13618304
 ] 

Claus Ibsen commented on CAMEL-6218:


Alan, what exact Camel version was that stacktrace from? eg was it 2.10.0, 
2.10.1, etc. We need that so we know exactly which code line the NPE is 
triggered from.

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
 Attachments: camel-6214-transferExchange.java


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618306#comment-13618306
 ] 

Claus Ibsen commented on CAMEL-6218:


I assume its 2.10.0, then we can see that the NPE is because payload is null
http://svn.apache.org/viewvc/camel/tags/camel-2.10.0/camel-core/src/main/java/org/apache/camel/impl/DefaultExchangeHolder.java?view=markup

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
 Attachments: camel-6214-transferExchange.java


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5916) CXFRS: Inject @Params as IN message headers and handle Subresources


 [ 
https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raul Kripalani updated CAMEL-5916:
--

Issue Type: New Feature  (was: Bug)

 CXFRS: Inject @Params as IN message headers and handle Subresources
 ---

 Key: CAMEL-5916
 URL: https://issues.apache.org/jira/browse/CAMEL-5916
 Project: Camel
  Issue Type: New Feature
  Components: camel-cxf
Reporter: Raul Kripalani
Assignee: Raul Kripalani
 Fix For: 2.11.1


 See 
 http://camel.465427.n5.nabble.com/camel-cxfrs-Handling-of-Subresources-td5724615.html
  for context.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CAMEL-6228) CXFRS: Consumer - Inject Resource instance into message

Raul Kripalani created CAMEL-6228:
-

 Summary: CXFRS: Consumer - Inject Resource instance into message
 Key: CAMEL-6228
 URL: https://issues.apache.org/jira/browse/CAMEL-6228
 Project: Camel
  Issue Type: Improvement
  Components: camel-cxf
Affects Versions: 2.10.4
Reporter: Raul Kripalani
Assignee: Raul Kripalani
 Fix For: 2.11.1


CxfRsInvoker#asyncInvoke and CxfRsInvoker#syncInvoke forsake the Service 
Object. Instead it should be passed on to the CxfRsBinding.

Will try and fix for 2.11 as it implies API changes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception

2013-03-31 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Müller updated CAMEL-6218:


Affects Version/s: 2.10.4
Fix Version/s: 2.11.0

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.10.4
Reporter: Alan Foster
 Fix For: 2.11.0

 Attachments: camel-6214-transferExchange.java, 
 org.apache.cmueller.camel.zip


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception

2013-03-31 Thread JIRA


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618398#comment-13618398
 ] 

Christian Müller commented on CAMEL-6218:
-

We should fix this before 2.11.0 in my opinion.

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.10.4
Reporter: Alan Foster
 Fix For: 2.11.0

 Attachments: camel-6214-transferExchange.java, 
 org.apache.cmueller.camel.zip


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


 [ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Foster updated CAMEL-6218:
---

Attachment: camel-6218-test-project.rar

I've just added an example project which has the previously included test 
failing now. I haven't had any luck tracking down the actual issue yet sadly :(

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.10.4
Reporter: Alan Foster
 Fix For: 2.11.0

 Attachments: camel-6214-transferExchange.java, 
 camel-6218-test-project.rar, org.apache.cmueller.camel.zip


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618406#comment-13618406
 ] 

Alan Foster commented on CAMEL-6218:


Ah, thank you for including an example project [~muellerc], I see you beat me 
to it! :)

I also have seen some other bugs related in this area; The most important one 
seems to be a race condition with using InOut + ActiveMQ Component. I'll try 
making a sample project to show this bug ASAP.

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.10.4
Reporter: Alan Foster
 Fix For: 2.11.0

 Attachments: camel-6214-transferExchange.java, 
 camel-6218-test-project.rar, org.apache.cmueller.camel.zip


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5916) CXFRS: Inject @Params as IN message headers and handle Subresources

[
https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raul Kripalani updated CAMEL-5916:
--

Description:
The camel-cxfrs consumer currently dumps the {{MessageContentList}} coming from
the CXF stack into the Message body.

We should offer a CxfRsBinding that is more user-friendly and makes the request
data more accesible to the route. Aim for the following:

- Map JAX-RS parameters (@HeaderParam, @QueryParam, etc.) as Camel IN message
headers.
- Set the request entity as the IN message body.
- Inject binary @Multipart attachments as Camel IN message attachments.

Additionally, path parameters along the Subresource locator chain should be
mapped as headers too. See
http://camel.465427.n5.nabble.com/camel-cxfrs-Handling-of-Subresources-td5724615.html
for context.

was:See
http://camel.465427.n5.nabble.com/camel-cxfrs-Handling-of-Subresources-td5724615.html
for context.

CXFRS: Inject @Params as IN message headers and handle Subresources
---

Key: CAMEL-5916
URL: https://issues.apache.org/jira/browse/CAMEL-5916
Project: Camel
Issue Type: New Feature
Components: camel-cxf
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Fix For: 2.11.1

The camel-cxfrs consumer currently dumps the {{MessageContentList}} coming
from the CXF stack into the Message body.
We should offer a CxfRsBinding that is more user-friendly and makes the
request data more accesible to the route. Aim for the following:
- Map JAX-RS parameters (@HeaderParam, @QueryParam, etc.) as Camel IN message
headers.
- Set the request entity as the IN message body.
- Inject binary @Multipart attachments as Camel IN message attachments.
Additionally, path parameters along the Subresource locator chain should be
mapped as headers too. See
http://camel.465427.n5.nabble.com/camel-cxfrs-Handling-of-Subresources-td5724615.html
for context.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5916) CXFRS: Inject @Params as IN message headers and handle Subresources

[
https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raul Kripalani updated CAMEL-5916:
--

Description:
The camel-cxfrs consumer currently dumps the {{MessageContentList}} coming from
the CXF stack into the Message body. The route then has to do much lower-level
processing than usual, and is tightly coupled with the method signature of the
JAX-RS operation.

We should offer a CxfRsBinding that is more user-friendly and makes the request
data more accesible to the route. Aim for the following:

was:
The camel-cxfrs consumer currently dumps the {{MessageContentList}} coming from
the CXF stack into the Message body.

We should offer a CxfRsBinding that is more user-friendly and makes the request
data more accesible to the route. Aim for the following:

CXFRS: Inject @Params as IN message headers and handle Subresources
---

Key: CAMEL-5916
URL: https://issues.apache.org/jira/browse/CAMEL-5916
Project: Camel
Issue Type: New Feature
Components: camel-cxf
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Fix For: 2.11.1

The camel-cxfrs consumer currently dumps the {{MessageContentList}} coming
from the CXF stack into the Message body. The route then has to do much
lower-level processing than usual, and is tightly coupled with the method
signature of the JAX-RS operation.
We should offer a CxfRsBinding that is more user-friendly and makes the
request data more accesible to the route. Aim for the following:
- Map JAX-RS parameters (@HeaderParam, @QueryParam, etc.) as Camel IN message
headers.
- Set the request entity as the IN message body.
- Inject binary @Multipart attachments as Camel IN message attachments.
Additionally, path parameters along the Subresource locator chain should be
mapped as headers too. See
http://camel.465427.n5.nabble.com/camel-cxfrs-Handling-of-Subresources-td5724615.html
for context.

[jira] [Updated] (CAMEL-5916) CXFRS: Simpler, higher-level binding style injecting headers, attachements and entity

[
https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raul Kripalani updated CAMEL-5916:
--

Summary: CXFRS: Simpler, higher-level binding style injecting headers,
attachements and entity (was: CXFRS: Inject @Params as IN message headers and
handle Subresources)

CXFRS: Simpler, higher-level binding style injecting headers, attachements
and entity
-

Key: CAMEL-5916
URL: https://issues.apache.org/jira/browse/CAMEL-5916
Project: Camel
Issue Type: New Feature
Components: camel-cxf
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Fix For: 2.11.1

[jira] [Updated] (CAMEL-5916) CXFRS: Simpler, higher-level binding style injecting headers, attachments and entity

[
https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raul Kripalani updated CAMEL-5916:
--

Fix Version/s: (was: 2.11.1)
2.11.0
Summary: CXFRS: Simpler, higher-level binding style injecting
headers, attachments and entity (was: CXFRS: Simpler, higher-level binding
style injecting headers, attachements and entity)

CXFRS: Simpler, higher-level binding style injecting headers, attachments and
entity

Key: CAMEL-5916
URL: https://issues.apache.org/jira/browse/CAMEL-5916
Project: Camel
Issue Type: New Feature
Components: camel-cxf
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Fix For: 2.11.0

[jira] [Resolved] (CAMEL-5916) CXFRS: Simpler, higher-level binding style injecting headers, attachments and entity

[
https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raul Kripalani resolved CAMEL-5916.
---

Resolution: Fixed

Created a {{SimpleCxfRsBinding}} CXFRS Binding which can be enabled by setting
the {{bindingStyle}} parameter to {{SimpleConsumer}}. This is a fully backwards
compatible change, as the old behaviour is still the default one.

CXFRS: Simpler, higher-level binding style injecting headers, attachments and
entity

Key: CAMEL-5916
URL: https://issues.apache.org/jira/browse/CAMEL-5916
Project: Camel
Issue Type: New Feature
Components: camel-cxf
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Fix For: 2.11.0

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618422#comment-13618422
 ] 

Raul Kripalani commented on CAMEL-6218:
---

[~alanfoster], I fixed a few bugs and race conditions in camel-jms recently. 
Take a look if any of [these 
issues|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20component%20%3D%20camel-jms%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20assignee%20in%20(currentUser())]
 could match your findings.

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.10.4
Reporter: Alan Foster
 Fix For: 2.11.0

 Attachments: camel-6214-transferExchange.java, 
 camel-6218-test-project.rar, org.apache.cmueller.camel.zip


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-6218) TransferExchage InOut ActiveMQ Exception


[ 
https://issues.apache.org/jira/browse/CAMEL-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618466#comment-13618466
 ] 

Alan Foster commented on CAMEL-6218:


[~raulvk] Nice work on fixing a lot of those bugs! 

The test i'm writing is having a lot of issues, I am getting a lot of blueprint 
apache aries ComponentDefinitionExceptions when it attempts to start the 
org.apache.cxf.cxf-rt-transports-http bundle in JUnit for reason...

I have been able to deploy the route to Karaf just fine however! The exception 
thrown when inside Karaf is {{Caused By javax.jms.InvalidDestinationException 
Cannot publish to a deleted Destination: 
temp-queue://ID:my-computer-1234-etc-etc}} - I'll keep trying to make an actual 
JUnit test for this though

 TransferExchage InOut ActiveMQ Exception
 

 Key: CAMEL-6218
 URL: https://issues.apache.org/jira/browse/CAMEL-6218
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.10.4
Reporter: Alan Foster
 Fix For: 2.11.0

 Attachments: camel-6214-transferExchange.java, 
 camel-6218-test-project.rar, org.apache.cmueller.camel.zip


 The scnearios are :
 - when using the transferExchange option only on the producer, I don't 
 get the body back, but not the header.
 - When I use the transferExchange option on both producer and consumer, I 
 get the headers back, but not the body. And instead I get the following 
 exception
 {code:java}
 [ryQueueReplyManager[temporary]] TemporaryQueueReplyManager WARN  
 Execution of JMS message listener failed. Caused by: 
 [java.lang.NullPointerException - null]
 java.lang.NullPointerException
   at 
 org.apache.camel.impl.DefaultExchangeHolder.unmarshal(DefaultExchangeHolder.java:107)
   at 
 org.apache.camel.component.jms.JmsBinding.extractBodyFromJms(JmsBinding.java:128)
   at 
 org.apache.camel.component.jms.JmsMessage.createBody(JmsMessage.java:214)
   at org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:41)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:136)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
   at 
 org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:71)
   at 
 org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:113)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)
   at 
 org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)
   at 
 org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)
   at 
 org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
   at java.lang.Thread.run(Thread.java:662)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination

Alan Foster created CAMEL-6229:
--

 Summary: InOut ActiveMQ exception Cannot publish to a deleted 
Destination
 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster


When exposing a cxf-rs webservice and attempting to talk to another route, 
using InOut MEP + ActiveMQ the following exception occurs 

{code}
22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request :: 
22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
invoker failed for destination 'temporary' - trying to recover. Cause: The 
Consumer is closed
22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 on 
closing pooled connection: The connection is already closed
22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 on 
closing pooled connection: The connection is already closed
22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 on 
closing pooled connection: The connection is already closed
22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 on 
closing pooled connection: The connection is already closed
22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 on 
closing pooled connection: The connection is already closed
22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 on 
closing pooled connection: The connection is already closed
22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 on 
closing pooled connection: The connection is already closed
22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 on 
closing pooled connection: The connection is already closed
22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 on 
closing pooled connection: The connection is already closed
22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to delete 
Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 on 
closing pooled connection: The connection is already closed
22:18:14,857 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
invoker failed for destination 'responseHandler' - trying to recover. Cause: 
The Consumer is closed
22:18:14,919 | INFO  | responseHandler] | faultJmsMessageListenerContainer | 
153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
Connection
22:18:14,927 | INFO  | nager[temporary] | faultJmsMessageListenerContainer | 
153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
Connection
22:18:14,939 | INFO  | responseHandler] | route2   | 
147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Response handler 
successfully received a request!
22:18:14,943 | WARN  | responseHandler] | EndpointMessageListener  | 
147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Execution of JMS 
message listener failed. Caused by: [org.apache.camel.RuntimeCamelException - 
org.springframework.jms.InvalidDestinationException: Cannot publish to a 
deleted Destination: temp-queue://ID:alan-dell-49913-1364764601861-3:3:10; 
nested exception is

[jira] [Updated] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


 [ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Foster updated CAMEL-6229:
---

Attachment: camel-6229.rar

Attached a sample project which allows you to reproduce this error.

Note, I haven't been create a simple JUnit test that extends 
CamelBlueprintTestSupport, as I get a lot of strange exceptions - I'm not sure 
if this is a bug or not, but perhaps someone could shed light on it however?

So currently the steps to reproduce this bug actually depend on it being 
deployed in a container, sorry

  1) install with :  mvn install -Dmaven.test.skip=true
  2) Deploy to a container
  3) Run the junit test manually a couple of times. Sometimes the test will 
pass, but it also fails quite frequently

Sorry again that I couldn't get it succesfully running as a JUnit test!

 InOut ActiveMQ exception Cannot publish to a deleted Destination
 

 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
Assignee: Raul Kripalani
 Attachments: camel-6229.rar


 When exposing a cxf-rs webservice and attempting to talk to another route, 
 using InOut MEP + ActiveMQ the following exception occurs 
 {code}
 22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request 
 :: 
 22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'temporary' - trying to recover. Cause: The 
 Consumer is closed
 22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 
 on closing pooled connection: The connection is already closed
 22:18:14,857 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for

[jira] [Commented] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


[ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618496#comment-13618496
 ] 

Raul Kripalani commented on CAMEL-6229:
---

Two things:

# Could be related to CAMEL-5865. The InOut logic was a bit rough around the 
edges and was much improved in that ticket. Please try your code with Camel 
2.10.4 and give us some feedback.
# Please post your route logic. In particular, I'd like to see your AMQ 
component configuration (JmsConfiguration) and the AMQ endpoint options, of 
both the producer and the consumer.

Thanks.

 InOut ActiveMQ exception Cannot publish to a deleted Destination
 

 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
 Attachments: camel-6229.rar


 When exposing a cxf-rs webservice and attempting to talk to another route, 
 using InOut MEP + ActiveMQ the following exception occurs 
 {code}
 22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request 
 :: 
 22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'temporary' - trying to recover. Cause: The 
 Consumer is closed
 22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 
 on closing pooled connection: The connection is already closed
 22:18:14,857 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'responseHandler' - trying to recover. Cause: 
 The Consumer is closed
 22:18:14,919 | INFO  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
 Connection
 22:18:14,927 | INFO  |

[jira] [Assigned] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


 [ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raul Kripalani reassigned CAMEL-6229:
-

Assignee: Raul Kripalani

 InOut ActiveMQ exception Cannot publish to a deleted Destination
 

 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
Assignee: Raul Kripalani
 Attachments: camel-6229.rar


 When exposing a cxf-rs webservice and attempting to talk to another route, 
 using InOut MEP + ActiveMQ the following exception occurs 
 {code}
 22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request 
 :: 
 22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'temporary' - trying to recover. Cause: The 
 Consumer is closed
 22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 
 on closing pooled connection: The connection is already closed
 22:18:14,857 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'responseHandler' - trying to recover. Cause: 
 The Consumer is closed
 22:18:14,919 | INFO  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
 Connection
 22:18:14,927 | INFO  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
 Connection
 22:18:14,939 | INFO  | responseHandler] | route2   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Response handler 
 successfully received a request!
 22:18:14,943 | WARN  | responseHandler] | EndpointMessageListener

[jira] [Commented] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


[ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618508#comment-13618508
 ] 

Raul Kripalani commented on CAMEL-6229:
---

Thanks. Can you try with Camel JMS 2.10.4? 

Also, when you say you are on Camel 2.10, you mean Camel 2.10.0? What micro 
version exactly?

 InOut ActiveMQ exception Cannot publish to a deleted Destination
 

 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
Assignee: Raul Kripalani
 Attachments: camel-6229.rar


 When exposing a cxf-rs webservice and attempting to talk to another route, 
 using InOut MEP + ActiveMQ the following exception occurs 
 {code}
 22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request 
 :: 
 22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'temporary' - trying to recover. Cause: The 
 Consumer is closed
 22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 
 on closing pooled connection: The connection is already closed
 22:18:14,857 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'responseHandler' - trying to recover. Cause: 
 The Consumer is closed
 22:18:14,919 | INFO  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
 Connection
 22:18:14,927 | INFO  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
 Connection
 22:18:14,939 | INFO  | responseHandler] | route2   | 
 147

[jira] [Commented] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


[ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618511#comment-13618511
 ] 

Raul Kripalani commented on CAMEL-6229:
---

Ok, never mind, I see the Camel version in the logs ;)

I don't know if FuseSource/Red Hat have backmerged some important JMS patches 
onto their 2.10.0.fuse-71-047 release.

From the logs, it looks like they backmerged the initial support for 
concurrentConsumers on temp reply queues from Camel 2.10.3, but they didn't 
merge the latest fixes which actually make this feature useable (CAMEL-5865) 
in Camel 2.10.4. My reasoning is that I see 10 different temp queues being 
created for the same request queue, which is exactly what CAMEL-5865 resolves.

Please give it a shot with Camel 2.10.4. You should be able to uninstall the 
current camel-jms component and install 2.10.4 with:

{code}
install -s mvn:org.apache.camel/camel-jms/2.10.4
{code}

Hopefully no more dependency upgrades will be necessary. 

 InOut ActiveMQ exception Cannot publish to a deleted Destination
 

 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
Assignee: Raul Kripalani
 Attachments: camel-6229.rar


 When exposing a cxf-rs webservice and attempting to talk to another route, 
 using InOut MEP + ActiveMQ the following exception occurs 
 {code}
 22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request 
 :: 
 22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'temporary' - trying to recover. Cause: The 
 Consumer is closed
 22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 
 on closing pooled connection: The connection is already closed

[jira] [Commented] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


[ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618516#comment-13618516
 ] 

Alan Foster commented on CAMEL-6229:


[~raulvk] Thanks for the response! I did think that your fixed jira CAMEL-5865 
seemed familiar :)

I wasn't able to swap out the camel-jms in the fuse container, but I downloaded 
service mix 4.5.1 which has camel 2.10.4 in it by default, and it seems to be 
working, hurray :)

 InOut ActiveMQ exception Cannot publish to a deleted Destination
 

 Key: CAMEL-6229
 URL: https://issues.apache.org/jira/browse/CAMEL-6229
 Project: Camel
  Issue Type: Bug
Reporter: Alan Foster
Assignee: Raul Kripalani
 Attachments: camel-6229.rar


 When exposing a cxf-rs webservice and attempting to talk to another route, 
 using InOut MEP + ActiveMQ the following exception occurs 
 {code}
 22:18:14,813 | INFO  | tp1882786420-364 | route1   | 
 147 - org.apache.camel.camel-core - 2.10.0.fuse-71-047 | Received a request 
 :: 
 22:18:14,838 | WARN  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'temporary' - trying to recover. Cause: The 
 Consumer is closed
 22:18:14,849 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:3 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:4 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:5 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:6 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:7 
 on closing pooled connection: The connection is already closed
 22:18:14,850 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:8 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:2 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:1 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:9 
 on closing pooled connection: The connection is already closed
 22:18:14,851 | INFO  | nager[temporary] | PooledConnection | 
 122 - org.apache.activemq.activemq-pool - 5.7.0.fuse-71-047 | failed to 
 delete Temporary Queue temp-queue://ID:alan-dell-49913-1364764601861-3:3:10 
 on closing pooled connection: The connection is already closed
 22:18:14,857 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
 invoker failed for destination 'responseHandler' - trying to recover. Cause: 
 The Consumer is closed
 22:18:14,919 | INFO  | responseHandler] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
 Connection
 22:18:14,927 | INFO  | nager[temporary] | faultJmsMessageListenerContainer | 
 153 - org.springframework.jms -

[jira] [Commented] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination


[ 
https://issues.apache.org/jira/browse/CAMEL-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618520#comment-13618520
 ] 

Alan Foster commented on CAMEL-6229:


Ah, I was just about to mark this as resolved, and then I noticed some very odd 
things in the log files :

{code}
0:28:59,458 | INFO  | tp1937409810-134 | route1   | 96 
- org.apache.camel.camel-core - 2.10.4 | Received a request :: 
00:28:59,461 | WARN  | responseHandler] | TemporaryQueueReplyManager   | 
125 - org.apache.camel.camel-jms - 2.10.4 | Exception inside the DMLC for 
Temporary ReplyTo Queue for destination responseHandler, refreshing ReplyTo 
destination
javax.jms.IllegalStateException: The Consumer is closed
at 
org.apache.activemq.ActiveMQMessageConsumer.checkClosed(ActiveMQMessageConsumer.java:817)[62:org.apache.activemq.activemq-core:5.7.0]
at 
org.apache.activemq.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:581)[62:org.apache.activemq.activemq-core:5.7.0]
at 
org.apache.activemq.pool.PooledMessageConsumer.receive(PooledMessageConsumer.java:67)[59:org.apache.activemq.activemq-pool:5.7.0]
at 
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:429)[123:org.springframework.jms:3.0.7.RELEASE]
at 
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:310)[123:org.springframework.jms:3.0.7.RELEASE]
at 
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)[123:org.springframework.jms:3.0.7.RELEASE]
at 
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)[123:org.springframework.jms:3.0.7.RELEASE]
at 
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)[123:org.springframework.jms:3.0.7.RELEASE]
at 
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)[123:org.springframework.jms:3.0.7.RELEASE]
at java.lang.Thread.run(Thread.java:662)[:1.6.0_27]
00:28:59,462 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
123 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
invoker failed for destination 'temporary' - trying to recover. Cause: The 
Consumer is closed
00:28:59,468 | INFO  | responseHandler] | PooledConnection | 59 
- org.apache.activemq.activemq-pool - 5.7.0 | failed to delete Temporary Queue 
temp-queue://ID:alan-dell-53847-1364772340736-5:17:1 on closing pooled 
connection: The connection is already closed
00:28:59,472 | INFO  | responseHandler] | PooledConnection | 59 
- org.apache.activemq.activemq-pool - 5.7.0 | failed to delete Temporary Queue 
temp-queue://ID:alan-dell-53847-1364772340736-5:17:2 on closing pooled 
connection: The connection is already closed
00:28:59,472 | WARN  | responseHandler] | faultJmsMessageListenerContainer | 
123 - org.springframework.jms - 3.0.7.RELEASE | Setup of JMS message listener 
invoker failed for destination 'responseHandler' - trying to recover. Cause: 
The Session is closed
00:28:59,479 | WARN  | responseHandler] | BrokerRegistry   | 62 
- org.apache.activemq.activemq-core - 5.7.0 | Broker localhost not started so 
using default instead
00:28:59,482 | WARN  | responseHandler] | BrokerRegistry   | 62 
- org.apache.activemq.activemq-core - 5.7.0 | Broker localhost not started so 
using default instead
00:28:59,486 | INFO  | responseHandler] | faultJmsMessageListenerContainer | 
123 - org.springframework.jms - 3.0.7.RELEASE | Successfully refreshed JMS 
Connection
{code}

And these are continuously output the log file too

{code}
00:32:11,049 | WARN  | responseHandler] | TemporaryQueueReplyManager   | 
125 - org.apache.camel.camel-jms - 2.10.4 | Timeout occurred after 2 millis 
waiting for reply message with correlationID 
[Camel-ID-alan-dell-53850-1364772369222-0-126]. Setting 
ExchangeTimedOutException on (MessageId: ID-alan-dell-53850-1364772369222-0-125 
on ExchangeId: ID-alan-dell-53850-1364772369222-0-124) and continue routing.
00:32:11,053 | WARN  | responseHandler] | CorrelationTimeoutMap| 96 
- org.apache.camel.camel-core - 2.10.4 | Exception happened during eviction of 
entry ID 
org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler@4efdd8b, won't 
evict and will continue trying: java.lang.IllegalStateException: 
COMPLETE,resumed
00:32:12,055 | WARN  | responseHandler] | TemporaryQueueReplyManager   | 
125 -

[jira] [Comment Edited] (CAMEL-6229) InOut ActiveMQ exception Cannot publish to a deleted Destination