Re: Requestor doesn't start listener?

[Willem Jiang]

Spring 3.0 will not start the MessageListenerContainer even you set the 
autoStart property to be true.
We work around this issue in Camel 2.2, so please try out the Camel 
2.2-SNAPSHOT, and we will release Camel 2.2 in next month.

Willem
Claus Ibsen wrote:
Hi

You most likely need Camel 2.2 to use Spring 3.0 as Spring 3.0 change
something in their JMS implementation.
http://camel.apache.org/camel-220-release.html
http://camel.apache.org/download.html

On Sat, Jan 16, 2010 at 11:49 PM, rbolkey <rbol...@gmail.com> wrote:
Hi all,

Context: Camel 2.1.0 and Spring JMS 3.0.0.RELEASE

I'm having a problem, and I think the issue is that Camel's JMS Requestor
doesn't start the Spring SimpleMessageListenerContainer that it creates?
Requestor#doStart() calls the container's afterPropertiesSet, but doesn't
call the containers #start() method.

Context: I'm trying to get an asynchronous request reply from a spring bean.
The message is returned to the temporary container in the Requestor, but the
container rejects it because the container isn't in a running state
(isRunning is false).  While debugging the container, I find that
#initialize() is called on it (via afterPropertiesSet) but never #start().
The following exception is thrown when the async response is delivered
(AbstractMessageListenerContainer#doExecuteListener):

201614.669 | WARN | s.j.l.SimpleMessageListenerContainer | Rejecting
received message because of the listener container having been stopped in
the meantime: ActiveMQBytesMessage {commandId = 13, responseRequired = true,
messageId = ID:dagda-35519-1263672970635-2:1:1:1:1, originalDestination =
null, originalTransactionId = null, producerId =
ID:dagda-35519-1263672970635-2:1:1:1, destination =
temp-queue://ID:dagda-35519-1263672970635-2:1:1, transactionId = null,
expiration = 0, timestamp = 1263672974644, arrival = 0, brokerInTime =
1263672974645, brokerOutTime = 1263672974651, correlationId =
727d928b-5b71-4844-a989-eba998a9bafb, replyTo =
temp-queue://ID:dagda-35519-1263672970635-2:1:1, persistent = true, type =
null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
null, compressed = false, userID = null, content =
org.apache.activemq.util.byteseque...@f08d0f, marshalledProperties =
org.apache.activemq.util.byteseque...@bcfa38, dataStructure = null,
redeliveryCounter = 0, size = 0, properties =
{CamelBeanMultiParameterArray=false, CamelJmsDeliveryMode=2},
readOnlyProperties = true, readOnlyBody = true, droppable = false}
ActiveMQBytesMessage{ bytesOut = null, dataOut = null, dataIn = null }

Is my suspicion correct, or am I missing something?

Thanks,
Rick
--
View this message in context: 
http://old.nabble.com/Requestor-doesn%27t-start-listener--tp27194455p27194455.html
Sent from the Camel - Users mailing list archive at Nabble.com.