I implemented a posible solution for the "component not owner" problem. I
found that
deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java
sleeps meanwhile the jsr componet modifies the message.In JMSFlow the
variable "exchange" is serialized to an MQ queue and deserialized that's why
when ConsumerProccesor wakes up exchange is in the wrong state. With this
patch I propose to take again the "exchange" from the "exchanges" list. I
tested it with Seda flow and JmsFlow separated and it works.
I'm looking forward for your answer.

Best regards.

Zacarías Monzón

Reply via email to