You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Zacarias <zm...@gmail.com> on 2007/10/26 17:00:51 UTC
SM-822 patch
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
Re: SM-822 patch
Posted by Zacarias <zm...@gmail.com>.
Yes, I didn't realize that remove returns an object I asumed that it returns
true or false. Congrats for the optimization.
Thanks.
Cheers
Zacarias Monzon.
On 10/26/07, Guillaume Nodet <gn...@gmail.com> wrote:
>
> Why not using:
>
> exchange = exchanges.remove(exchange.getExchangeId());
>
> instead of
>
> exchange = exchanges.get(exchange.getExchangeId());
> exchanges.remove(exchange.getExchangeId());
>
> It should be the same but in an atomic call.
>
> On 10/26/07, Zacarias <zm...@gmail.com> wrote:
> > It seems that patch files are filtered or something. I attached the
> patch
> > file at https://issues.apache.org/activemq/browse/SM-822
> >
> > Cheer,
> > Zacarias
> >
> > On 10/26/07, Guillaume Nodet <gn...@gmail.com> wrote:
> > >
> > > Could you raise a JIRA and attach your patch ? It seems to have been
> > > removed from your email. Another solution is to use the nabble forums
> > > too.
> > >
> > > On 10/26/07, Zacarias <zm...@gmail.com> wrote:
> > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > Cheers,
> > > Guillaume Nodet
> > > ------------------------
> > > Blog: http://gnodet.blogspot.com/
> > >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re: SM-822 patch
Posted by Guillaume Nodet <gn...@gmail.com>.
Why not using:
exchange = exchanges.remove(exchange.getExchangeId());
instead of
exchange = exchanges.get(exchange.getExchangeId());
exchanges.remove(exchange.getExchangeId());
It should be the same but in an atomic call.
On 10/26/07, Zacarias <zm...@gmail.com> wrote:
> It seems that patch files are filtered or something. I attached the patch
> file at https://issues.apache.org/activemq/browse/SM-822
>
> Cheer,
> Zacarias
>
> On 10/26/07, Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > Could you raise a JIRA and attach your patch ? It seems to have been
> > removed from your email. Another solution is to use the nabble forums
> > too.
> >
> > On 10/26/07, Zacarias <zm...@gmail.com> wrote:
> > > 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
> > >
> > >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: SM-822 patch
Posted by Zacarias <zm...@gmail.com>.
It seems that patch files are filtered or something. I attached the patch
file at https://issues.apache.org/activemq/browse/SM-822
Cheer,
Zacarias
On 10/26/07, Guillaume Nodet <gn...@gmail.com> wrote:
>
> Could you raise a JIRA and attach your patch ? It seems to have been
> removed from your email. Another solution is to use the nabble forums
> too.
>
> On 10/26/07, Zacarias <zm...@gmail.com> wrote:
> > 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
> >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re: SM-822 patch
Posted by Guillaume Nodet <gn...@gmail.com>.
Could you raise a JIRA and attach your patch ? It seems to have been
removed from your email. Another solution is to use the nabble forums
too.
On 10/26/07, Zacarias <zm...@gmail.com> wrote:
> 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
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/