You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@tuscany.apache.org by Gregor Kiddie <Gr...@channeladvisor.com> on 2011/05/19 12:55:44 UTC

Bug in Tuscany around JMS and replyTo

This looks like a bug in Tuscany, but we can't narrow it down to where.

 

The way we have our system set up.

 

Module which is endpointed by Tuscany, using JMS (ActiveMQ). This has a
request queue and response queue set up for it

 

Pretty much as

<service name="BusinessService">

      <binding.jms correlationScheme="RequestCorrelIDToCorrelID" >

            <response>

                  <destination name="BusinessServiceResponse" />

                        </response>

            <tuscany:wireFormat.jmsObject />

      </binding.jms>

</service>

 

We have camel set up on ActiveMQ which takes text messages from another
queue, converts them into Object messages suitable for Tuscany, sets the
replyTo header to the response queue for Camel, and passes the message
into the Module.

 

Now the peculiar bit. This works... Once. Tuscany never seems to respond
that the request queue is free to be re-used, so Camel blocks
indefinitely (and therefore doesn't consume any further messages).

 

Any suggestions as to what might be going on? Tracing through the code
isn't showing anything obvious!

 

Gk.

 

 

 


RE: Bug in Tuscany around JMS and replyTo

Posted by Gregor Kiddie <Gr...@channeladvisor.com>.
You know I forget to put that in every time :D

 

Version 1.6.

 

We couldn't find enough documentation for 2.x to go with it.

 

Gk.

 

From: ant elder [mailto:ant.elder@gmail.com] 
Sent: 19 May 2011 14:28
To: user@tuscany.apache.org
Subject: Re: Bug in Tuscany around JMS and replyTo

 

There have been quite a lot of code changes on the JMS binding over the
releases so as a start which Tuscany release are you using? 

   ...ant

On Thu, May 19, 2011 at 11:55 AM, Gregor Kiddie
<Gr...@channeladvisor.com> wrote:

This looks like a bug in Tuscany, but we can't narrow it down to where.

 

The way we have our system set up.

 

Module which is endpointed by Tuscany, using JMS (ActiveMQ). This has a
request queue and response queue set up for it

 

Pretty much as

<service name="BusinessService">

      <binding.jms correlationScheme="RequestCorrelIDToCorrelID" >

            <response>

                  <destination name="BusinessServiceResponse" />

                        </response>

            <tuscany:wireFormat.jmsObject />

      </binding.jms>

</service>

 

We have camel set up on ActiveMQ which takes text messages from another
queue, converts them into Object messages suitable for Tuscany, sets the
replyTo header to the response queue for Camel, and passes the message
into the Module.

 

Now the peculiar bit. This works... Once. Tuscany never seems to respond
that the request queue is free to be re-used, so Camel blocks
indefinitely (and therefore doesn't consume any further messages).

 

Any suggestions as to what might be going on? Tracing through the code
isn't showing anything obvious!

 

Gk.

 

 

 

 


Re: Bug in Tuscany around JMS and replyTo

Posted by ant elder <an...@gmail.com>.
There have been quite a lot of code changes on the JMS binding over the
releases so as a start which Tuscany release are you using?

   ...ant

On Thu, May 19, 2011 at 11:55 AM, Gregor Kiddie <
Gregor.Kiddie@channeladvisor.com> wrote:

> This looks like a bug in Tuscany, but we can’t narrow it down to where.
>
>
>
> The way we have our system set up.
>
>
>
> Module which is endpointed by Tuscany, using JMS (ActiveMQ). This has a
> request queue and response queue set up for it
>
>
>
> Pretty much as
>
> <service name=*"BusinessService"*>
>
>       <binding.jms correlationScheme=*"RequestCorrelIDToCorrelID"* >
>
>             <response>
>
>                   <destination name=*"BusinessServiceResponse"* />
>
>                         </response>
>
>             <tuscany:wireFormat.jmsObject />
>
>       </binding.jms>
>
> </service>
>
>
>
> We have camel set up on ActiveMQ which takes text messages from another
> queue, converts them into Object messages suitable for Tuscany, sets the
> replyTo header to the response queue for Camel, and passes the message into
> the Module.
>
>
>
> Now the peculiar bit. This works… Once. Tuscany never seems to respond that
> the request queue is free to be re-used, so Camel blocks indefinitely (and
> therefore doesn’t consume any further messages).
>
>
>
> Any suggestions as to what might be going on? Tracing through the code
> isn’t showing anything obvious!
>
>
>
> Gk.
>
>
>
>
>
>
>